From: "Li,Rongqing" <lirongqing@baidu.com>
To: Sean Christopherson <seanjc@google.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"joro@8bytes.org" <joro@8bytes.org>
Subject: 答复: [PATCH] KVM: x86: fix kvm_vcpu_is_preempted
Date: Thu, 13 Jan 2022 08:06:12 +0000 [thread overview]
Message-ID: <f0be007a87494a9bb645fedc433e9310@baidu.com> (raw)
In-Reply-To: <Yd8FO8O9AQa79sFc@google.com>
> -----邮件原件-----
> 发件人: Sean Christopherson <seanjc@google.com>
> 发送时间: 2022年1月13日 0:44
> 收件人: Li,Rongqing <lirongqing@baidu.com>
> 抄送: pbonzini@redhat.com; vkuznets@redhat.com; wanpengli@tencent.com;
> jmattson@google.com; tglx@linutronix.de; mingo@redhat.com; bp@alien8.de;
> x86@kernel.org; hpa@zytor.com; rkrcmar@redhat.com; kvm@vger.kernel.org;
> joro@8bytes.org
> 主题: Re: [PATCH] KVM: x86: fix kvm_vcpu_is_preempted
>
> On Wed, Jan 12, 2022, Li RongQing wrote:
> > After support paravirtualized TLB shootdowns, steal_time.preempted
> > includes not only KVM_VCPU_PREEMPTED, but also KVM_VCPU_FLUSH_TLB
> >
> > and kvm_vcpu_is_preempted should test only with KVM_VCPU_PREEMPTED
> >
> > Fixes: 858a43aae2367 ("KVM: X86: use paravirtualized TLB Shootdown")
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > ---
> > arch/x86/kernel/kvm.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c index
> > 59abbda..a9202d9 100644
> > --- a/arch/x86/kernel/kvm.c
> > +++ b/arch/x86/kernel/kvm.c
> > @@ -1025,8 +1025,8 @@ asm(
> > ".type __raw_callee_save___kvm_vcpu_is_preempted, @function;"
> > "__raw_callee_save___kvm_vcpu_is_preempted:"
> > "movq __per_cpu_offset(,%rdi,8), %rax;"
> > -"cmpb $0, " __stringify(KVM_STEAL_TIME_preempted) "+steal_time(%rax);"
> > -"setne %al;"
> > +"movb " __stringify(KVM_STEAL_TIME_preempted)
> "+steal_time(%rax), %al;"
> > +"andb $" __stringify(KVM_VCPU_PREEMPTED) ", %al;"
>
> Eww, the existing code is sketchy. It relies on the compiler to store _Bool/bool
> in a single byte since %rax may be non-zero from the __per_cpu_offset(), and
> modifying %al doesn't zero %rax[63:8]. I doubt gcc or clang use anything but a
> single byte on x86-64, but "andl" is just as cheap so I don't see any harm in being
> paranoid.
>
Build with gcc (GCC) 7.3.0, disassembled as blow
before:
ffffffff8105bdc0 <__raw_callee_save___kvm_vcpu_is_preempted>:
ffffffff8105bdc0: 48 8b 04 fd c0 16 1d mov -0x7de2e940(,%rdi,8),%rax
ffffffff8105bdc7: 82
ffffffff8105bdc8: 80 b8 90 c0 02 00 00 cmpb $0x0,0x2c090(%rax)
ffffffff8105bdcf: 0f 95 c0 setne %al
ffffffff8105bdd2: c3 retq
ffffffff8105bdd3: 0f 1f 00 nopl (%rax)
ffffffff8105bdd6: 66 2e 0f 1f 84 00 00 nopw %cs:0x0(%rax,%rax,1)
ffffffff8105bddd: 00 00 00
after:
ffffffff8105bdc0 <__raw_callee_save___kvm_vcpu_is_preempted>:
ffffffff8105bdc0: 48 8b 04 fd c0 16 1d mov -0x7de2e940(,%rdi,8),%rax
ffffffff8105bdc7: 82
ffffffff8105bdc8: 8a 80 90 c0 02 00 mov 0x2c090(%rax),%al
ffffffff8105bdce: 24 01 and $0x1,%al
ffffffff8105bdd0: c3 retq
ffffffff8105bdd1: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
ffffffff8105bdd6: 66 2e 0f 1f 84 00 00 nopw %cs:0x0(%rax,%rax,1)
ffffffff8105bddd: 00 00 00
Thanks
-Li
next prev parent reply other threads:[~2022-01-13 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:19 [PATCH] KVM: x86: fix kvm_vcpu_is_preempted Li RongQing
2022-01-12 16:43 ` Sean Christopherson
2022-01-13 8:06 ` Li,Rongqing [this message]
2022-01-13 10:00 ` Peter Zijlstra
2022-01-13 11:03 ` Paolo Bonzini
2022-01-14 9:49 ` 答复: " Li,Rongqing
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=f0be007a87494a9bb645fedc433e9310@baidu.com \
--to=lirongqing@baidu.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.