linux-kernel - Re: [PATCH] x86, irq: Fix regression caused by commit b568b8601f05

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:	Tue, 17 Feb 2015 18:55:14 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Pavel Machek <pavel@....cz>, Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jiang Liu <jiang.liu@...ux.intel.com>,
	Ville Syrjälä <syrjala@....fi>,
	Len Brown <len.brown@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
	Sander Eikelenboom <linux@...elenboom.it>,
	linux-acpi@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86, irq: Fix regression caused by commit b568b8601f05

On Monday, February 16, 2015 08:36:37 PM Pavel Machek wrote:
> On Mon 2015-02-16 10:11:13, Jiang Liu wrote:
> > Commit b568b8601f05 ("Treat SCI interrupt as normal GSI interrupt")
> > accidently removes support of legacy PIC interrupt when fixing a
> 
> accidentaly?
> 
> > regression for Xen, which causes a nasty regression on HP/Compaq
> > nc6000 where we fail to register the ACPI interrupt, and thus
> > lose eg. thermal notifications leading a potentially overheated
> > machine.
> > 
> > So reintroduce support of legacy PIC based ACPI SCI interrupt.
> > 
> > Reported-by: Ville Syrjälä <syrjala@....fi>
> > Signed-off-by: Jiang Liu <jiang.liu@...ux.intel.com>
> 
> Acked-by: Pavel Machek <pavel@....cz>

Is anyone taking care of this one or should I take it?

Ingo, Peter?


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/