From: Daniel Li <dli@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: vmcs_revision_id: do we care?
Date: Tue, 08 Jan 2008 17:40:17 -0500 [thread overview]
Message-ID: <4783FBD1.9020002@virtualiron.com> (raw)
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?
next reply other threads:[~2008-01-08 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 22:40 Daniel Li [this message]
2008-01-08 22:48 ` vmcs_revision_id: do we care? Keir Fraser
2008-01-09 16:13 ` Daniel Li
2008-01-09 16:18 ` Samuel Thibault
2008-01-09 19:25 ` Keir Fraser
2008-01-10 18:08 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4783FBD1.9020002@virtualiron.com \
--to=dli@virtualiron.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.