qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Straub <lukasstraub2@web.de>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Fabiano Rosas <farosas@suse.de>, Peter Xu <peterx@redhat.com>,
	Yong Huang <yong.huang@smartx.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] multifd: Make the main thread yield periodically to the main loop
Date: Tue, 19 Aug 2025 14:03:26 +0200	[thread overview]
Message-ID: <20250819140326.6e94b1c9@penguin> (raw)
In-Reply-To: <aKRSZ7jCfIzvv4jW@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]

On Tue, 19 Aug 2025 11:31:03 +0100
Daniel P. Berrangé <berrange@redhat.com> wrote:

> On Mon, Aug 11, 2025 at 10:53:11AM -0300, Fabiano Rosas wrote:
> > Lukas Straub <lukasstraub2@web.de> writes:
> >   
> > > On Fri, 8 Aug 2025 11:37:23 -0400
> > > Peter Xu <peterx@redhat.com> wrote:
> > >> ...
> > >> migrate_cancel() should really be an OOB command..  It should be a superset
> > >> of yank features, plus anything migration speficic besides yanking the
> > >> channels, for example, when migration thread is blocked in PRE_SWITCHOVER.  
> > >
> > > Hmm, I think the migration code should handle this properly even if the
> > > yank command is used. From the POV of migration, it sees that the
> > > connection broke with connection reset. That is the same error as if the
> > > other side crashes/is killed or a NAT/stateful firewall in between
> > > reboots.
> > >  
> > 
> > That should all work just fine. After yank or after a detectable network
> > failure. The issue here seems to be that the destination recv is hanging
> > indefinitely. I don't think we ever played with socket timeout
> > configurations, or even switching to non-blocking during the sync. This
> > is actually (AFAIK) the first time we get a hang that's not "just" a
> > synchronization issue in the migration code.  
> 
> Based on the stack trace, whether the socket is blocking or not isn't a
> problem - QEMU is stuck in a  sem_wait call that will delay the coroutine,
> and thus the thread, indefinitely. IMHO the semaphore usage needs to be
> removed in favour of a synchronization mechanism that can integrate with
> event loop such that the coroutine does not block.
> 

I don't think that is an issue. The semaphore is just there to sync
with the multifd threads, which are in turn blocking on recvmsg.

Without multifd the main thread would hang in recvmsg as well in this
scenario.

Best Regards,
Lukas Straub

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-08-19 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07  2:41 [PATCH] multifd: Make the main thread yield periodically to the main loop yong.huang
2025-08-07  9:32 ` Lukas Straub
2025-08-07  9:36 ` Lukas Straub
2025-08-08  2:36   ` Yong Huang
2025-08-08  7:01     ` Lukas Straub
2025-08-08  8:02       ` Yong Huang
2025-08-08 13:55         ` Fabiano Rosas
2025-08-08 15:37           ` Peter Xu
2025-08-11  2:25             ` Yong Huang
2025-08-11  7:03             ` Lukas Straub
2025-08-11 13:53               ` Fabiano Rosas
2025-08-19 10:31                 ` Daniel P. Berrangé
2025-08-19 12:03                   ` Lukas Straub [this message]
2025-08-19 12:07                     ` Daniel P. Berrangé
2025-08-19 20:03                       ` Peter Xu
2025-08-11  2:27           ` Yong Huang
2025-08-08  6:36 ` Yong Huang
2025-08-08 15:42 ` Peter Xu
2025-08-11  2:02   ` Yong Huang
2025-08-19 10:19 ` Daniel P. Berrangé

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=20250819140326.6e94b1c9@penguin \
    --to=lukasstraub2@web.de \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yong.huang@smartx.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;
as well as URLs for NNTP newsgroup(s).