All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>, Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	Juan Quintela <quintela@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V4 10/16] qmp event: Add COLO_EXIT event to notify users while exited COLO
Date: Tue, 6 Feb 2018 09:20:17 -0600	[thread overview]
Message-ID: <812d3335-30d3-28ed-ca9e-7f5b1b9caaca@redhat.com> (raw)
In-Reply-To: <CAK3tnvLsUp8CdpThNMSXR62JRSd1D+wGGZowixJF04CQ6e858g@mail.gmail.com>

On 02/05/2018 09:13 PM, Zhang Chen wrote:

>>> +##
>>> +{ 'event': 'COLO_EXIT',
>>> +  'data': {'mode': 'COLOMode', 'reason': 'COLOExitReason' } }
>>
>> Standard question when I see a new event: is there a way to poll for the
>> event's information?  If not, why don't we need one?
>>
>>
> Your means is we'd better print the information to a log file or something
> like that for all qemu events?
> CC  Eric Blake <eblake@redhat.com>
> any idea about this?

Nothing to add, Markus is right - implementing a new mechanism that logs 
all events as they are issued, and teaching libvirt to parse that log at 
startup, is more work than just implementing a query-foo command that 
libvirt already knows how to use to query current state on first connect 
(and based on that query, make an intelligent decision on whether at 
least one event was missed during downtime).  So far, no one has come up 
with an event that is so important it must be logged, when compared to 
the working alternative of just having events be ways to optimize 
performance so that the query- command doesn't have to be polled all the 
time, but no severe loss if the event is missed because the query- can 
be used in its place.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  parent reply	other threads:[~2018-02-06 15:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 13:44 [Qemu-devel] [PATCH V4 00/16] COLO: integrate colo frame with block replication and COLO proxy Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 01/16] filter-rewriter: fix memory leak for connection in connection_track_table Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 02/16] colo-compare: implement the process of checkpoint Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 03/16] colo-compare: use notifier to notify packets comparing result Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 04/16] COLO: integrate colo compare with colo frame Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 05/16] COLO: Add block replication into colo process Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 06/16] COLO: Remove colo_state migration struct Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 07/16] COLO: Load dirty pages into SVM's RAM cache firstly Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 08/16] ram/COLO: Record the dirty pages that SVM received Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 09/16] COLO: Flush memory data from ram cache Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 10/16] qmp event: Add COLO_EXIT event to notify users while exited COLO Zhang Chen
2018-02-03 15:49   ` Markus Armbruster
2018-02-06  3:13     ` Zhang Chen
2018-02-06  7:27       ` Markus Armbruster
2018-02-06  8:01         ` Zhang Chen
2018-02-06  9:53           ` Markus Armbruster
2018-02-06 12:44             ` Zhang Chen
2018-02-06 15:20       ` Eric Blake [this message]
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 11/16] savevm: split the process of different stages for loadvm/savevm Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 12/16] COLO: flush host dirty ram from cache Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 13/16] filter: Add handle_event method for NetFilterClass Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 14/16] filter-rewriter: handle checkpoint and failover event Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 15/16] COLO: notify net filters about checkpoint/failover event Zhang Chen
2018-01-19 13:44 ` [Qemu-devel] [PATCH V4 16/16] COLO: quick failover process by kick COLO thread Zhang Chen
2018-01-30  5:42 ` [Qemu-devel] [PATCH V4 00/16] COLO: integrate colo frame with block replication and COLO proxy Zhang Chen

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=812d3335-30d3-28ed-ca9e-7f5b1b9caaca@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhangckid@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.