[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [Patch] Remove a panic condition in enabling x2APIC


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: "Han, Weidong" <weidong.han@xxxxxxxxx>
  • Date: Fri, 12 Nov 2010 16:44:36 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
  • Delivery-date: Fri, 12 Nov 2010 00:45:28 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcuCRdXSIg3OXxWYSi609s60oaO2YQ==
  • Thread-topic: [Xen-devel] [Patch] Remove a panic condition in enabling x2APIC

Currently Xen triggers a panic if user disables VT-d by command line while not 
disable x2APIC. This requires users to specify both "iommu=0" and "x2apic=0" to 
disable VT-d if the platform supports x2APIC. It's not user friendly. This 
patch removes the panic condition. That's to say, don't require user to specify 
"x2apic=0" when specify "iommu=0". As long as VT-d is not enabled (disabled in 
BIOS or in command line), x2APIC won't be enabled naturally (x2APIC depends on 
VT-d Interrupt remapping). 

Signed-off-by: Weidong Han <weidong.han@xxxxxxxxx>

Attachment: remove-panic.patch
Description: remove-panic.patch

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