Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: 项文成 <xiangwencheng@lanxincomputing.com>
Cc: "kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
	 "anup@brainfault.org" <anup@brainfault.org>,
	"atishp@atishpatra.org" <atishp@atishpatra.org>,
	 "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
	"palmer@dabbelt.com" <palmer@dabbelt.com>,
	 "aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	 "linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: KVM: Remove unnecessary vcpu kick
Date: Tue, 18 Feb 2025 18:48:41 +0100	[thread overview]
Message-ID: <20250218-57a3a16e477f83a8c267d120@orel> (raw)
In-Reply-To: <38cc241c40a8ef2775e304d366bcd07df733ecf0.1d66512d.85e4.41a5.8cf7.4c1fdb05d775@feishu.cn>

On Tue, Feb 18, 2025 at 04:00:24PM +0800, 项文成 wrote:
> From 30dd00f6886119ecc5c39b6b88f8617a57e598fc Mon Sep 17 00:00:00 2001
> From: BillXiang <xiangwencheng@lanxincomputing.com>
> Date: Tue, 18 Feb 2025 15:45:52 +0800
> Subject: [PATCH] riscv: KVM: Remove unnecessary vcpu kick
> 
> Hello everyone,
> I'm wondering whether it's necessary to kick the virtual hart
> after writing to the vsfile of IMSIC.
> From my understanding, writing to the vsfile should directly
> forward the interrupt as MSI to the virtual hart. This means that
> an additional kick should not be necessary, as it would cause the
> vCPU to exit unnecessarily and potentially degrade performance.
> I've tested this behavior in QEMU, and it seems to work perfectly
> fine without the extra kick.
> Would appreciate any insights or confirmation on this!
> Best regards.

The above should be in a cover letter so the commit message can
be written following the guidelines of [1]

[1] Documentation/process/submitting-patches.rst

> 
> Signed-off-by: BillXiang <xiangwencheng@lanxincomputing.com>
> ---
>  arch/riscv/kvm/aia_imsic.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/riscv/kvm/aia_imsic.c b/arch/riscv/kvm/aia_imsic.c
> index a8085cd8215e..29ef9c2133a9 100644
> --- a/arch/riscv/kvm/aia_imsic.c
> +++ b/arch/riscv/kvm/aia_imsic.c
> @@ -974,7 +974,6 @@ int kvm_riscv_vcpu_aia_imsic_inject(struct kvm_vcpu *vcpu,
> 
>         if (imsic->vsfile_cpu >= 0) {
>                 writel(iid, imsic->vsfile_va + IMSIC_MMIO_SETIPNUM_LE);
> -               kvm_vcpu_kick(vcpu);

We can't completely remove the kick, but we could replace it with a
kvm_vcpu_wake_up().

There's also a kick in kvm_riscv_vcpu_vstimer_expired() which could be a
kvm_vcpu_wake_up() when hideleg has IRQ_VS_TIMER set (which it currently
always does).

Thanks,
drew

>         } else {
>                 eix = &imsic->swfile->eix[iid / BITS_PER_TYPE(u64)];
>                 set_bit(iid & (BITS_PER_TYPE(u64) - 1), eix->eip);
> --
> 2.46.2
> 
> -- 
> kvm-riscv mailing list
> kvm-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kvm-riscv

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-02-18 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  8:00 [PATCH] riscv: KVM: Remove unnecessary vcpu kick 项文成
2025-02-18 17:48 ` Andrew Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-19  1:54 BillXiang
2025-02-19  8:36 ` Andrew Jones
2025-02-19  8:51 ` Radim Krčmář
2025-02-20  7:12   ` xiangwencheng
2025-02-20  8:01     ` Andrew Jones
2025-02-20  8:17       ` xiangwencheng
2025-02-20  8:50         ` Radim Krčmář
2025-02-20 12:14           ` Andrew Jones

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=20250218-57a3a16e477f83a8c267d120@orel \
    --to=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=xiangwencheng@lanxincomputing.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