qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhang, Chen" <chen.zhang@intel.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: Mon, 9 Dec 2019 10:08:02 +0100	[thread overview]
Message-ID: <a0667556-3228-76cc-8e4d-1adf671f4a9e@redhat.com> (raw)
In-Reply-To: <7efe2315-87c3-2b64-2240-087aba389016@intel.com>

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.

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?

>>
>> 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



  reply	other threads:[~2019-12-09  9:08 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 [this message]
2019-12-10  0:29     ` 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=a0667556-3228-76cc-8e4d-1adf671f4a9e@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=chen.zhang@intel.com \
    --cc=jasowang@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).