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] [PATCH] Fix dom0 boot issue with VT-d enabled

To: "Han, Weidong" <weidong.han@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix dom0 boot issue with VT-d enabled
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 22 Apr 2008 09:56:05 +0100
Cc: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Delivery-date: Tue, 22 Apr 2008 01:56:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <08DF4D958216244799FC84F3514D70F00145BE71@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: AcikPaLRnC/jEA6mQyKQReF5XbGl0AAGQ+/H
Thread-topic: [Xen-devel] [PATCH] Fix dom0 boot issue with VT-d enabled
User-agent: Microsoft-Entourage/
On 22/4/08 06:56, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:

> c/s 17487 put iommu_setup() in __initcall(), this makes iommu_setup() be
> called before dom0 creation. Because iommu_setup() will do something for
> dom0 such as map 1:1 page table, while dom0 is NULL, reboot happens
> during dom0 booting. This patch moves iommu_setup() behind dom0
> creation.

The code for system and domain initialisation of iommu state is a
disgraceful mess. The former should be done early, before domains (including
dom0) are created. If you have stuff to do for dom0, do it when dom0 is
created. You get a call into your code at that point.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>