All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: lirongqing <lirongqing@baidu.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: eventfd: Remove redundant synchronize_srcu_expedited from irqfd assignment
Date: Mon, 9 Mar 2026 08:36:27 -0700	[thread overview]
Message-ID: <aa7o-4eHAfTikGec@google.com> (raw)
In-Reply-To: <20260309092132.2484-1-lirongqing@baidu.com>

On Mon, Mar 09, 2026, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
> 
> The synchronize_srcu_expedited() call in kvm_irqfd_assign() is unnecessary
> when adding a new irqfd to the resampler list. The list insertion is
> already RCU-safe, and existing readers will either see the old or the
> updated list without inconsistency.

It's not required for kernel safety, but I do think it's required for KVM's ABI,
e.g. to ensure the resampler is visible to readers before KVM_IRQFD returns to
userspace.

> Removing this call reduces latency during resampling irqfd setup.

May I ask why you're micro-optimizing VMs with an in-kernel I/O APIC?

> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
>  virt/kvm/eventfd.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
> index 3201f60..facfeab 100644
> --- a/virt/kvm/eventfd.c
> +++ b/virt/kvm/eventfd.c
> @@ -450,7 +450,6 @@ kvm_irqfd_assign(struct kvm *kvm, struct kvm_irqfd *args)
>  		}
>  
>  		list_add_rcu(&irqfd->resampler_link, &irqfd->resampler->list);
> -		synchronize_srcu_expedited(&kvm->irq_srcu);
>  
>  		mutex_unlock(&kvm->irqfds.resampler_lock);
>  	}
> -- 
> 2.9.4
> 

  reply	other threads:[~2026-03-09 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  9:21 [PATCH] KVM: eventfd: Remove redundant synchronize_srcu_expedited from irqfd assignment lirongqing
2026-03-09 15:36 ` Sean Christopherson [this message]
2026-03-10  1:37   ` 答复: [????] " Li,Rongqing(ACG CCN)
2026-03-10 14:12     ` Sean Christopherson

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=aa7o-4eHAfTikGec@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lirongqing@baidu.com \
    --cc=pbonzini@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 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.