Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: John Levon <john.levon@nutanix.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Thanos Makatos <thanos.makatos@nutanix.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: optionally post write on ioeventfd write
Date: Wed, 10 Jun 2026 08:31:38 +0100	[thread overview]
Message-ID: <aikS2rM4wnJOHZM6@lent> (raw)
In-Reply-To: <aeeNiQf6NMJk9zKd@google.com>

On Tue, Apr 21, 2026 at 07:45:29AM -0700, Sean Christopherson wrote:

> On Fri, Apr 10, 2026, Thanos Makatos wrote:
> > Hi Paolo, Sean,
> > 
> > Following up on this, please let me know whether this is something I
> > should revise/resend.
> 
> No action needed on your end.  More discussion is needed to make sure this is
> uAPI that we want to support long term, but we're not waiting on you for anything.

I appreciate everyone is busy, but I haven't seen any further discussion on this
since this email, and I have people asking about this feature - is it possible
to get an update?

thanks,
john

  reply	other threads:[~2026-06-10  7:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 12:56 [PATCH] KVM: optionally post write on ioeventfd write Thanos Makatos
2026-03-12 15:02 ` David Woodhouse
2026-03-12 16:12   ` Thanos Makatos
2026-04-21 14:44     ` Sean Christopherson
2026-03-23 15:01 ` Thanos Makatos
2026-04-10 19:11   ` Thanos Makatos
2026-04-21 14:45     ` Sean Christopherson
2026-06-10  7:31       ` John Levon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-13 20:00 [RFC PATCH] KVM: optionally commit " Sean Christopherson
2026-03-02 12:28 ` [PATCH] KVM: optionally post " Thanos Makatos
2026-03-05  1:26   ` Sean Christopherson
2026-03-06 11:14     ` Thanos Makatos
2026-03-05  1:49   ` kernel test robot
2026-03-05  9:39   ` kernel test robot

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=aikS2rM4wnJOHZM6@lent \
    --to=john.levon@nutanix.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thanos.makatos@nutanix.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