From: Andre Przywara <andre.przywara@amd.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: "avi@redhat.com" <avi@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm/svm: fix DR interception handling on upcoming AMD CPUs
Date: Wed, 9 Feb 2011 11:43:28 +0100 [thread overview]
Message-ID: <4D526FD0.8000802@amd.com> (raw)
In-Reply-To: <20110209100115.GB26519@amd.com>
Roedel, Joerg wrote:
> On Tue, Feb 08, 2011 at 07:22:29PM -0500, Andre Przywara wrote:
>> Somehow the code line advancing the RIP and checking for exceptions
>> got dropped between the post on the ML and the commit.
>> Add it again to let guests boot on upcoming AMD CPUs again.
>>
>> Reported-by: Joerg Roedel <joerg.roedel@amd.com>
>> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
>> ---
>> arch/x86/kvm/svm.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>> index 25bd1bc..be06e58 100644
>> --- a/arch/x86/kvm/svm.c
>> +++ b/arch/x86/kvm/svm.c
>> @@ -2776,6 +2776,7 @@ static int dr_interception(struct vcpu_svm *svm)
>> if (!err)
>> kvm_register_write(&svm->vcpu, reg, val);
>> }
>> + kvm_complete_insn_gp(&svm->vcpu, err);
>
> Any exception check takes presedence over the intercept. So a call to
> skip_emulated_instruction should be sufficient here.
You are right, but I think this way the implementation is cleaner and
more generic. If there is no exception condition detected (err==0), then
the call will just do skip_emulated_instruction anyway.
But as I write this, I see that err is not initialized, so I'd propose
this corrected version of the patch instead.
Regards,
Andre.
--
From 8c1dced7b4f80e4968b03656aee2452535b2ef2f Mon Sep 17 00:00:00 2001
From: Andre Przywara <andre.przywara@amd.com>
Date: Wed, 9 Feb 2011 01:10:45 +0100
Subject: [PATCH] kvm/svm: fix DR interception handling on upcoming AMD CPUs
Somehow the code line advancing the RIP and checking for exceptions
got dropped between the mail on the ML and the commit.
Add it again to let guests boot on upcoming AMD CPUs again.
While at it, properly initialize the err variable to fix the write DR
case.
Reported-by: Joerg Roedel <joerg.roedel@amd.com>
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
---
arch/x86/kvm/svm.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 25bd1bc..d558121 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -2760,7 +2760,7 @@ static int dr_interception(struct vcpu_svm *svm)
{
int reg, dr;
unsigned long val;
- int err;
+ int err = 0;
if (!boot_cpu_has(X86_FEATURE_DECODEASSISTS))
return emulate_on_interception(svm);
@@ -2776,6 +2776,7 @@ static int dr_interception(struct vcpu_svm *svm)
if (!err)
kvm_register_write(&svm->vcpu, reg, val);
}
+ kvm_complete_insn_gp(&svm->vcpu, err);
return 1;
}
--
1.6.4
next prev parent reply other threads:[~2011-02-09 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:22 [PATCH] kvm/svm: fix DR interception handling on upcoming AMD CPUs Andre Przywara
2011-02-09 10:01 ` Roedel, Joerg
2011-02-09 10:43 ` Andre Przywara [this message]
2011-02-09 12:56 ` Roedel, Joerg
2011-02-09 13:39 ` 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=4D526FD0.8000802@amd.com \
--to=andre.przywara@amd.com \
--cc=Joerg.Roedel@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