From: "Longpeng(Mike)" <longpeng2@huawei.com>
To: <quintela@redhat.com>, <dgilbert@redhat.com>
Cc: longpeng2@huawei.com, arei.gonglei@huawei.com, qemu-devel@nongnu.org
Subject: [PATCH 0/2] migration: add vsock channel support
Date: Thu, 6 Aug 2020 15:40:28 +0800 [thread overview]
Message-ID: <20200806074030.174-1-longpeng2@huawei.com> (raw)
Longpeng (Mike) (2):
migration: unify the framework of socket-type channel
migration: add vsock as data channel support
migration/migration.c | 20 +++++++-------
migration/socket.c | 72 +++++++++++----------------------------------------
migration/socket.h | 11 +++-----
3 files changed, 28 insertions(+), 75 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-08-06 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 7:40 Longpeng(Mike) [this message]
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.)
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=20200806074030.174-1-longpeng2@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).