[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 00/05] xen: events: cleanups after irq core improvements (Was: Re: [Xen-devel] Re: [tip:irq/core] x86: xen: Sanitise sparse_irq handling)
- To: "H. Peter Anvin" <hpa@xxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
- From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
- Date: Mon, 25 Oct 2010 17:22:16 +0100
- Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>, "mingo@xxxxxxx" <mingo@xxxxxxx>
- Delivery-date: Mon, 25 Oct 2010 09:32:46 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
On Sat, 2010-10-16 at 01:17 +0100, Jeremy Fitzhardinge wrote:
> 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?
On Sat, 2010-10-16 at 03:01 +0100, H. Peter Anvin wrote:
> It should.
I'm about to followup with an initial stab at some cleanups which are
made possible by these core changes, including hanging the per-irq info
off the handler_data.
These patches are on top of recent Linus master tree plus Konrad's
swiotlb-xen tree and Stefano's PVHVM tree since the latter in particular
touches the same area.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
