linux-kernel - Re: [PATCH v2 1/2] PCI: Add 'nodomains' boot option, and pci_domains

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Oct 2007 17:17:12 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Greg KH <greg@...ah.com>, Andi Kleen <ak@...e.de>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2 1/2] PCI: Add 'nodomains' boot option, and	pci_domains_supported
 global

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@...hat.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.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/