From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] VT-d: prevent dom0 to use VT-d HW Date: Wed, 09 Sep 2009 15:32:08 -0700 Message-ID: <4AA82CE8.1040106@goop.org> References: <715D42877B251141A38726ABF5CABF2C054B5B4A8A@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <715D42877B251141A38726ABF5CABF2C054B5B4A8A@pdsmsx503.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Han, Weidong" Cc: "xen-devel@lists.xensource.com" , "Kay, Allen M" , "'Keir.Fraser@eu.citrix.com'" List-Id: xen-devel@lists.xenproject.org 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