- Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Wed, 11 Apr 2012 13:49:11 +0300
- Cc: zhangyanfei <zhangyanfei@xxxxxxxxxxxxxx>, mtosatti@xxxxxxxxxx, ebiederm@xxxxxxxxxxxx, luto@xxxxxxx, dzickus@xxxxxxxxxx, paul.gortmaker@xxxxxxxxxxxxx, gregkh@xxxxxxx, ludwig.nussel@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx
- In-reply-to: <20120411102136.GG2428@amd.com>
- References: <4F84E0DF.8040206@cn.fujitsu.com> <20120411102136.GG2428@amd.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120316 Thunderbird/11.0
On 04/11/2012 01:21 PM, Joerg Roedel wrote:
> Hi,
>
> 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?
He's determining the layout at runtime. It should even work with kvm's
vmx implementation.
It's vulnerable to two issues:
- fields that are cached in the processor and not flushed to memory
(perhaps just make sure to VMXOFF before dumping memory)
- fields that are encoded differently in memory than VMREAD/VMWRITE
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Linux Kernel]
[Linux SCSI]
[XFree86]