[PATCH 0/4] Export offsets of VMCS fields as note information for kdump
zhangyanfei at cn.fujitsu.com
Wed Apr 11 06:59:46 EDT 2012
于 2012年04月11日 18:21, Joerg Roedel 写道:
> On Wed, Apr 11, 2012 at 09:39:43AM +0800, zhangyanfei wrote:
>> The problem is that VMCS internal is hidden by Intel in its
>> specification. So, we reverse engineering it in the way implemented in
>> this patch set.
> Have you made sure this layout is the same on all uarchitectures that
> implment VMX?
The layout differs from each other in different VMCS revision identifiers.
The VMCS revision identifier is contained at the first 32 bits of the VMCS
region. And the VMCS revision identifiers may differ from different architectures.
for example, there are two processors below:
Processor 1: Intel(R) Xeon(R) CPU E7540 @ 2.00GHz with 24 cores
FIELD(VM_EXIT_CONTROLS) = 057c0578
Processor 2: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz
FIELD(VM_EXIT_CONTROLS) = 01e401e0
The purpose to get the VMCSINFO of one architecture is for guest debugging that was
running on the same architecture, so there is no problem the layouts differ from different
More information about the kexec