From: Liran Alon <LIRAN.ALON@ORACLE.COM>
To: Paolo Bonzini <pbonzini@redhat.com>, Wanpeng Li <kernellwp@gmail.com>
Cc: Radim Krcmar <rkrcmar@redhat.com>, kvm <kvm@vger.kernel.org>,
idan.brown@ORACLE.COM,
Konrad Rzeszutek Wilk <konrad.wilk@ORACLE.COM>,
"# v3 . 10+" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] KVM: x86: Exit to user-mode on #UD intercept when emulator requires
Date: Tue, 07 Nov 2017 16:13:42 +0200 [thread overview]
Message-ID: <5A01BF96.8080303@ORACLE.COM> (raw)
In-Reply-To: <bf28963b-f3b6-97e5-a48c-f3884c8a2bb1@redhat.com>
On 07/11/17 14:22, Paolo Bonzini wrote:
> On 07/11/2017 09:12, Liran Alon wrote:
>>
>>
>> On 07/11/17 02:47, Wanpeng Li wrote:
>>> 2017-11-06 22:39 GMT+08:00 Liran Alon <liran.alon@oracle.com>:
>>>> Signed-off-by: Liran Alon <liran.alon@oracle.com>
>>>> Reviewed-by: Nikita Leshenko <nikita.leshchenko@oracle.com>
>>>> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>>> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>>>> Cc: stable@vger.kernel.org
>>>
>>> Except the changelog.
>> Thanks for the review.
>> Currently both you and Paolo added "Reviewed-by" to this commit.
>>
>> Is there anything else you wish me to add to the commit message before
>> this commit being accepted? Do you have a suggestion? I though the
>> commit-title explains it enough for this trivial patch and didn't saw
>> any complain about not having body by ./scripts/checkpatch.pl.
>>
>> In addition, if I would need to edit commit message body, should I send
>> the next version of this commit as a standalone or re-send the entire
>> series?
>
> No, don't worry. Generally, when a maintainer adds a Reviewed-by it
> means that it's just a matter of time before the patch goes in.
>
> For the commit message, I was thinking of something like:
>
> ---
> Instruction emulation after trapping a #UD exception can result in an
> MMIO access, for example when emulating a MOVBE on a processor that
> doesn't support the instruction. In this case, the #UD vmexit handler
> must exit to user mode, but there wasn't any code to do so. Add it for
> both VMX and SVM.
> ---
>
> Sounds good?
Sounds good. Thanks.
So if I understood correctly, I leave it to you to insert the patch with
this commit message when it is inserted.
Thanks. :)
>
> Paolo
>
>> Thanks,
>> -Liran
>>
>>>
>>> Reviewed-by: Wanpeng Li <wanpeng.li@hotmail.com>
>>>
>>>> ---
>>>> arch/x86/kvm/svm.c | 2 ++
>>>> arch/x86/kvm/vmx.c | 2 ++
>>>> 2 files changed, 4 insertions(+)
>>>>
>>>> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>>>> index 0e68f0b3cbf7..e0162b20e3c9 100644
>>>> --- a/arch/x86/kvm/svm.c
>>>> +++ b/arch/x86/kvm/svm.c
>>>> @@ -2189,6 +2189,8 @@ static int ud_interception(struct vcpu_svm *svm)
>>>> int er;
>>>>
>>>> er = emulate_instruction(&svm->vcpu, EMULTYPE_TRAP_UD);
>>>> + if (er == EMULATE_USER_EXIT)
>>>> + return 0;
>>>> if (er != EMULATE_DONE)
>>>> kvm_queue_exception(&svm->vcpu, UD_VECTOR);
>>>> return 1;
>>>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>>>> index 95a01609d7ee..2b63d9edc207 100644
>>>> --- a/arch/x86/kvm/vmx.c
>>>> +++ b/arch/x86/kvm/vmx.c
>>>> @@ -5886,6 +5886,8 @@ static int handle_exception(struct kvm_vcpu *vcpu)
>>>> return 1;
>>>> }
>>>> er = emulate_instruction(vcpu, EMULTYPE_TRAP_UD);
>>>> + if (er == EMULATE_USER_EXIT)
>>>> + return 0;
>>>> if (er != EMULATE_DONE)
>>>> kvm_queue_exception(vcpu, UD_VECTOR);
>>>> return 1;
>>>> --
>>>> 1.9.1
>>>>
>
prev parent reply other threads:[~2017-11-07 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1509979184-31964-1-git-send-email-liran.alon@oracle.com>
2017-11-06 14:39 ` [PATCH v2 1/3] KVM: x86: Exit to user-mode on #UD intercept when emulator requires Liran Alon
2017-11-06 14:47 ` Greg KH
2017-11-06 14:50 ` Paolo Bonzini
2017-11-06 15:07 ` Greg KH
2017-11-06 15:19 ` Paolo Bonzini
2017-11-07 0:47 ` Wanpeng Li
2017-11-07 8:12 ` Liran Alon
2017-11-07 12:22 ` Paolo Bonzini
2017-11-07 14:13 ` Liran Alon [this message]
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=5A01BF96.8080303@ORACLE.COM \
--to=liran.alon@oracle.com \
--cc=idan.brown@ORACLE.COM \
--cc=kernellwp@gmail.com \
--cc=konrad.wilk@ORACLE.COM \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).