From: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" <longpeng2@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: arei.gonglei@huawei.com, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH 2/2] migration: add vsock as data channel support
Date: Fri, 14 Aug 2020 08:31:00 +0800 [thread overview]
Message-ID: <2bc0e226-ee71-330a-1bcd-bd9d097509bc@huawei.com> (raw)
In-Reply-To: <20200812095211.GB2810@work-vm>
在 2020/8/12 17:52, Dr. David Alan Gilbert 写道:
> * Longpeng(Mike) (longpeng2@huawei.com) wrote:
>> The vsock channel is more widely use in some new features, for example,
>> the Nitro/Enclave. It can also be used as the migration channel.
>>
>> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
>
> OK; it might be worth adding some tests for this.
>
OK, I'll try when I'm free.
> Can I ask what your use case is - is this migrating an L2 inside an L1
> or what?
>
Yes, L2 migrationg is a potential use case for this. However, our use
case is still focusing on the L1 migration.
There is no network stack in our platform ( [1] ), so we use the vsock
channel to communicate between the QEMU (on x86/ARM) and an Agent (on a
PCIe card), the source Agent will transport the data to the destination.
Links:
[1]
https://kvmforum2019.sched.com/event/Tmzh/zero-next-generation-virtualization-platform-for-huawei-cloud-jinsong-liu-zhichao-huang-huawei
>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
Thanks.
>> ---
>> migration/migration.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/migration/migration.c b/migration/migration.c
>> index 3160b95..fcf7974 100644
>> --- a/migration/migration.c
>> +++ b/migration/migration.c
>> @@ -383,7 +383,8 @@ void qemu_start_incoming_migration(const char *uri, Error **errp)
>> if (!strcmp(uri, "defer")) {
>> deferred_incoming_migration(errp);
>> } else if (strstart(uri, "tcp:", &p) ||
>> - strstart(uri, "unix:", NULL)) {
>> + strstart(uri, "unix:", NULL) ||
>> + strstart(uri, "vsock:", NULL)) {
>> socket_start_incoming_migration(p ? p : uri, errp);
>> #ifdef CONFIG_RDMA
>> } else if (strstart(uri, "rdma:", &p)) {
>> @@ -2072,7 +2073,8 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
>> }
>>
>> if (strstart(uri, "tcp:", &p) ||
>> - strstart(uri, "unix:", NULL)) {
>> + strstart(uri, "unix:", NULL) ||
>> + strstart(uri, "vsock:", NULL)) {
>> socket_start_outgoing_migration(s, p ? p : uri, &local_err);
>> #ifdef CONFIG_RDMA
>> } else if (strstart(uri, "rdma:", &p)) {
>> --
>> 1.8.3.1
>>
next prev parent reply other threads:[~2020-08-14 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 7:40 [PATCH 0/2] migration: add vsock channel support Longpeng(Mike)
2020-08-06 7:40 ` [PATCH 1/2] migration: unify the framework of socket-type channel Longpeng(Mike)
2020-08-12 9:43 ` Dr. David Alan Gilbert
2020-08-06 7:40 ` [PATCH 2/2] migration: add vsock as data channel support Longpeng(Mike)
2020-08-12 9:52 ` Dr. David Alan Gilbert
2020-08-14 0:31 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) [this message]
2020-08-27 17:15 ` [PATCH 0/2] migration: add vsock " Dr. David Alan Gilbert
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=2bc0e226-ee71-330a-1bcd-bd9d097509bc@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).