From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 2/5] kvm/svm: enhance MOV CR intercept handler
Date: Mon, 13 Dec 2010 14:13:40 +0200 [thread overview]
Message-ID: <4D060DF4.8000108@redhat.com> (raw)
In-Reply-To: <1291989088-1380-3-git-send-email-andre.przywara@amd.com>
On 12/10/2010 03:51 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 | 91 ++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 82 insertions(+), 11 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
> @@ -256,6 +256,8 @@ struct __attribute__ ((__packed__)) vmcb {
> #define SVM_EXITINFOSHIFT_TS_REASON_JMP 38
> #define SVM_EXITINFOSHIFT_TS_HAS_ERROR_CODE 44
>
> +#define SVM_EXITINFO_REG_MASK 0x0F
> +
> #define SVM_EXIT_READ_CR0 0x000
> #define SVM_EXIT_READ_CR3 0x003
> #define SVM_EXIT_READ_CR4 0x004
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index 298ff79..ee5f100 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -2594,12 +2594,81 @@ static int emulate_on_interception(struct vcpu_svm *svm)
> return emulate_instruction(&svm->vcpu, 0, 0, 0) == EMULATE_DONE;
> }
>
> +static int cr_interception(struct vcpu_svm *svm)
> +{
> + int reg, cr;
> + unsigned long val;
> + int err;
> +
> + if (!static_cpu_has(X86_FEATURE_DECODEASSISTS))
> + return emulate_on_interception(svm);
> +
> + /* bit 63 is the valid bit, as not all instructions (like lmsw)
> + provide the information */
Please use kernel style comments:
/*
* text
* text
*/
Even better, use a name for the bit, which will obviate the need for a
comment.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-13 12:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 13:51 [PATCH -v2 0/5] kvm/svm: implement new DecodeAssist features Andre Przywara
2010-12-10 13:51 ` [PATCH 1/5] kvm/svm: add new SVM feature bit names 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 [this message]
2010-12-20 11:56 ` Marcelo Tosatti
2010-12-20 13:20 ` Andre Przywara
2010-12-10 13:51 ` [PATCH 3/5] kvm/svm: enhance mov DR " Andre Przywara
2010-12-13 12:14 ` Avi Kivity
2010-12-16 12:07 ` Andre Przywara
2010-12-16 12:48 ` Avi Kivity
2010-12-10 13:51 ` [PATCH 4/5] kvm/svm: implement enhanced INVLPG intercept Andre Przywara
2010-12-10 13:51 ` [PATCH 5/5] kvm/svm: copy instruction bytes from VMCB Andre Przywara
2010-12-13 12:24 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2010-12-07 10:59 [PATCH 0/5] kvm/svm: implement new DecodeAssist features 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
2010-12-07 14:41 ` 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=4D060DF4.8000108@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.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