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] PCI BAR register space written with garbage in HVM guest

To: "Dan Gora" <dan.gora@xxxxxxxxx>
Subject: Re: [Xen-devel] PCI BAR register space written with garbage in HVM guest.
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 16 Mar 2010 10:24:35 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Mar 2010 03:25:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4779de451003151809n6cec813dp32d77fee34b1bda2@xxxxxxxxxxxxxx>
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: <4779de451003151809n6cec813dp32d77fee34b1bda2@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Dan Gora <dan.gora@xxxxxxxxx> 16.03.10 02:09 >>>
>I'm really pretty much at a loss as even how to debug this.  There
>doesn't appear to be any dump_stack() in XEN so that I can see what
>called pci_conf_write() in XEN, but even then it appears that it only
>gets called as a trap from the dom0 or domU.  It's not clear to me if
>you can even see what process/stack actually caused the trap back in
>the dom0 or domU.  Is that possible?



Xen-devel mailing list