From: "Chao Du" <duchao@eswincomputing.com>
To: "Daniel Henrique Barboza" <dbarboza@ventanamicro.com>
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
anup@brainfault.org, atishp@atishpatra.org
Subject: Re: [PATCH] RISC-V: KVM: remove a redundant condition in kvm_arch_vcpu_ioctl_run()
Date: Tue, 12 Dec 2023 15:12:22 +0800 (GMT+08:00) [thread overview]
Message-ID: <4840760d.ce9.18c5cde9e56.Coremail.duchao@eswincomputing.com> (raw)
In-Reply-To: <94bcaa6d-fe18-4eed-b2d4-a6a5521230bf@ventanamicro.com>
> -----Original Messages-----From:"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>Sent Time:2023-12-11 20:06:33 (Monday)To:"Chao Du" <duchao@eswincomputing.com>, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, anup@brainfault.org, atishp@atishpatra.orgCc:Subject:Re: [PATCH] RISC-V: KVM: remove a redundant condition in kvm_arch_vcpu_ioctl_run()
>
>
>
> On 12/11/23 06:40, Chao Du wrote:
> > The latest ret value is updated by kvm_riscv_vcpu_aia_update(),
> > the loop will continue if the ret is less than or equal to zero.
> > So the later condition will never hit. Thus remove it.
>
> Good catch. There's another potential optimization to be done a little above
> this change:
>
>
> while (ret > 0) {
> (...)
>
> /* Update AIA HW state before entering guest */
> ret = kvm_riscv_vcpu_aia_update(vcpu);
> if (ret <= 0) {
> preempt_enable();
> continue; <------------------
> }
> (...)
>
> Note that this 'continue' isn't doing much - we'll restart the loop with ret <= 0
> while requiring ret > 0 to do another iteration. I.e. this 'continue' can be
> replaced for 'break' without compromising the logic.
Yes, you are right. The 'continue' could be replaced by a 'break'.
I also find another small point:
ret = 1;
(...)
/* Update AIA HW state before entering guest */
ret = kvm_riscv_vcpu_aia_update(vcpu);
the assignment 'ret = 1' is somehow redundant, since it will be
overwritten before any reference.
>
> (of course, testing it to be sure is always advised :D )
>
> >
> > Signed-off-by: Chao Du <duchao@eswincomputing.com>
> > ---
>
>
> Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
>
>
> > arch/riscv/kvm/vcpu.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/arch/riscv/kvm/vcpu.c b/arch/riscv/kvm/vcpu.c
> > index e087c809073c..bf3952d1a621 100644
> > --- a/arch/riscv/kvm/vcpu.c
> > +++ b/arch/riscv/kvm/vcpu.c
> > @@ -757,8 +757,7 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu)
> > /* Update HVIP CSR for current CPU */
> > kvm_riscv_update_hvip(vcpu);
> >
> > - if (ret <= 0 ||
> > - kvm_riscv_gstage_vmid_ver_changed(&vcpu->kvm->arch.vmid) ||
> > + if (kvm_riscv_gstage_vmid_ver_changed(&vcpu->kvm->arch.vmid) ||
> > kvm_request_pending(vcpu) ||
> > xfer_to_guest_mode_work_pending()) {
> > vcpu->mode = OUTSIDE_GUEST_MODE;
next prev parent reply other threads:[~2023-12-12 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 9:40 [PATCH] RISC-V: KVM: remove a redundant condition in kvm_arch_vcpu_ioctl_run() Chao Du
2023-12-11 12:06 ` Daniel Henrique Barboza
2023-12-12 7:12 ` Chao Du [this message]
2023-12-13 12:22 ` Anup Patel
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=4840760d.ce9.18c5cde9e56.Coremail.duchao@eswincomputing.com \
--to=duchao@eswincomputing.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=dbarboza@ventanamicro.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@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