From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: lizhijian@cn.fujitsu.com, quintela@redhat.com,
yunhong.jiang@intel.com, eddie.dong@intel.com,
peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
arei.gonglei@huawei.com, stefanha@redhat.com,
amit.shah@redhat.com
Subject: Re: [Qemu-devel] [PATCH COLO-Frame v10 12/38] COLO: Save PVM state to secondary side when do checkpoint
Date: Tue, 17 Nov 2015 18:20:26 +0800 [thread overview]
Message-ID: <564AFF6A.80101@huawei.com> (raw)
In-Reply-To: <20151113185317.GD8720@work-vm>
On 2015/11/14 2:53, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>> On 2015/11/7 2:59, Dr. David Alan Gilbert wrote:
>>> * zhanghailiang (zhang.zhanghailiang@huawei.com) wrote:
>>>> The main process of checkpoint is to synchronize SVM with PVM.
>>>> VM's state includes ram and device state. So we will migrate PVM's
>>>> state to SVM when do checkpoint, just like migration does.
>>>>
>>>> We will cache PVM's state in slave, we use QEMUSizedBuffer
>>>> to store the data, we need to know the size of VM state, so in master,
>>>> we use qsb to store VM state temporarily, get the data size by call qsb_get_length()
>>>> and then migrate the data to the qsb in the secondary side.
>>>>
>>>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>>>> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
>>>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>>>> ---
>>>> migration/colo.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++++----
>>>> migration/ram.c | 47 +++++++++++++++++++++++++++++--------
>>>> migration/savevm.c | 2 +-
>>>> 3 files changed, 101 insertions(+), 16 deletions(-)
>>>>
>>>> diff --git a/migration/colo.c b/migration/colo.c
>>>> index 2510762..b865513 100644
>>>> --- a/migration/colo.c
>>>> +++ b/migration/colo.c
>>>> @@ -17,6 +17,9 @@
>>>> #include "qemu/error-report.h"
>>>> #include "qemu/sockets.h"
>>>>
>>>> +/* colo buffer */
>>>> +#define COLO_BUFFER_BASE_SIZE (4 * 1024 * 1024)
>>>> +
>>>> bool colo_supported(void)
>>>> {
>>>> return true;
>>>> @@ -94,9 +97,12 @@ static int colo_ctl_get(QEMUFile *f, uint32_t require)
>>>> return value;
>>>> }
>>>>
>>>> -static int colo_do_checkpoint_transaction(MigrationState *s)
>>>> +static int colo_do_checkpoint_transaction(MigrationState *s,
>>>> + QEMUSizedBuffer *buffer)
>>>> {
>>>> int ret;
>>>> + size_t size;
>>>> + QEMUFile *trans = NULL;
>>>>
>>>> ret = colo_ctl_put(s->to_dst_file, COLO_COMMAND_CHECKPOINT_REQUEST, 0);
>>>> if (ret < 0) {
>>>> @@ -107,15 +113,47 @@ static int colo_do_checkpoint_transaction(MigrationState *s)
>>>> if (ret < 0) {
>>>> goto out;
>>>> }
>>>> + /* Reset colo buffer and open it for write */
>>>> + qsb_set_length(buffer, 0);
>>>> + trans = qemu_bufopen("w", buffer);
>>>> + if (!trans) {
>>>> + error_report("Open colo buffer for write failed");
>>>> + goto out;
>>>> + }
>>>>
>>>> - /* TODO: suspend and save vm state to colo buffer */
>>>> + qemu_mutex_lock_iothread();
>>>> + vm_stop_force_state(RUN_STATE_COLO);
>>>> + qemu_mutex_unlock_iothread();
>>>> + trace_colo_vm_state_change("run", "stop");
>>>> +
>>>> + /* Disable block migration */
>>>> + s->params.blk = 0;
>>>> + s->params.shared = 0;
>>>> + qemu_savevm_state_header(trans);
>>>> + qemu_savevm_state_begin(trans, &s->params);
>>>> + qemu_mutex_lock_iothread();
>>>> + qemu_savevm_state_complete(trans);
>>>> + qemu_mutex_unlock_iothread();
>>>> +
>>>> + qemu_fflush(trans);
>>>>
>>>> ret = colo_ctl_put(s->to_dst_file, COLO_COMMAND_VMSTATE_SEND, 0);
>>>> if (ret < 0) {
>>>> goto out;
>>>> }
>>>> + /* we send the total size of the vmstate first */
>>>> + size = qsb_get_length(buffer);
>>>> + ret = colo_ctl_put(s->to_dst_file, COLO_COMMAND_VMSTATE_SIZE, size);
>>>> + if (ret < 0) {
>>>> + goto out;
>>>> + }
>>>>
>>>> - /* TODO: send vmstate to Secondary */
>>>> + qsb_put_buffer(s->to_dst_file, buffer, size);
>>>> + qemu_fflush(s->to_dst_file);
>>>> + ret = qemu_file_get_error(s->to_dst_file);
>>>> + if (ret < 0) {
>>>> + goto out;
>>>> + }
>>>>
>>>> ret = colo_ctl_get(s->from_dst_file, COLO_COMMAND_VMSTATE_RECEIVED);
>>>> if (ret < 0) {
>>>> @@ -127,14 +165,24 @@ static int colo_do_checkpoint_transaction(MigrationState *s)
>>>> goto out;
>>>> }
>>>>
>>>> - /* TODO: resume Primary */
>>>> + ret = 0;
>>>> + /* resume master */
>>>> + qemu_mutex_lock_iothread();
>>>> + vm_start();
>>>> + qemu_mutex_unlock_iothread();
>>>> + trace_colo_vm_state_change("stop", "run");
>>>>
>>>> out:
>>>> + if (trans) {
>>>> + qemu_fclose(trans);
>>>> + }
>>>> +
>>>> return ret;
>>>> }
>>>>
>>>> static void colo_process_checkpoint(MigrationState *s)
>>>> {
>>>> + QEMUSizedBuffer *buffer = NULL;
>>>> int fd, ret = 0;
>>>>
>>>> /* Dup the fd of to_dst_file */
>>>> @@ -159,6 +207,13 @@ static void colo_process_checkpoint(MigrationState *s)
>>>> goto out;
>>>> }
>>>>
>>>> + buffer = qsb_create(NULL, COLO_BUFFER_BASE_SIZE);
>>>> + if (buffer == NULL) {
>>>> + ret = -ENOMEM;
>>>> + error_report("Failed to allocate buffer!");
>>>
>>> Please say 'Failed to allocate colo buffer'; QEMU has lots and lots of buffers.
>>>
>>
>> OK, will fix it in next version.
>>
>>>> + goto out;
>>>> + }
>>>> +
>>>> qemu_mutex_lock_iothread();
>>>> vm_start();
>>>> qemu_mutex_unlock_iothread();
>>>> @@ -166,7 +221,7 @@ static void colo_process_checkpoint(MigrationState *s)
>>>>
>>>> while (s->state == MIGRATION_STATUS_COLO) {
>>>> /* start a colo checkpoint */
>>>> - ret = colo_do_checkpoint_transaction(s);
>>>> + ret = colo_do_checkpoint_transaction(s, buffer);
>>>> if (ret < 0) {
>>>> goto out;
>>>> }
>>>> @@ -179,6 +234,9 @@ out:
>>>> migrate_set_state(&s->state, MIGRATION_STATUS_COLO,
>>>> MIGRATION_STATUS_COMPLETED);
>>>>
>>>> + qsb_free(buffer);
>>>> + buffer = NULL;
>>>> +
>>>> if (s->from_dst_file) {
>>>> qemu_fclose(s->from_dst_file);
>>>> }
>>>> diff --git a/migration/ram.c b/migration/ram.c
>>>> index a25bcc7..5784c15 100644
>>>> --- a/migration/ram.c
>>>> +++ b/migration/ram.c
>>>> @@ -38,6 +38,7 @@
>>>> #include "trace.h"
>>>> #include "exec/ram_addr.h"
>>>> #include "qemu/rcu_queue.h"
>>>> +#include "migration/colo.h"
>>>>
>>>> #ifdef DEBUG_MIGRATION_RAM
>>>> #define DPRINTF(fmt, ...) \
>>>> @@ -1165,15 +1166,8 @@ void migration_bitmap_extend(ram_addr_t old, ram_addr_t new)
>>>> }
>>>> }
>>>>
>>>> -/* Each of ram_save_setup, ram_save_iterate and ram_save_complete has
>>>> - * long-running RCU critical section. When rcu-reclaims in the code
>>>> - * start to become numerous it will be necessary to reduce the
>>>> - * granularity of these critical sections.
>>>> - */
>>>> -
>>>> -static int ram_save_setup(QEMUFile *f, void *opaque)
>>>> +static int ram_save_init_globals(void)
>>>> {
>>>> - RAMBlock *block;
>>>> int64_t ram_bitmap_pages; /* Size of bitmap in pages, including gaps */
>>>>
>>>> dirty_rate_high_cnt = 0;
>>>> @@ -1233,6 +1227,31 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
>>>> migration_bitmap_sync();
>>>> qemu_mutex_unlock_ramlist();
>>>> qemu_mutex_unlock_iothread();
>>>> + rcu_read_unlock();
>>>> +
>>>> + return 0;
>>>> +}
>>>
>>> It surprises me you want migration_bitmap_sync in ram_save_init_globals(),
>>> but I guess you want the first sync at the start.
>>>
>>
>> Er, sorry,i don't quite understand.
>> Here. I just split part codes of ram_save_setup()
>> into a helper function ram_save_init_global(), to make it more clear.
>> We can't do initial work for twice. Is there any thing wrong ?
>
> No, that's OK - it just seemed odd for a function like 'init_globals'
> to do such a big side effect of doing the sync; but yes, it makes sense
> since it's just a split.
>
>>>> +/* Each of ram_save_setup, ram_save_iterate and ram_save_complete has
>>>> + * long-running RCU critical section. When rcu-reclaims in the code
>>>> + * start to become numerous it will be necessary to reduce the
>>>> + * granularity of these critical sections.
>>>> + */
>>>> +
>>>> +static int ram_save_setup(QEMUFile *f, void *opaque)
>>>> +{
>>>> + RAMBlock *block;
>>>> +
>>>> + /*
>>>> + * migration has already setup the bitmap, reuse it.
>>>> + */
>>>> + if (!migration_in_colo_state()) {
>>>> + if (ram_save_init_globals() < 0) {
>>>> + return -1;
>>>> + }
>>>> + }
>>>> +
>>>> + rcu_read_lock();
>>>>
>>>> qemu_put_be64(f, ram_bytes_total() | RAM_SAVE_FLAG_MEM_SIZE);
>>>>
>>>> @@ -1332,7 +1351,8 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>>>> while (true) {
>>>> int pages;
>>>>
>>>> - pages = ram_find_and_save_block(f, true, &bytes_transferred);
>>>> + pages = ram_find_and_save_block(f, !migration_in_colo_state(),
>>>> + &bytes_transferred);
>>>> /* no more blocks to sent */
>>>> if (pages == 0) {
>>>> break;
>>>> @@ -1343,8 +1363,15 @@ static int ram_save_complete(QEMUFile *f, void *opaque)
>>>> ram_control_after_iterate(f, RAM_CONTROL_FINISH);
>>>>
>>>> rcu_read_unlock();
>>>> + /*
>>>> + * Since we need to reuse dirty bitmap in colo,
>>>> + * don't cleanup the bitmap.
>>>> + */
>>>> + if (!migrate_colo_enabled() ||
>>>> + migration_has_failed(migrate_get_current())) {
>>>> + migration_end();
>>>> + }
>>>>
>>>> - migration_end();
>>>> qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
>>>>
>>>> return 0;
>>>> diff --git a/migration/savevm.c b/migration/savevm.c
>>>> index dbcc39a..0faf12b 100644
>>>> --- a/migration/savevm.c
>>>> +++ b/migration/savevm.c
>>>> @@ -48,7 +48,7 @@
>>>> #include "qemu/iov.h"
>>>> #include "block/snapshot.h"
>>>> #include "block/qapi.h"
>>>> -
>>>> +#include "migration/colo.h"
>>>>
>>>> #ifndef ETH_P_RARP
>>>> #define ETH_P_RARP 0x8035
>>>
>>> Wrong patch?
>>>
>>
>> No, we have call migration_in_colo_state() in qemu_savevm_state_begin().
>> So we have to include "migration/colo.h"
>
> I don't think you use it in savevm.c until patch 30, so you can add
> the #include in patch 30 (or whichever is the patch that first needs it).
>
Ha, I know what you mean. And yes, you are right,
we shouldn't call migration_in_colo_state() in qemu_savevm_state_begin() here.
Good catch. I will fix it in next version. Thanks.
> Dave
>
>
>>
>>>
>>> So other than those minor things:
>>>
>>> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>>
>>> but watch out for the recent changes to migrate_end that went in
>>> a few days ago.
>>>
>>
>> Thanks for reminding me, i have rebased that. ;)
>>
>> zhanghailiang
>>
>>> Dave
>>>
>>>> --
>>>> 1.8.3.1
>>>>
>>>>
>>> --
>>> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>>>
>>> .
>>>
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> .
>
next prev parent reply other threads:[~2015-11-17 10:25 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 11:56 [Qemu-devel] [PATCH COLO-Frame v10 00/38] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT) zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 01/38] configure: Add parameter for configure to enable/disable COLO support zhanghailiang
2015-11-05 14:52 ` Eric Blake
2015-11-06 7:36 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 02/38] migration: Introduce capability 'x-colo' to migration zhanghailiang
2015-11-13 16:01 ` Eric Blake
2015-11-16 8:35 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 03/38] COLO: migrate colo related info to secondary node zhanghailiang
2015-11-06 16:36 ` Dr. David Alan Gilbert
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 04/38] migration: Add state records for migration incoming zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 05/38] migration: Integrate COLO checkpoint process into migration zhanghailiang
2015-11-06 16:48 ` Dr. David Alan Gilbert
2015-11-13 16:42 ` Eric Blake
2015-11-16 13:00 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 06/38] migration: Integrate COLO checkpoint process into loadvm zhanghailiang
2015-11-06 17:29 ` Dr. David Alan Gilbert
2015-11-09 6:09 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 07/38] migration: Rename the'file' member of MigrationState and MigrationIncomingState zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 08/38] COLO/migration: establish a new communication path from destination to source zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 09/38] COLO: Implement colo checkpoint protocol zhanghailiang
2015-11-06 18:26 ` Dr. David Alan Gilbert
2015-11-09 6:51 ` zhanghailiang
2015-11-09 7:33 ` zhanghailiang
2015-11-13 16:46 ` Eric Blake
2015-11-17 7:04 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 10/38] COLO: Add a new RunState RUN_STATE_COLO zhanghailiang
2015-11-06 18:28 ` Dr. David Alan Gilbert
2015-11-13 16:47 ` Eric Blake
2015-11-17 7:15 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 11/38] QEMUSizedBuffer: Introduce two help functions for qsb zhanghailiang
2015-11-06 18:30 ` Dr. David Alan Gilbert
2015-11-09 8:14 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 12/38] COLO: Save PVM state to secondary side when do checkpoint zhanghailiang
2015-11-06 18:59 ` Dr. David Alan Gilbert
2015-11-09 9:17 ` zhanghailiang
2015-11-13 18:53 ` Dr. David Alan Gilbert
2015-11-17 10:20 ` zhanghailiang [this message]
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 13/38] COLO: Load PVM's dirty pages into SVM's RAM cache temporarily zhanghailiang
2015-11-13 15:39 ` Dr. David Alan Gilbert
2015-11-16 7:57 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 14/38] COLO: Load VMState into qsb before restore it zhanghailiang
2015-11-13 16:02 ` Dr. David Alan Gilbert
2015-11-16 8:46 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 15/38] ram/COLO: Record pages received from PVM by re-using migration dirty bitmap zhanghailiang
2015-11-13 16:19 ` Dr. David Alan Gilbert
2015-11-16 9:07 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 16/38] COLO: Flush PVM's cached RAM into SVM's memory zhanghailiang
2015-11-13 16:38 ` Dr. David Alan Gilbert
2015-11-16 12:46 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 17/38] COLO: synchronize PVM's state to SVM periodically zhanghailiang
2015-11-13 18:34 ` Dr. David Alan Gilbert
2015-11-17 9:11 ` zhanghailiang
2015-11-17 10:08 ` Dr. David Alan Gilbert
2015-11-17 10:29 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 18/38] COLO failover: Introduce a new command to trigger a failover zhanghailiang
2015-11-13 16:59 ` Eric Blake
2015-11-17 8:03 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 19/38] COLO failover: Introduce state to record failover process zhanghailiang
2015-11-20 15:51 ` Dr. David Alan Gilbert
2015-11-23 5:56 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 20/38] COLO: Implement failover work for Primary VM zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 21/38] COLO: Implement failover work for Secondary VM zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 22/38] COLO: implement default failover treatment zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 23/38] qmp event: Add event notification for COLO error zhanghailiang
2015-11-20 21:50 ` Eric Blake
2015-11-23 6:01 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 24/38] COLO failover: Shutdown related socket fd when do failover zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 25/38] COLO failover: Don't do failover during loading VM's state zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 26/38] COLO: Control the checkpoint delay time by migrate-set-parameters command zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 27/38] COLO: Process shutdown command for VM in COLO state zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 28/38] COLO: Update the global runstate after going into colo state zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 29/38] savevm: Split load vm state function qemu_loadvm_state zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 30/38] COLO: Separate the process of saving/loading ram and device state zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 31/38] COLO: Split qemu_savevm_state_begin out of checkpoint process zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 32/38] netfilter: Add a public API to release all the buffered packets zhanghailiang
2015-11-03 12:39 ` Yang Hongyang
2015-11-03 13:19 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 33/38] netfilter: Introduce an API to delete the timer of all buffer-filters zhanghailiang
2015-11-03 12:41 ` Yang Hongyang
2015-11-03 13:07 ` zhanghailiang
2015-11-04 2:51 ` Jason Wang
2015-11-04 3:08 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 34/38] filter-buffer: Accept zero interval zhanghailiang
2015-11-03 12:43 ` Yang Hongyang
2015-11-04 2:52 ` Jason Wang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 35/38] netfilter: Introduce a API to automatically add filter-buffer for each netdev zhanghailiang
2015-11-03 12:57 ` Yang Hongyang
2015-11-03 13:16 ` zhanghailiang
2015-11-04 2:56 ` Jason Wang
2015-11-04 3:07 ` zhanghailiang
2015-11-05 7:43 ` zhanghailiang
2015-11-05 8:52 ` Wen Congyang
2015-11-05 9:21 ` Jason Wang
2015-11-05 9:33 ` Wen Congyang
2015-11-05 9:19 ` Jason Wang
2015-11-05 10:58 ` zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 36/38] netfilter: Introduce an API to delete all the automatically added netfilters zhanghailiang
2015-11-03 12:58 ` Yang Hongyang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 37/38] colo: Use the netfilter to buffer and release packets zhanghailiang
2015-11-03 11:56 ` [Qemu-devel] [PATCH COLO-Frame v10 38/38] COLO: Add block replication into colo process zhanghailiang
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=564AFF6A.80101@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=yunhong.jiang@intel.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).