From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] KVM: SVM: Fix fault-rip on vmsave/vmload emulation
Date: Wed, 06 Apr 2011 14:21:00 +0300 [thread overview]
Message-ID: <4D9C4C9C.6060401@redhat.com> (raw)
In-Reply-To: <1302085803-25399-1-git-send-email-joerg.roedel@amd.com>
On 04/06/2011 01:30 PM, Joerg Roedel wrote:
> When the emulation of vmload or vmsave fails because the
> guest passed an unsupported physical address it gets an #GP
> with rip pointing to the instruction after vmsave/vmload.
> This is a bug and fixed by this patch.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-06 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 10:30 [PATCH] KVM: SVM: Fix fault-rip on vmsave/vmload emulation Joerg Roedel
2011-04-06 11:21 ` Avi Kivity [this message]
2011-04-06 11:28 ` Avi Kivity
2011-04-06 12:27 ` Roedel, Joerg
2011-04-06 12:43 ` Avi Kivity
2011-04-06 13:13 ` Roedel, Joerg
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=4D9C4C9C.6060401@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=stable@kernel.org \
/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