LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Andi Kleen" <ak@suse.de>, "Chuck Ebbert" <cebbert@redhat.com>,
"Muli Ben-Yehuda" <muli@il.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
riku.seppala@kymp.net, "Andy Whitcroft" <apw@shadowen.org>
Subject: Re: Oops in 2.6.23-rc1-git9, arch/x86_64/pci/k8-bus.c::fill_mp_bus_to_cpumask()
Date: Sat, 4 Aug 2007 11:15:32 -0700 [thread overview]
Message-ID: <20070804111532.1d3936fa.akpm@linux-foundation.org> (raw)
In-Reply-To: <86802c440708041045gd4a70fejf54f8532ff1a46f6@mail.gmail.com>
On Sat, 4 Aug 2007 10:45:31 -0700 "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
> Andrew,
>
> still need
> x86_64-get-mp_bus_to_node-as-early-v2.patch in the -mm
> it fix
What does it fix? Much more detail, please.
> diff -puN arch/i386/pci/irq.c~x86_64-get-mp_bus_to_node-as-early-v2
> arch/i386/pci/irq.c
> --- a/arch/i386/pci/irq.c~x86_64-get-mp_bus_to_node-as-early-v2
> +++ a/arch/i386/pci/irq.c
> @@ -136,10 +136,26 @@ static void __init pirq_peer_trick(void)
> busmap[e->bus] = 1;
> }
> for(i = 1; i < 256; i++) {
> + struct pci_bus *bus = NULL;
> + struct pci_sysdata *sd;
> if (!busmap[i] || pci_find_bus(0, i))
> continue;
> - if (pci_scan_bus(i, &pci_root_ops, NULL))
> + /* Allocate per-root-bus (not per bus) arch-specific data.
> + * TODO: leak; this memory is never freed.
> + * It's arguable whether it's worth the trouble to care.
> + */
> + sd = kzalloc(sizeof(*sd), GFP_KERNEL);
> + if (!sd) {
> + printk(KERN_ERR "PCI: OOM, not probing PCI bus %02x\n",
> + i);
> + continue;
> + }
> + sd->node = get_mp_bus_to_node(i);
> + bus = pci_scan_bus(i, &pci_root_ops, sd);
> + if (bus)
> printk(KERN_INFO "PCI: Discovered primary peer
> bus %02x [IRQ]\n", i);
Wordwrapped, tabs replaced with spaces.
Please, for once and for all, fix your email client?
Thanks.
next prev parent reply other threads:[~2007-08-04 18:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:10 Chuck Ebbert
2007-08-03 22:50 ` Andrew Morton
2007-08-04 6:17 ` Muli Ben-Yehuda
2007-08-04 9:30 ` Andi Kleen
2007-08-04 16:32 ` Andrew Morton
2007-08-04 17:45 ` Yinghai Lu
2007-08-04 18:15 ` Andrew Morton [this message]
2007-08-04 19:02 ` Yinghai Lu
2007-08-05 5:52 ` Andrew Morton
2007-08-05 6:02 ` Muli Ben-Yehuda
2007-08-05 6:07 ` Yinghai Lu
2007-08-05 6:11 ` Muli Ben-Yehuda
2007-08-05 6:24 ` Yinghai Lu
2007-08-05 6:27 ` Yinghai Lu
2007-08-05 6:04 ` Yinghai Lu
2007-08-04 23:40 ` Andi Kleen
2007-08-05 4:15 ` Muli Ben-Yehuda
2007-08-05 4:33 ` Yinghai Lu
2007-08-05 5:00 ` Muli Ben-Yehuda
2007-08-05 4:31 ` Yinghai Lu
2007-08-05 5:04 ` Muli Ben-Yehuda
2007-08-05 5:38 ` Yinghai Lu
2007-08-05 7:53 ` [PATCH/RFT] finish i386 and x86-64 sysdata conversion Muli Ben-Yehuda
2007-08-05 8:49 ` Yinghai Lu
2007-08-05 11:54 ` Muli Ben-Yehuda
2007-08-05 16:39 ` Yinghai Lu
2007-08-05 17:36 ` Jeff Garzik
2007-08-05 20:41 ` Yinghai Lu
2007-08-07 22:49 ` Andrew Morton
2007-08-07 22:56 ` Muli Ben-Yehuda
2007-08-08 0:43 ` Jeff Garzik
2007-08-08 1:09 ` Yinghai Lu
2007-08-08 1:21 ` Jeff Garzik
2007-08-08 1:28 ` Yinghai Lu
2007-08-08 2:59 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070804111532.1d3936fa.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=apw@shadowen.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=riku.seppala@kymp.net \
--cc=yhlu.kernel@gmail.com \
--subject='Re: Oops in 2.6.23-rc1-git9, arch/x86_64/pci/k8-bus.c::fill_mp_bus_to_cpumask()' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).