From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"'Keir.Fraser@eu.citrix.com'" <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] VT-d: prevent dom0 to use VT-d HW
Date: Wed, 09 Sep 2009 15:32:08 -0700 [thread overview]
Message-ID: <4AA82CE8.1040106@goop.org> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C054B5B4A8A@pdsmsx503.ccr.corp.intel.com>
On 09/07/09 19:24, Han, Weidong wrote:
> pv-ops dom0 contains Linux upstream VT-d driver, and will go to enable it when VT-d is set in kernel config file. It should not enable VT-d in dom0.
>
> Currently it already zaps ACPI DMAR signature to prevents dom0 using VT-d HW when VT-d is enabled for Xen. But when VT-d is not enabled for Xen, and VT-d is set in pv-ops kernel config file, pv-ops dom0 will go to enable it. This will results in pv-ops dom0 booting failure. This patch prevents dom0 to use VT-d HW whether VT-d is enabled or disabled for Xen.
>
Which tree is this against? My dom0 tree doesn't have
drivers/passthrough/vtd/. Is there a branch you'd like me to pull in?
Thanks,
J
next prev parent reply other threads:[~2009-09-09 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 2:24 [PATCH] VT-d: prevent dom0 to use VT-d HW Han, Weidong
2009-09-08 11:43 ` Christian Tramnitz
2009-09-08 11:51 ` Teo En Ming (Zhang Enming)
2009-09-08 14:07 ` Ian Jackson
2009-09-08 14:14 ` Keir Fraser
2009-09-09 22:32 ` Jeremy Fitzhardinge [this message]
2009-09-09 22:35 ` Kay, Allen M
2009-09-09 22:41 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA82CE8.1040106@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.