From: "Zhang, Chen" <chen.zhang@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-dev <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>
Cc: Zhang Chen <zhangckid@gmail.com>
Subject: Re: [PATCH V3 0/4] Introduce Advanced Watch Dog module
Date: Tue, 10 Dec 2019 08:29:29 +0800 [thread overview]
Message-ID: <c4a3b0c5-a6bc-2f6c-2fe8-7c25e3b0e378@intel.com> (raw)
In-Reply-To: <a0667556-3228-76cc-8e4d-1adf671f4a9e@redhat.com>
On 12/9/2019 5:08 PM, Paolo Bonzini wrote:
> On 08/12/19 18:52, Zhang, Chen wrote:
>> Hi All~
>>
>> No news for a long time.
>>
>> Please give me more comments about this series.
> Sorry, people were probably busy with the QEMU release candidates.
>
> Even before looking at the code, the series is completely missing
> documentation on how to use it and on the chardev protocol. The
> documentation should go in docs/ and should be written as restructuredText.
>
> The qemu-options.hx patches also lack documentation about the properties
> accepted by the new object.
OK, I will add documentation in docs/ and qemu-options.hx in next version.
For the chardev protocol part, current implementation just use plaintext
that make AWD easy to connect with other user defined node, I am not
very familiar with this part, do you have any suggestions here? maybe
use some general protocol is better? or Jason have any suggestions?
>
> In particular:
>
>>> -chardev socket,id=h1,host=3.3.3.3,port=9009,server,nowait
>>> -chardev socket,id=heartbeat0,host=3.3.3.3,port=4445
>>> -object iothread,id=iothread2
>>> -object
>>> advanced-watchdog,id=heart1,server=on,awd_node=h1,notification_node=heartbeat0,opt_script=colo_opt_script_path,iothread=iothread1,pulse_interval=1000,timeout=5000
> What are the two sockets for, and what should be in colo_opt_script_path?
Anything user want to send when timeout, for example:
If timeout is detected, AWD send quit command to Qemu.
colo_opt_script_path=/tmp/qemu-qmp-quit.script
------------------------------------
qemu-qmp-quit.script:
{ "execute": "quit" }
------------------------------------
Thanks
Zhang Chen
>
>>> In secondary node:
>>>
>>> -monitor tcp::4445,server,nowait
>>> -chardev socket,id=h1,host=3.3.3.3,port=9009,reconnect=1
>>> -chardev socket,id=heart1,host=3.3.3.8,port=4445
>>> -object iothread,id=iothread1
>>> -object
>>> advanced-watchdog,id=heart1,server=off,awd_node=h1,notification_node=heart1,opt_script=colo_secondary_opt_script,iothread=iothread1,timeout=10000
> Same here.
>
> Paolo
>
prev parent reply other threads:[~2019-12-10 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:30 [PATCH V3 0/4] Introduce Advanced Watch Dog module Zhang Chen
2019-11-19 12:30 ` [PATCH V3 1/4] net/awd.c: Introduce Advanced Watch Dog module framework Zhang Chen
2019-11-19 12:30 ` [PATCH V3 2/4] net/awd.c: Initailize input/output chardev Zhang Chen
2019-11-19 12:30 ` [PATCH V3 3/4] net/awd.c: Load advanced watch dog worker thread job Zhang Chen
2019-11-19 12:30 ` [PATCH V3 4/4] vl.c: Make Advanced Watch Dog delayed initialization Zhang Chen
2019-12-08 17:52 ` [PATCH V3 0/4] Introduce Advanced Watch Dog module Zhang, Chen
2019-12-09 9:08 ` Paolo Bonzini
2019-12-10 0:29 ` Zhang, Chen [this message]
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=c4a3b0c5-a6bc-2f6c-2fe8-7c25e3b0e378@intel.com \
--to=chen.zhang@intel.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).