[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] RE: [VTD-NEO][patch 6/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough


  • To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 20 Sep 2007 09:35:55 +0100
  • Delivery-date: Thu, 20 Sep 2007 01:36:38 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfvUQE/NSLHf0ZTRFaUb5meDjaqbALsHd9QABfyc/c=
  • Thread-topic: [Xen-devel] RE: [VTD-NEO][patch 6/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough

On 19/9/07 22:21, "Kay, Allen M" <allen.m.kay@xxxxxxxxx> wrote:

> dom0.patch: create vt-d 1:1 mapping for dom0; call iommu_domain_init()
> in domain.c.

Do PV guests actually need per-domain iommu state? If they do, isn't
release_devices() the partnering destructor function, and so should that not
be invoked from domain.c too?

> These changes were tested against 15909.  The changes made by cs# 15910
> breaks even non-vtd vmx guest bring-up.  It causes xen crash complaining
> about:
> 
>  "(XEN) Failed vm entry (exit reason 0x80000021) caused by invalid guest
> state (0)"

How is the guest state broken? Does guest rflags have bit 1 set?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.