linux-kernel - [RFC v1 0/2] x86: kconfig: simplify APIC entries

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-next>] [day] [month] [year] [list]

Date:	Tue, 10 Mar 2015 16:14:33 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	bhelgaas@...gle.com, mingo@...hat.com, tglx@...utronix.de,
	hpa@...or.com, pure.logic@...us-software.ie, jgross@...e.com,
	luto@...capital.net, andy.shevchenko@...il.com,
	thomas.petazzoni@...e-electrons.com, JBeulich@...e.com, bp@...e.de
Cc:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	x86@...nel.org, "Luis R. Rodriguez" <mcgrof@...e.com>
Subject: [RFC v1 0/2] x86: kconfig: simplify APIC entries

From: "Luis R. Rodriguez" <mcgrof@...e.com>

There's quite a bit of Kconfig entries related to X86_LOCAL_APIC
and X86_IO_APIC, and all for 32-bit purposes. Since 32-bit isn't in
a magical state of flux we now *should* know when to enable or disable
APIC stuff for these systems. Through history we've observed for
instance PCI_MSI requires these under specific scenarios, just enable
it for those learned scenarios and expect future requirements to also
be explicit about the requirements on 32-bit. This lets us remove
clutter (3 Kconfig entries) from x86 Kconfig simply for 32-bit build
purposes.

Luis R. Rodriguez (2):
  x86: kconfig: simplify enabling [IO]APIC for PCI_MSI
  x86: kconfig: remove UP [IO]APIC options

 Documentation/PCI/MSI-HOWTO.txt |  5 +----
 arch/x86/Kconfig                | 33 ++-------------------------------
 drivers/pci/Kconfig             |  2 ++
 3 files changed, 5 insertions(+), 35 deletions(-)

-- 
2.3.2.209.gd67f9d5.dirty

--
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/