qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"dgilbert@redhat.com" <dgilbert@redhat.com>,
	"owasserm@redhat.com" <owasserm@redhat.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"mrhines@us.ibm.com" <mrhines@us.ibm.com>,
	Moyuxiang <moyuxiang@huawei.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] rdma: Fix block during rdma migration
Date: Thu, 15 May 2014 12:08:26 +0200	[thread overview]
Message-ID: <87oayz9wx1.fsf@elfo.mitica> (raw)
In-Reply-To: <53740DC0.4030905@linux.vnet.ibm.com> (Michael R. Hines's message of "Thu, 15 May 2014 08:43:44 +0800")

"Michael R. Hines" <mrhines@linux.vnet.ibm.com> wrote:
> On 05/09/2014 12:25 PM, Gonglei (Arei) wrote:
>> Hi,
>>
>>> -----Original Message-----
>>> From: Michael R. Hines [mailto:mrhines@linux.vnet.ibm.com]
>>> Sent: Tuesday, April 01, 2014 8:42 AM
>>> To: Gonglei (Arei); qemu-devel@nongnu.org
>>> Cc: Huangweidong (C); quintela@redhat.com; dgilbert@redhat.com;
>>> owasserm@redhat.com; mrhines@us.ibm.com; Moyuxiang;
>>> pbonzini@redhat.com
>>> Subject: Re: [Qemu-devel] [PATCH] rdma: Fix block during rdma migration
>>>
>>> On 03/29/2014 03:39 PM, arei.gonglei@huawei.com wrote:
>>>> From: Mo Yuxiang <Moyuxiang@huawei.com>
>>>>
>>>> If the networking break or there's something wrong with rdma
>>>> device(ib0 with no IP) during rdma migration, the main_loop of
>>>> qemu will be blocked in rdma_destroy_id. I add rdma_ack_cm_event
>>>> to fix this bug.
>>>>
>>>> Signed-off-by: Mo Yuxiang <Moyuxiang@huawei.com>
>>>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>>>> ---
>>>>    migration-rdma.c | 1 +
>>>>    1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/migration-rdma.c b/migration-rdma.c
>>>> index eeb4302..f60749b 100644
>>>> --- a/migration-rdma.c
>>>> +++ b/migration-rdma.c
>>>> @@ -949,6 +949,7 @@ route:
>>>>            ERROR(errp, "result not equal to event_addr_resolved %s",
>>>>                    rdma_event_str(cm_event->event));
>>>>            perror("rdma_resolve_addr");
>>>> +        rdma_ack_cm_event(cm_event);
>>>>            ret = -EINVAL;
>>>>            goto err_resolve_get_addr;
>>>>        }
>>> Reviewed-by: Michael R. Hines <mrhines@us.ibm.com>
>>>
>>> Good catch. =) That's an obvious bug. It looks like I need
>>> to do a much better job of "kill -9" inside the regression
>>> testing scripts - probably i should try killing the migration
>>> prematurely at different periods just to be sure there are
>>> no more places where the connection state is not getting
>>> cleaned up......
>>>
>>> - Michael
>>>
>> Michael, do you have a plan to pull this patch to master? Thanks.
>>
>> Best regards,
>> -Gonglei
>>
>
> Sorry for the late reply, but I'm not the maintainer for migration,
> that's Juan
> (I can only signoff on patches like everyone else =).
>
> I also have outstanding RDMA patches myself that have not yet been pulled.
>
> Would you mind pinging Juan for both of us?

Pointer, please?

I was waiting for Michael Reviewed-by from Michael.


Later, Juan.

>
> - Michael
>
> - Michael

  parent reply	other threads:[~2014-05-15 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29  7:39 [Qemu-devel] [PATCH] rdma: Fix block during rdma migration arei.gonglei
2014-04-01  0:42 ` Michael R. Hines
2014-04-01  1:47   ` Gonglei (Arei)
2014-05-09  4:25   ` Gonglei (Arei)
2014-05-15  0:43     ` Michael R. Hines
2014-05-15  6:47       ` Gonglei (Arei)
2014-05-15 10:08       ` Juan Quintela [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-17  1:45 Wangyufei (James)
2014-03-14  1:42 Wangyufei (James)

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=87oayz9wx1.fsf@elfo.mitica \
    --to=quintela@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=moyuxiang@huawei.com \
    --cc=mrhines@linux.vnet.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weidong.huang@huawei.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).