From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>, Andi Kleen <ak@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 1/2] PCI: Add 'nodomains' boot option, and pci_domains_supported global
Date: Thu, 11 Oct 2007 17:17:12 -0400 [thread overview]
Message-ID: <470E92D8.8060603@garzik.org> (raw)
In-Reply-To: <20071011205727.GA29222@havoc.gtf.org>
Jeff Garzik wrote:
> * Introduce pci_domains_supported global, hardcoded to zero if
> !CONFIG_PCI_DOMAINS.
>
> * Introduce 'nodomains' boot option, which clears pci_domains_supported
> on platforms that enable it by default (x86, x86-64, and others when
> they are converted to use this).
>
> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> ---
> Revised per Andi's comments, and split into two patches.
>
> As found in jgarzik/misc-2.6.git#ALL and jgarzik/misc-2.6.git#pciseg.
>
> Documentation/kernel-parameters.txt | 2 ++
> drivers/pci/pci.c | 13 +++++++++++++
> include/linux/pci.h | 7 +++++--
> 3 files changed, 20 insertions(+), 2 deletions(-)
As a note, if this wasn't obvious, this was not implemented in
x86-specific code because I think other arches can/should be able to
hook into this.
The default !CONFIG_PCI_DOMAINS implementation continues to work for all
such arches.
next prev parent reply other threads:[~2007-10-11 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:57 [PATCH v2 1/2] PCI: Add 'nodomains' boot option, and pci_domains_supported global Jeff Garzik
2007-10-11 20:58 ` [PATCH v2 2/2] X86: Introduce and enable PCI domain support Jeff Garzik
2007-10-11 21:40 ` Greg KH
2007-10-11 21:45 ` Greg KH
2007-10-11 21:17 ` Jeff Garzik [this message]
2007-10-11 21:38 ` [PATCH v2 1/2] PCI: Add 'nodomains' boot option, and pci_domains_supported global Greg KH
2007-10-11 21:50 ` Jeff Garzik
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=470E92D8.8060603@garzik.org \
--to=jeff@garzik.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.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