This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH, v3] replace d->nr_pirqs sized arrays with radix

To: "Keir Fraser" <keir.xen@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH, v3] replace d->nr_pirqs sized arrays with radix tree
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 21 Jun 2011 16:01:11 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 21 Jun 2011 08:04:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA266908.1C9B1%keir.xen@xxxxxxxxx>
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: <4E00698702000078000486C5@xxxxxxxxxxxxxxxxxxxx> <CA266908.1C9B1%keir.xen@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 21.06.11 at 16:28, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> On 21/06/2011 08:51, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>> With this it is questionable whether retaining struct domain's nr_pirqs
>> is actually necessary - the value now only serves for bounds checking,
>> and this boundary could easily be nr_irqs.
>> Note that ia64, the build of which is broken currently anyway, is only
>> being partially fixed up.
>> v2: adjustments for split setup/teardown of translation data
>> v3: re-sync with radix tree implementation changes
> What is the reason for rcu-head.h?

Header dependency mess (need to have the full type definition
available in xen/irq.h).


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>