All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Denis V. Lunev" <den@virtuozzo.com>, Hanna Czenczek <hreitz@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
	"Denis V. Lunev" <den@openvz.org>,
	qemu-devel@nongnu.org, "Akihiko Odaki" <akihiko.odaki@daynix.com>,
	qemu-block@nongnu.org, qemu-stable@nongnu.org,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 1/1] coroutine: fix lost wakeup in qemu_co_sleep_wake()
Date: Thu, 9 Jul 2026 15:43:09 -0400	[thread overview]
Message-ID: <ak_5zULusWIPrOBH@x1.local> (raw)
In-Reply-To: <9cbdce55-83a7-4b43-b3b6-8123d85ab9c8@virtuozzo.com>

On Thu, Jul 09, 2026 at 09:00:52PM +0200, Denis V. Lunev wrote:
> On 7/9/26 20:55, Philippe Mathieu-Daudé wrote:
> > Hi Denis,
> >
> > I tried to review, but not my area and way out of my confort zone...
> > Cc'ing Akihiko & Peter who might have more familiarity :)

I'm always scared to work on coroutines.. :)

> 
> I thought that v3 should go fast, this is v3. Not too much
> changes + unit test. I was wrong :(

This does look like to fix a real issue. I'm also surprised it got
overlooked until now.  Said that, I still think some block people should
look at this..

Kevin and Stefan are both on PTO, getting back either in 1 or 2 weeks.
Let's see if Hanna will start to notice?  If there's still no update in 2
weeks, I can help to reach out to them.

PS: I copied Paolo too; normally he's flooded, but sometimes he'll reply.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2026-07-09 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 11:58 [PATCH v3 0/1] coroutine: fix lost wakeup in qemu_co_sleep_wake() Denis V. Lunev via qemu development
2026-06-10 11:58 ` [PATCH v3 1/1] " Denis V. Lunev via qemu development
2026-07-09 18:55   ` Philippe Mathieu-Daudé
2026-07-09 19:00     ` Denis V. Lunev
2026-07-09 19:43       ` Peter Xu [this message]
2026-07-09 20:54         ` Denis V. Lunev
2026-06-18 17:57 ` [PATCH v3 0/1] " Denis V. Lunev
2026-06-25 23:23 ` Denis V. Lunev
2026-07-02 17:47 ` Denis V. Lunev
2026-07-09 12:56 ` Denis V. Lunev

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=ak_5zULusWIPrOBH@x1.local \
    --to=peterx@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=den@openvz.org \
    --cc=den@virtuozzo.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@oss.qualcomm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@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.