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] xen.git branch reorg

To: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 28 Apr 2009 09:28:05 -0700
Cc: bderzhavets@xxxxxxxxx, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 28 Apr 2009 09:28:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1240932793.10269.99.camel@petrie>
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: <351130.85293.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1240932793.10269.99.camel@petrie>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090320)
William Pitcock wrote:

I'll try to debug it if I have time over the weekend. It shouldn't be
very hard to do.

Do you have any specifics on what is failing?

For some reason the privcmd mappings are either not getting created properly, or are disappearing for some reason, causing a SIGBUS on qemu's privcmd mapping. I put a bunch of printks in at one point, and couldn't see where it was failing. I'm planning on having another go with all the tracing infrastructure I put in place, but feel free to look at it if you're so inclined.


Xen-devel mailing list

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