From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: device capabilities
Date: Sat, 05 Sep 2009 08:39:57 -0500 [thread overview]
Message-ID: <4AA26A2D.4010605@codemonkey.ws> (raw)
In-Reply-To: <4AA12F46.6000207@redhat.com>
Gerd Hoffmann wrote:
> Look at patch #5 (watchdogs). What else do you suggest here?
> There is nothing which can be used to identify the device as watchdog.
That's a problem with the watchdog timers. The WatchdogTimerModel stuff
really replicates qdev functionality.
Ideally, the watchdog_list would go away and we would just make
-watchdog an alias for -device. Instead of having a global watchdog
action, we should have a watchdog frontend/backend and allow a user to
specify the action for a watchdog backend. This is basically what
-watchdog-action does.
The current command line options assume one global watchdog. I don't
see why we shouldn't support two though. Even if we limited ourselves
to one, it should use the same infrastructure as everything else.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-09-05 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 10:27 [Qemu-devel] [PATCH 0/5] qdev: device capabilities Gerd Hoffmann
2009-08-31 10:27 ` [Qemu-devel] [PATCH 1/5] " Gerd Hoffmann
2009-08-31 10:27 ` [Qemu-devel] [PATCH 2/5] qdev: add audio capability Gerd Hoffmann
2009-08-31 10:27 ` [Qemu-devel] [PATCH 3/5] qdev: add ethernet capability Gerd Hoffmann
2009-08-31 10:27 ` [Qemu-devel] [PATCH 4/5] qdev: add display capability Gerd Hoffmann
2009-08-31 10:27 ` [Qemu-devel] [PATCH 5/5] qdev: add watchdog capability Gerd Hoffmann
2009-09-04 15:08 ` [Qemu-devel] [PATCH 0/5] qdev: device capabilities Anthony Liguori
2009-09-04 15:16 ` Gerd Hoffmann
2009-09-05 13:39 ` Anthony Liguori [this message]
2009-09-07 10:47 ` Gerd Hoffmann
2009-09-07 20:36 ` Anthony Liguori
2009-09-08 6:52 ` Gerd Hoffmann
2009-09-10 16:30 ` Markus Armbruster
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=4AA26A2D.4010605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.