|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [tip:irq/core] x86: xen: Sanitise sparse_irq handlin
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "mingo@xxxxxxx" <mingo@xxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [tip:irq/core] x86: xen: Sanitise sparse_irq handling |
From: |
"H. Peter Anvin" <hpa@xxxxxxxxx> |
Date: |
Fri, 15 Oct 2010 19:01:36 -0700 |
Cc: |
"Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx> |
Delivery-date: |
Fri, 15 Oct 2010 19:02:49 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4CB8EF30.7060504@xxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<tip-77dff1c755c3218691e95e7e38ee14323b35dbdb@xxxxxxxxxxxxxx> <4CB8EE8A.5020900@xxxxxxxx> <4CB8EF30.7060504@xxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
It should.
"Jeremy Fitzhardinge" <jeremy@xxxxxxxx> 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/77dff1c755c3218691e95e7e38ee14323b35dbdb
>>> Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>>> AuthorDate: Wed, 29 Sep 2010 17:37:10 +0200
>>> Committer: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>>> 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 !=
>> 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
--
Sent from my mobile phone. Please pardon any lack of formatting.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|