linux-kernel - Re: [v3.4-rc1] ACPI regression bisected

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]

Message-ID: <alpine.LFD.2.02.1204121907330.2542@ionos>
Date:	Thu, 12 Apr 2012 19:09:54 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
cc:	Jörg Otte <jrg.otte@...glemail.com>,
	Andi Kleen <ak@...ux.intel.com>, linux-kernel@...r.kernel.org,
	Len Brown <lenb@...nel.org>
Subject: Re: [v3.4-rc1] ACPI regression bisected

On Thu, 12 Apr 2012, Thomas Gleixner wrote:

> On Thu, 12 Apr 2012, Matthew Garrett wrote:
> 
> > On Thu, Apr 12, 2012 at 10:57:45AM +0200, Thomas Gleixner wrote:
> > 
> > > OK, so now the question is whether the ACPI interrupt can end up being
> > > shared or not.
> > 
> > Per spec:
> > 
> > "OSPM is required to treat the ACPI SCI interrupt as a sharable, level, 
> > active low interrupt."
> 
> I feared that. So now is the question whether there is a way to mask
> the interrupt at the "device" level.

If not, I could be persuaded to provide a mechanism to force thread
all interrupts which are on that line, if there's a good argument to
do so.

All machines in my farm do not share the line, so I guess it's only
relevant when you boot with apic disabled or such.

Thanks,

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