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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

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

from [Keir Fraser] [Permanent Link][Original]
To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, "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 11:02:01 +0100
Delivery-date: Tue, 12 Sep 2006 03:00:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C12C4214.11FF%Keir.Fraser@xxxxxxxxxxxx>
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: AcbWT5jsidfVUI6ZSymoMuYZeVAv0AAAacB3AABPbVs=
Thread-topic: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code
User-agent: Microsoft-Entourage/11.2.5.060620
Actually I looked closer and you always make yourself look like a P4/Xeon APIC. So the correct phys broadcast id is always 0xFF for the virtual LAPIC. You shouldn’t check for 0xF. Right?

 -- Keir

On 12/9/06 10:53, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:

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

 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [Xen-devel] 32E (64bit) VMX keyboard is out of control, ifgiven an addition 'hde', You, Yongkang
Next by Date:  RE: [Xen-devel] 32E (64bit) VMX keyboard is out of control, ifgiven an addition 'hde', Ian Pratt
Previous by Thread:  Re: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code, Keir Fraser
Next by Thread:  RE: [Xen-devel][PATCH][RESEND]Add broadcast destination for physical destinationmode in LAPIC virtualization code, Xin, Xiaohui
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy