WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical des

To: "Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code
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
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <9A1462408D6D394C8A7A812E98F00A4D0E5338@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: AcbWT5jsidfVUI6ZSymoMuYZeVAv0AAAacB3
Thread-topic: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code
User-agent: Microsoft-Entourage/11.2.5.060620
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