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

Re: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code


  • To: "Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 12 Sep 2006 10:53:08 +0100
  • Delivery-date: Tue, 12 Sep 2006 02:52:00 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbWT5jsidfVUI6ZSymoMuYZeVAv0AAAacB3
  • Thread-topic: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code

On 12/9/06 10:41, "Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx> wrote:

This patch adds broadcast destination for physical destination mode. Without this patch, HVM x64 Windows cannot install and boot
 
Signed-off-by: Xiaohui Xin <xiaohui.xin@xxxxxxxxx>

Do you need to support 0xF as broadcast dest? Are there VT chips that have a P6-style APIC? I’m just a little concerned that we may eventually use 0xF as an APIC ID, when we run VT guests with enough VCPUs. We could avoid that though.

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