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] vmcs_revision_id: do we care?

To: Daniel Li <dli@xxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] vmcs_revision_id: do we care?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 08 Jan 2008 22:48:40 +0000
Delivery-date: Tue, 08 Jan 2008 14:49:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4783FBD1.9020002@xxxxxxxxxxxxxxx>
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: AchSSJyw20Gmi747EdytVwAWy6hiGQ==
Thread-topic: [Xen-devel] vmcs_revision_id: do we care?
User-agent: Microsoft-Entourage/11.3.6.070618
No, we'll simply fail a VMPTRLD the first time we load a VMCS onto a
different processor than the one it was initialised on. This configuration
is actually quite hard to support and I don't see that it's worth it (even
though I know there are a few boxes from a certain tier-1 vendor out there
exhibiting this issue). It's really not a valid SMP system configuration.

 -- Keir

On 8/1/08 22:40, "Daniel Li" <dli@xxxxxxxxxxxxxxx> wrote:

> Right now when xen finds out a SMP host has processors with different
> vmcs_revision_id, it considers it a bug.
> 
> xen/arch/x86/hvm/vmx/vmcs.c:vmx_init_vmcs_config():
> 
> rdmsr(MSR_IA32_VMX_BASIC_MSR, vmx_msr_low, vmx_msr_high);
> 
> if ( smp_processor_id() == 0 )
> {
>     vmcs_revision_id = vmx_msr_low;
> }
> else
> {
>     BUG_ON(vmcs_revision_id != vmx_msr_low);
> }
> 
> Does anyone know why are we doing this? Can we change that check into a
> warning message?
> 
> _______________________________________________
> 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