linux-kernel - Re: [PATCH v2] x86/mrst: correct pin to irq mapping

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: <20110412063538.GD31050@elte.hu>
Date:	Tue, 12 Apr 2011 08:35:38 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	jacob pan <jacob.jun.pan@...ux.intel.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Feng Tang <feng.tang@...el.com>,
	Alan Cox <alan@...ux.intel.com>,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: [PATCH v2] x86/mrst: correct pin to irq mapping


* jacob pan <jacob.jun.pan@...ux.intel.com> wrote:

> Without the patch, kernel will crash during boot on Moorestown since the 
> secondary CPU clockevent (apbt1) will fail to request irq#1, which does not 
> have ioapic chip in its irq_desc[] entry. So, I would think this is an urgent 
> bug fix for 39.

Ok, just for future reference, this information is like 10x more important than 
*any* of the other information you presented in various changelog versions of 
this patch! I do not have this hardware so i had no idea how severe the problem 
was in practice - whether it's cosmetic, performance related or stability 
related.

I'll push your urgent fix to Linus via tip:x86/urgent.

Thanks,

	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/