This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] RE: [VTD-NEO][patch 6/6] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
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
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <13A2F7DE1BAEA345A61DD40F303ED7A6813446@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
User-agent: Microsoft-Entourage/
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