From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: PCI BAR register space written with garbage in HVM guest. Date: Tue, 16 Mar 2010 10:24:35 +0000 Message-ID: <4B9F6A7302000078000351A0@vpn.id2.novell.com> References: <4779de451003151809n6cec813dp32d77fee34b1bda2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4779de451003151809n6cec813dp32d77fee34b1bda2@mail.gmail.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Gora Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Dan Gora 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? show_execution_state(guest_cpu_user_regs()); Jan