From: Avi Kivity <avi@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH 2/3] KVM: SVM: Restore correct registers after sel_cr0 intercept emulation
Date: Sun, 05 Sep 2010 10:09:14 +0300 [thread overview]
Message-ID: <4C83421A.7070501@redhat.com> (raw)
In-Reply-To: <20100902162934.GD1964@amd.com>
On 09/02/2010 07:29 PM, Roedel, Joerg wrote:
>
>> I agree. We can probably use X86EMUL_PROPAGATE_FAULT to abort
>> emulation, but looking at the code, it will take some refactoring.
> I thought of an X86EMUL_INTERCEPTED. An architecture specific function
> is called after instruction decoding which checks if an intercept is
> necessary. If it returns X86EMUL_INTERCEPTED then the instruction
> emulation is discarded and kvm goes straight back into the guest.
Yes, this sounds just right.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-09-05 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 15:29 [PATCH 0/3] KVM fixes and cleanups Joerg Roedel
2010-09-02 15:29 ` [PATCH 1/3] KVM: MMU: Fix 32 bit legacy paging with NPT Joerg Roedel
2010-09-02 15:56 ` Avi Kivity
2010-09-02 16:32 ` Roedel, Joerg
2010-09-02 15:29 ` [PATCH 2/3] KVM: SVM: Restore correct registers after sel_cr0 intercept emulation Joerg Roedel
2010-09-02 16:02 ` Avi Kivity
2010-09-02 16:29 ` Roedel, Joerg
2010-09-05 7:09 ` Avi Kivity [this message]
2010-09-02 15:29 ` [PATCH 3/3] KVM: SVM: Clean up rip handling in vmrun emulation Joerg Roedel
2010-09-03 12:21 ` Roedel, Joerg
2010-09-03 21:29 ` Alexander Graf
2010-09-04 19:32 ` Joerg Roedel
2010-09-06 18:26 ` [PATCH 0/3] KVM fixes and cleanups Marcelo Tosatti
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=4C83421A.7070501@redhat.com \
--to=avi@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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