From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: zhangyanfei <zhangyanfei@cn.fujitsu.com>,
mtosatti@redhat.com, ebiederm@xmission.com, luto@mit.edu,
dzickus@redhat.com, paul.gortmaker@windriver.com, gregkh@suse.de,
ludwig.nussel@suse.de, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump
Date: Wed, 11 Apr 2012 13:49:11 +0300 [thread overview]
Message-ID: <4F8561A7.80604@redhat.com> (raw)
In-Reply-To: <20120411102136.GG2428@amd.com>
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
next prev parent reply other threads:[~2012-04-11 10:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 1:39 [PATCH 0/4] Export offsets of VMCS fields as note information for kdump zhangyanfei
2012-04-11 1:49 ` [PATCH 1/4] x86: Add helper variables and functions to hold VMCSINFO zhangyanfei
2012-04-11 1:50 ` [PATCH 2/4] KVM: VMX: Add functions to fill VMCSINFO zhangyanfei
2012-04-11 8:48 ` Avi Kivity
2012-04-11 10:34 ` zhangyanfei
2012-04-11 11:41 ` Avi Kivity
2012-04-11 1:57 ` [PATCH 3/4] ksysfs: export VMCSINFO via sysfs zhangyanfei
2012-04-12 23:00 ` Greg KH
2012-04-17 1:52 ` zhangyanfei
2012-04-17 2:30 ` Greg KH
2012-04-11 1:58 ` [PATCH 4/4] kexec: Add crash_save_vmcsinfo to update VMCSINFO zhangyanfei
2012-04-11 8:56 ` [PATCH 0/4] Export offsets of VMCS fields as note information for kdump Avi Kivity
2012-04-11 10:12 ` zhangyanfei
2012-04-11 11:15 ` Avi Kivity
2012-04-11 10:21 ` Joerg Roedel
2012-04-11 10:49 ` Avi Kivity [this message]
2012-04-11 10:59 ` zhangyanfei
2012-04-17 7:44 ` Avi Kivity
2012-04-17 10:51 ` zhangyanfei
2012-04-17 10:59 ` Avi Kivity
2012-04-17 11:25 ` Wen Congyang
2012-04-17 13:04 ` Avi Kivity
2012-04-18 7:30 ` zhangyanfei
2012-04-18 8:24 ` Avi Kivity
2012-04-18 9:49 ` zhangyanfei
2012-04-18 11:56 ` Avi Kivity
2012-04-19 10:36 ` HATAYAMA Daisuke
2012-04-19 10:42 ` Avi Kivity
2012-04-19 11:27 ` HATAYAMA Daisuke
2012-04-19 11:31 ` Avi Kivity
2012-04-19 12:01 ` HATAYAMA Daisuke
2012-04-19 12:08 ` Avi Kivity
2012-04-20 10:11 ` HATAYAMA Daisuke
2012-04-22 9:58 ` Avi Kivity
2012-04-22 10:33 ` Gleb Natapov
2012-04-22 10:57 ` Avi Kivity
2012-04-17 16:49 ` Anthony Liguori
2012-04-18 12:13 ` Avi Kivity
2012-04-18 13:47 ` Nadav Har'El
2012-04-18 14:06 ` Avi Kivity
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=4F8561A7.80604@redhat.com \
--to=avi@redhat.com \
--cc=dzickus@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=joerg.roedel@amd.com \
--cc=kexec@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
--cc=luto@mit.edu \
--cc=mtosatti@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=zhangyanfei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).