public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86 PCI domain support
Date: Sat, 3 Dec 2005 13:03:15 -0800	[thread overview]
Message-ID: <20051203210315.GA4822@suse.de> (raw)
In-Reply-To: <4391FC0A.9040202@pobox.com>

On Sat, Dec 03, 2005 at 03:11:54PM -0500, Jeff Garzik wrote:
> Andi Kleen wrote:
> >On Fri, Dec 02, 2005 at 08:39:04PM -0500, Jeff Garzik wrote:
> >
> >>ACPI PCI support stopped short of supporting multiple PCI domains,
> >>which is something I need in order to support a current machine
> >>configuration, and something many will soon need, to support upcoming
> >>systems.
> >>
> >>This is a minimal, untested implementation.  But it should work,
> >>provided your PCI op hooks (direct, BIOS, mmconfig) support PCI domains
> >>(mmconfig).
> >
> >
> >It looks like a good start.  Thanks for doing this.
> >
> >It actually needs some more fixes - e.g. falling back to 
> >type1 if the bus is not covered in MCFG (needed for the 
> >K8 internal busses) and a workaround for buggy Asus BIOS with wrong MCFG.
> >I have that in the works.
> >
> >But your changes are needed too - or at least they are correct
> >according to the spec. I don't know of a system that actually
> >has different mmconfig apertures for different busses yet.
> >The only case that's interesting right now is that some busses
> >don't support it at all, but these don't need a seg number,
> >just a non listing in MCFG.
> >
> >Greg are you queueing this up? 
> 
> The first two patches could go in immediately, the last should probably 
> wait a bit...

Ok, I'll queue up all of them for testing in the next few -mm releases
before sending them on.

Care to add some "Signed-off-by:" lines to the patches?

thanks,

greg k-h

  reply	other threads:[~2005-12-03 21:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03  1:39 [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03  1:39 ` [PATCH 1/3] x86 PCI domain support: a humble fix Jeff Garzik
2005-12-03  1:40 ` [PATCH 2/3] x86 PCI domain support: struct pci_sysdata Jeff Garzik
2005-12-03  1:40 ` [PATCH 3/3] x86 PCI domain support: the meat Jeff Garzik
2005-12-03  1:42 ` [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03  3:15 ` Andi Kleen
2005-12-03 20:11   ` Jeff Garzik
2005-12-03 21:03     ` Greg KH [this message]
2005-12-07  0:39     ` Greg KH
2005-12-07  1:32       ` Andi Kleen
2005-12-07  1:41         ` Greg KH
2005-12-07  2:14       ` Jeff Garzik
2005-12-07  2:33         ` Greg KH
2005-12-07  4:12           ` Jeff Garzik
2005-12-07  5:23             ` Greg KH

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=20051203210315.GA4822@suse.de \
    --to=gregkh@suse.de \
    --cc=ak@suse.de \
    --cc=jgarzik@pobox.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