From: Andre Przywara <andre.przywara@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCH 2/5] kvm/svm: enhance MOV CR intercept handler
Date: Tue, 7 Dec 2010 15:30:06 +0100 [thread overview]
Message-ID: <4CFE44EE.7000807@amd.com> (raw)
In-Reply-To: <4CFE3581.20305@redhat.com>
Avi Kivity wrote:
> On 12/07/2010 12:59 PM, Andre Przywara wrote:
>> Newer SVM implementations provide the GPR number in the VMCB, so
>> that the emulation path is no longer necesarry to handle CR
>> register access intercepts. Implement the handling in svm.c and
>> use it when the info is provided.
>>
>> Signed-off-by: Andre Przywara<andre.przywara@amd.com>
>> ---
>> arch/x86/include/asm/svm.h | 2 +
>> arch/x86/kvm/svm.c | 74 +++++++++++++++++++++++++++++++++++++++-----
>> 2 files changed, 68 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/svm.h b/arch/x86/include/asm/svm.h
>> index 11dbca7..589fc25 100644
>> --- a/arch/x86/include/asm/svm.h
>> +++ b/arch/x86/include/asm/svm.h
>> ...
>> @@ -2864,14 +2922,14 @@ static int pause_interception(struct vcpu_svm *svm)
>> }
>>
>> static int (*svm_exit_handlers[])(struct vcpu_svm *svm) = {
>> - [SVM_EXIT_READ_CR0] = emulate_on_interception,
>> - [SVM_EXIT_READ_CR3] = emulate_on_interception,
>> - [SVM_EXIT_READ_CR4] = emulate_on_interception,
>> - [SVM_EXIT_READ_CR8] = emulate_on_interception,
>> + [SVM_EXIT_READ_CR0] = cr_interception,
>> + [SVM_EXIT_READ_CR3] = cr_interception,
>> + [SVM_EXIT_READ_CR4] = cr_interception,
>> + [SVM_EXIT_READ_CR8] = cr_interception,
>> [SVM_EXIT_CR0_SEL_WRITE] = emulate_on_interception,
>> [SVM_EXIT_WRITE_CR0] = cr0_write_interception,
>> - [SVM_EXIT_WRITE_CR3] = emulate_on_interception,
>> - [SVM_EXIT_WRITE_CR4] = emulate_on_interception,
>> + [SVM_EXIT_WRITE_CR3] = cr_interception,
>> + [SVM_EXIT_WRITE_CR4] = cr_interception,
>> [SVM_EXIT_WRITE_CR8] = cr8_write_interception,
>
> We could move cr[08]_write_interception into cr_interception, but that
> takes a bit more thought. Best done later.
Yes, I thought about that, too. But since we still have to deal with the
emulation code path, it would not make the code easier. But if we
overwrite the svm_exit_handlers[] on detecting the SVM feature, this
could make more sense. I will check this out.
Thanks for the review, I will address your comments.
Regards,
Andre.
next prev parent reply other threads:[~2010-12-07 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 10:59 [PATCH 0/5] kvm/svm: implement new DecodeAssist features Andre Przywara
2010-12-07 10:59 ` [PATCH 1/5] kvm/svm: add new SVM feature bit names Andre Przywara
2010-12-07 10:59 ` [PATCH 2/5] kvm/svm: enhance MOV CR intercept handler Andre Przywara
2010-12-07 13:24 ` Avi Kivity
2010-12-07 14:30 ` Andre Przywara [this message]
2010-12-07 14:41 ` Avi Kivity
2010-12-07 10:59 ` [PATCH 3/5] kvm/svm: enhance mov DR " Andre Przywara
2010-12-07 11:02 ` Alexander Graf
2010-12-07 13:14 ` Avi Kivity
2010-12-07 13:25 ` Avi Kivity
2010-12-07 10:59 ` [PATCH 4/5] kvm/svm: implement enhanced INVLPG intercept Andre Przywara
2010-12-07 13:27 ` Avi Kivity
2010-12-07 10:59 ` [PATCH 5/5] kvm/svm: copy instruction bytes from VMCB Andre Przywara
2010-12-07 13:33 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2010-12-10 13:51 [PATCH -v2 0/5] kvm/svm: implement new DecodeAssist features Andre Przywara
2010-12-10 13:51 ` [PATCH 2/5] kvm/svm: enhance MOV CR intercept handler Andre Przywara
2010-12-13 12:13 ` Avi Kivity
2010-12-20 11:56 ` Marcelo Tosatti
2010-12-20 13:20 ` Andre Przywara
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=4CFE44EE.7000807@amd.com \
--to=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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