From: Peter Xu <peterx@redhat.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Dr . David Alan Gilbert" <dave@treblig.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Hailiang Zhang" <zhanghailiang@xfusion.com>,
"Yury Kotov" <yury-kotov@yandex-team.ru>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"Prasad Pandit" <ppandit@redhat.com>,
"Zhang Chen" <zhangckid@gmail.com>,
"Juraj Marcin" <jmarcin@redhat.com>
Subject: Re: [PATCH RFC 4/9] migration/rdma: Change io_create_watch() to return immediately
Date: Wed, 8 Oct 2025 16:42:11 -0400 [thread overview]
Message-ID: <aObMoyblRullLbSK@x1.local> (raw)
In-Reply-To: <a29ebbe7-008d-4d96-a2c4-825378055a28@fujitsu.com>
On Fri, Sep 26, 2025 at 02:39:43AM +0000, Zhijian Li (Fujitsu) wrote:
>
>
> On 28/08/2025 04:59, Peter Xu wrote:
> > The old RDMA's io_create_watch() isn't really doing much work anyway. For
> > G_IO_OUT, it already does return immediately. For G_IO_IN, it will try to
> > detect some RDMA context length however normally nobody will be able to set
> > it at all.
> >
>
>
> First, RDMA migration works well with this patch applied.
>
> Tested-by: Li Zhijian <lizhijian@fujitsu.com>
Thanks a lot, Zhijian.
>
>
> I have a small question. While testing, I didn't observe any callers to
> qio_channel_rdma_create_watch() during a complete RDMA migration using
> the default capabilities and parameters.
> I was wondering in which case this function is expected to be called?
> (I see io_create_watch() is mandatory for QIOChannelClass)
Yes, that's also my observation. See my reply to Fabiano on the same patch
for some information.
A summary of what I said there but more focused to what you're asking: IIUC
currently we almost always rely on qemu_rdma_wait_comp_channel() to poll
the two rdma fds, and yield if necessary when in a coroutine.
IOW, I don't know when qio_channel_rdma_create_watch(), or in most cases,
qio_channel_wait(), will be used at all. I had a feeling that if it's used
it might stuck forever (as the gsource will be monitoring control_len, see
below [1], while IIUC only the thread itself can update it, or am I
wrong?). But I'm not fluent with the RDMA codebase. Maybe you'll have a
better picture after seeing what I said here and there.
This patch is almost something I want to guarantee it won't happen, hence
for whatever could return QIO_CHANNEL_ERR_BLOCK for rdma channels I want to
make sure it immediately retries instead of hanging forever in the temp
main loop of qio_channel_wait().
>
>
> Thanks
> Zhijian
>
>
> > Simplify the code so that RDMA iochannels simply always rely on synchronous
> > reads and writes. It is highly likely what 6ddd2d76ca6f86f was talking
> > about, that the async model isn't really working well.
> >
> > This helps because this is almost the only dependency that the migration
> > core would need a coroutine for rdma channels.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > migration/rdma.c | 69 +++---------------------------------------------
> > 1 file changed, 3 insertions(+), 66 deletions(-)
> >
> > diff --git a/migration/rdma.c b/migration/rdma.c
> > index ed4e20b988..bcd7aae2f2 100644
> > --- a/migration/rdma.c
> > +++ b/migration/rdma.c
> > @@ -2789,56 +2789,14 @@ static gboolean
> > qio_channel_rdma_source_prepare(GSource *source,
> > gint *timeout)
> > {
> > - QIOChannelRDMASource *rsource = (QIOChannelRDMASource *)source;
> > - RDMAContext *rdma;
> > - GIOCondition cond = 0;
> > *timeout = -1;
> > -
> > - RCU_READ_LOCK_GUARD();
> > - if (rsource->condition == G_IO_IN) {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmain);
> > - } else {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmaout);
> > - }
> > -
> > - if (!rdma) {
> > - error_report("RDMAContext is NULL when prepare Gsource");
> > - return FALSE;
> > - }
> > -
> > - if (rdma->wr_data[0].control_len) {
> > - cond |= G_IO_IN;
> > - }
> > - cond |= G_IO_OUT;
> > -
> > - return cond & rsource->condition;
> > + return TRUE;
> > }
> >
> > static gboolean
> > qio_channel_rdma_source_check(GSource *source)
> > {
> > - QIOChannelRDMASource *rsource = (QIOChannelRDMASource *)source;
> > - RDMAContext *rdma;
> > - GIOCondition cond = 0;
> > -
> > - RCU_READ_LOCK_GUARD();
> > - if (rsource->condition == G_IO_IN) {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmain);
> > - } else {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmaout);
> > - }
> > -
> > - if (!rdma) {
> > - error_report("RDMAContext is NULL when check Gsource");
> > - return FALSE;
> > - }
> > -
> > - if (rdma->wr_data[0].control_len) {
[1]
> > - cond |= G_IO_IN;
> > - }
> > - cond |= G_IO_OUT;
> > -
> > - return cond & rsource->condition;
> > + return TRUE;
> > }
> >
> > static gboolean
> > @@ -2848,29 +2806,8 @@ qio_channel_rdma_source_dispatch(GSource *source,
> > {
> > QIOChannelFunc func = (QIOChannelFunc)callback;
> > QIOChannelRDMASource *rsource = (QIOChannelRDMASource *)source;
> > - RDMAContext *rdma;
> > - GIOCondition cond = 0;
> > -
> > - RCU_READ_LOCK_GUARD();
> > - if (rsource->condition == G_IO_IN) {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmain);
> > - } else {
> > - rdma = qatomic_rcu_read(&rsource->rioc->rdmaout);
> > - }
> > -
> > - if (!rdma) {
> > - error_report("RDMAContext is NULL when dispatch Gsource");
> > - return FALSE;
> > - }
> > -
> > - if (rdma->wr_data[0].control_len) {
> > - cond |= G_IO_IN;
> > - }
> > - cond |= G_IO_OUT;
> >
> > - return (*func)(QIO_CHANNEL(rsource->rioc),
> > - (cond & rsource->condition),
> > - user_data);
> > + return (*func)(QIO_CHANNEL(rsource->rioc), rsource->condition, user_data);
> > }
> >
> > static void
--
Peter Xu
next prev parent reply other threads:[~2025-10-08 20:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 20:59 [PATCH RFC 0/9] migration: Threadify loadvm process Peter Xu
2025-08-27 20:59 ` [PATCH RFC 1/9] migration/vfio: Remove BQL implication in vfio_multifd_switchover_start() Peter Xu
2025-08-28 18:05 ` Maciej S. Szmigiero
2025-09-16 21:34 ` Fabiano Rosas
2025-08-27 20:59 ` [PATCH RFC 2/9] migration/rdma: Fix wrong context in qio_channel_rdma_shutdown() Peter Xu
2025-09-16 21:41 ` Fabiano Rosas
2025-09-26 1:01 ` Zhijian Li (Fujitsu)
2025-08-27 20:59 ` [PATCH RFC 3/9] migration/rdma: Allow qemu_rdma_wait_comp_channel work with thread Peter Xu
2025-09-16 21:50 ` Fabiano Rosas
2025-09-26 1:02 ` Zhijian Li (Fujitsu)
2025-08-27 20:59 ` [PATCH RFC 4/9] migration/rdma: Change io_create_watch() to return immediately Peter Xu
2025-09-16 22:35 ` Fabiano Rosas
2025-10-08 20:34 ` Peter Xu
2025-09-26 2:39 ` Zhijian Li (Fujitsu)
2025-10-08 20:42 ` Peter Xu [this message]
2025-08-27 20:59 ` [PATCH RFC 5/9] migration: Thread-ify precopy vmstate load process Peter Xu
2025-08-27 23:51 ` Dr. David Alan Gilbert
2025-08-29 16:37 ` Peter Xu
2025-09-04 1:38 ` Dr. David Alan Gilbert
2025-10-08 21:02 ` Peter Xu
2025-08-29 8:29 ` Vladimir Sementsov-Ogievskiy
2025-08-29 17:17 ` Peter Xu
2025-09-01 9:35 ` Vladimir Sementsov-Ogievskiy
2025-09-17 18:23 ` Fabiano Rosas
2025-10-09 21:41 ` Peter Xu
2025-09-26 3:41 ` Zhijian Li (Fujitsu)
2025-10-08 21:10 ` Peter Xu
2025-08-27 20:59 ` [PATCH RFC 6/9] migration/rdma: Remove coroutine path in qemu_rdma_wait_comp_channel Peter Xu
2025-09-16 22:39 ` Fabiano Rosas
2025-10-08 21:18 ` Peter Xu
2025-09-26 2:44 ` Zhijian Li (Fujitsu)
2025-08-27 20:59 ` [PATCH RFC 7/9] migration/postcopy: Remove workaround on wait preempt channel Peter Xu
2025-09-17 18:30 ` Fabiano Rosas
2025-08-27 20:59 ` [PATCH RFC 8/9] migration/ram: Remove workaround on ram yield during load Peter Xu
2025-09-17 18:31 ` Fabiano Rosas
2025-08-27 20:59 ` [PATCH RFC 9/9] migration/rdma: Remove rdma_cm_poll_handler Peter Xu
2025-09-17 18:38 ` Fabiano Rosas
2025-10-08 21:22 ` Peter Xu
2025-09-26 3:38 ` Zhijian Li (Fujitsu)
2025-08-29 8:29 ` [PATCH RFC 0/9] migration: Threadify loadvm process Vladimir Sementsov-Ogievskiy
2025-08-29 17:18 ` Peter Xu
2025-09-04 8:27 ` Zhang Chen
2025-10-08 21:26 ` Peter Xu
2025-09-16 21:32 ` Fabiano Rosas
2025-10-09 16:58 ` Peter Xu
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=aObMoyblRullLbSK@x1.local \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=dave@treblig.org \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=kwolf@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=yury-kotov@yandex-team.ru \
--cc=zhangckid@gmail.com \
--cc=zhanghailiang@xfusion.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).