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


[Xen-devel] Re: regression on Xen: 23573 breaks PV on HVM guests

To: "Stefano Stabellini" <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: regression on Xen: 23573 breaks PV on HVM guests
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 25 Jul 2011 12:17:44 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Jul 2011 04:19:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1107251152310.12963@kaball-desktop>
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: <alpine.DEB.2.00.1107251152310.12963@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 25.07.11 at 12:54, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> 
>>> wrote:
> Hi all,
> I would just let you know that I found a regression in the hypervisor:
> CS 23573 causes PV on HVM guests to hang during boot.

Any details (e.g. state of the guest, messages from the hypervisor)
that might help finding out what the problem is? I'm not aware that I
intentionally changed anything behavior-wise in the pv-on-hvm specific


> The offending commit is the following:
> # HG changeset patch
> # User Jan Beulich <jbeulich@xxxxxxxxxx>
> # Date 1308825163 -3600
> # Node ID 584c2e5e03d96f912cdfe90f8e9f910d5d661706
> # Parent  4e9562c1ce4ecaac40011556c16712aefd47afa6
> replace d->nr_pirqs sized arrays with radix tree
> 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
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Xen-devel mailing list