linux-kernel - Re: [PATCH] x86: Re-enable IO-APIC for non-SMP X86

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

Message-ID: <54C17F15.1070404@nexus-software.ie>
Date:	Thu, 22 Jan 2015 22:52:05 +0000
From:	Bryan O'Donoghue <pure.logic@...us-software.ie>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	mingo@...hat.com, hpa@...or.com, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Re-enable IO-APIC for non-SMP X86_32

On 22/01/15 21:42, Thomas Gleixner wrote:
>   config X86_UP_APIC
>   	bool "Local APIC support on uniprocessors"
> -	depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI
> +	depends on X86_32 && !SMP && !X86_32_NON_STANDARD
>   	---help---
>   	  A local APIC (Advanced Programmable Interrupt Controller) is an
>   	  integrated interrupt controller in the CPU. If you have a single-CPU
> @@ -872,6 +872,10 @@ config X86_UP_APIC
>   	  performance counters), and the NMI watchdog which detects hard
>   	  lockups.
>
> +config X86_UP_APIC_MSI
> +	def_bool y
> +	select X86_UP_APIC if X86_32 && !SMP && !X86_32_NON_STANDARD && PCI_MSI
> +
>   config X86_UP_IOAPIC
>   	bool "IO-APIC support on uniprocessors"
>   	depends on X86_UP_APIC

OK.

That works.

You can select local apic and/or io-apic on X86_32 individually with 
PCI_MSI swiched off.

If you switch on PCI_MSI the option for X86_UP_APIC_MSI disappears from 
and is silently selected by X86_UP_APIC_MSI.




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