linux-kernel - Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP systems

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:	Mon, 7 Jul 2008 09:17:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Len Brown <lenb@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-next@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH 2/2] acpi: Disable IRQ 0 through I/O APIC for some HP
	systems


* Rafael J. Wysocki <rjw@...k.pl> wrote:

> Appended is a patch that actually works for me (it's missing the i386 
> part, but I can't test that anyway).
> 
> Please note two things:
> (1) The whole acpi_dmi_table[] thing originally depended on __i386__, so it
>     wouldn't work on x86-64 no matter what.  I removed that dependecy, but
>     I have no idea why it was there and so I'm not sure if that's correct. 

> (2) The clear_IO_APIC_pin(apic1, pin1) done if 
>     disable_irq0_through_ioapic is true is absolutely essential.  The 
>     symptoms are 100% reproducible without it.

thanks, applied to tip/x86, to give this some more testing.

the clear_IO_APIC_pin() is the most worrisome aspect of the change - but 
since we are already in limited quirk mode, does it hurt? Maciej, any 
preferences?

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