[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 10:30:49 +0100
  • Delivery-date: Thu, 20 Sep 2007 02:31:35 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfvUQE/NSLHf0ZTRFaUb5meDjaqbALsHd9QABfyc/cAAerY8g==
  • Thread-topic: [Xen-devel] RE: [VTD-NEO][patch 6/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough



On 20/9/07 09:35, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> 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?

I checked in everything except the extra invocation of iommu_domain_init().
I want to understand what iommu_domain_init() and release_devices() do
before deciding whether to move their invocations.

 -- 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®.