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 15:54:34 +0000 Message-ID: <4B9FB7CA020000780003534E@vpn.id2.novell.com> References: <4779de451003151809n6cec813dp32d77fee34b1bda2@mail.gmail.com> <20100316014851.GE7622@phenom.dumpdata.com> <4779de451003151955v15863656i5f39a631a8c558ee@mail.gmail.com> <20100316152040.GA28821@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100316152040.GA28821@phenom.dumpdata.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 , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Konrad Rzeszutek Wilk 16.03.10 16:20 >>> >The Hypervisor gets "trapped" when an outb is made (look for >emulate_privileged_op function and specifically out). No, that's only the path taken for pv guests. HVM guests use special exit events for trapping I/O instructions. Jan