qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, rjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] watchdog: convert to QemuOpts
Date: Wed, 03 Jun 2015 15:40:59 +0200	[thread overview]
Message-ID: <556F03EB.6000905@redhat.com> (raw)
In-Reply-To: <87a8whszmv.fsf@blackfin.pond.sub.org>



On 03/06/2015 15:14, Markus Armbruster wrote:
>>                                    However, boards often have embedded
>> watchdog devices; even if they currently don't, these should call
>> watchdog_perform_action() so that they are affected by -watchdog-action.
>> (This is listed in our BiteSizedTasks wiki page).
> 
> You'd have to configure their watchdog action with -global, because
> that's how we set onboard device properties.

Right.  That however doesn't work if the watchdog is a device but isn't
qdevified, or the watchdog isn't a device and doesn't have a dummy
device wrapper around it, aka the KVM_EXIT_WATCHDOG case.

Also, it's very hard to discover (e.g. how is one supposed to find a
watchdog_action property under ICH9_LPC---not yet upstream, but should
be in 2.4).

>    This makes -watchdog available in configuration files, like this:
> 
>         [watchdog]
>            model = "ib700"
> 
>    "-balloon virtio -watchdog ib700 -writeconfig /dev/stdout" now
>    produces
> 
>         [device]
>           driver = "virtio-balloon"
> 
>         [watchdog]
>           model = "ib700"
> 
>    Digs us deeper into the "alternative syntax" hole.

True, but consistent with "-drive if=virtio" which doesn't produce a
[device] stanza.

>    Of the three -watchdog behaviors "reject more than one watchdog",
>    "just add them all whether it makes sense or not" and "add at most
>    one, silently ignore the rest", this gives us the worst.

True, but consistent with the handling of other merge_lists options: the
last wins.

> If the stated objective is all you want, why not convert
> -watchdog-action instead of -watchdog?  Should be simpler.  Just make
> sure to preserve "last option wins" behavior.

Because I'm not sure that we won't have other watchdog options in the
future.  Also,

	[watchdog]
	    action = "reset"

is marginally nicer than any of

	[watchdog-action]
	    action = "reset"

and

	[machine]
	    watchdog-action = "reset"

Paolo

  reply	other threads:[~2015-06-03 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 13:09 [Qemu-devel] [PATCH v2] watchdog: convert to QemuOpts Paolo Bonzini
2015-05-27 14:06 ` Richard W.M. Jones
2015-05-27 14:17 ` Eric Blake
2015-05-27 14:40   ` Paolo Bonzini
2015-06-03 13:14 ` Markus Armbruster
2015-06-03 13:40   ` Paolo Bonzini [this message]
2015-06-03 15:27     ` Markus Armbruster
2015-06-03 15:38       ` Paolo Bonzini

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=556F03EB.6000905@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@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).