From: "H. Peter Anvin" Subject: Re: Re: [tip:irq/core] x86: xen: Sanitise sparse_irq handling Date: Fri, 15 Oct 2010 19:01:36 -0700 Message-ID: <6a6702dc-7dbb-47a3-a0cf-18c8a65252fe@email.android.com> References: <4CB8EE8A.5020900@goop.org> <4CB8EF30.7060504@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4CB8EF30.7060504@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , "linux-kernel@vger.kernel.org" , "mingo@redhat.com" , Jeremy Fitzhardinge Cc: "Xen-devel@lists.xensource.com" , Ian Campbell , "linux-tip-commits@vger.kernel.org" List-Id: xen-devel@lists.xenproject.org It should. "Jeremy Fitzhardinge" wrote: > On 10/15/2010 05:15 PM, Jeremy Fitzhardinge wrote: >> On 10/12/2010 01:29 PM, tip-bot for Thomas Gleixner wrote: >>> Commit-ID: 77dff1c755c3218691e95e7e38ee14323b35dbdb >>> Gitweb: http://git.kernel.org/tip/77dff1c755c3218691e95e7e38ee143= 23b35dbdb >>> Author: Thomas Gleixner >>> AuthorDate: Wed, 29 Sep 2010 17:37:10 +0200 >>> Committer: Thomas Gleixner >>> CommitDate: Tue, 12 Oct 2010 16:53:44 +0200 >>> >>> x86: xen: Sanitise sparse_irq handling >>> >>> There seems to be more cleanups possible, but that's left to the xen >>> experts :) >> This causes the kernel to fail to boot under Xen. The WARN_ON(res !=3D >> irq) triggers and nobody is very happy about the results. > >Of course the really interesting question is whether this sparse irq >rework allows us to hang our extra per-irq information of the irq_data >structure now, rather than having to maintain all these auxiliary arrays= ? > >Thanks, > J --=20 Sent from my mobile phone. Please pardon any lack of formatting.