From: Andi Kleen <ak@suse.de>
To: Greg KH <greg@kroah.com>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
Jim Paradis <jparadis@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86[-64] PCI domain support
Date: Tue, 26 Sep 2006 22:27:22 +0200 [thread overview]
Message-ID: <200609262227.22217.ak@suse.de> (raw)
In-Reply-To: <20060926202303.GA15369@kroah.com>
On Tuesday 26 September 2006 22:23, Greg KH wrote:
> On Tue, Sep 26, 2006 at 03:15:08PM -0400, Jeff Garzik wrote:
> >
> > The x86[-64] PCI domain effort needs to be restarted, because we've got
> > machines out in the field that need this in order for some devices to
> > work.
> >
> > RHEL is shipping it now, apparently without any problems.
> >
> > The 'pciseg' branch of
> > git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git pciseg
>
> So are the NUMA issues now taken care of properly?
I assume IBM would have complained if it was broken in RHEL.
But iirc Summit has two BIOS options for this. Maybe they just recommend
to set the other one for Linux. Anyways I guess that can be all figured
out once the patch is in tree.
-Andi
next prev parent reply other threads:[~2006-09-26 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 19:15 [PATCH] x86[-64] PCI domain support Jeff Garzik
2006-09-26 20:23 ` Greg KH
2006-09-26 20:27 ` Andi Kleen [this message]
2006-09-26 20:44 ` Jeff Garzik
2006-09-27 4:40 ` Greg KH
2006-09-27 7:28 ` Rolf Eike Beer
2006-09-28 9:33 ` Muli Ben-Yehuda
2006-09-28 9:45 ` Jeff Garzik
2006-09-28 22:45 ` Muli Ben-Yehuda
2006-09-28 23:03 ` Jeff Garzik
2006-09-28 23:31 ` Muli Ben-Yehuda
2006-09-30 9:34 ` Muli Ben-Yehuda
2006-09-30 10:03 ` Jeff Garzik
2006-09-30 10:42 ` Muli Ben-Yehuda
2006-09-30 11:12 ` Jeff Garzik
2006-09-30 11:41 ` Jeff Garzik
2006-09-30 17:51 ` [PATCH] x86-64: Calgary IOMMU: update to work with PCI domains Muli Ben-Yehuda
2006-10-01 3:41 ` Jeff Garzik
2006-09-29 13:43 ` [PATCH] x86[-64] PCI domain support Jon Mason
2006-09-29 17:11 ` Muli Ben-Yehuda
2006-09-29 18:24 ` Jon Mason
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=200609262227.22217.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=jparadis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox