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:27:15 +0000 Message-ID: <4B9F6B1302000078000351A3@vpn.id2.novell.com> References: <4779de451003151809n6cec813dp32d77fee34b1bda2@mail.gmail.com> <20100316014851.GE7622@phenom.dumpdata.com> <4779de451003151955v15863656i5f39a631a8c558ee@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4779de451003151955v15863656i5f39a631a8c558ee@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, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org >>> Dan Gora 16.03.10 03:55 >>> >This is where I could really use some help... Is it possible crash >only the domU from with xen? What would it leave behind to analyze >with xenctx? domain_crash(current->domain); assuming the access happens in the context of the DomU. If it happens in Dom0's context (e.g. coming from qemu) you'd still kill the whole system with this, so be careful. Jan