From: "Alex Bennée" <alex.bennee@linaro.org>
To: Rob Bradford <robert.bradford@intel.com>
Cc: virtio-comment@lists.oasis-open.org,
Stratos-dev <stratos-dev@op-lists.linaro.org>
Subject: Re: [virtio-comment] [PATCH] content: Reserve virtio-watchog device ID
Date: Thu, 22 Oct 2020 16:09:53 +0100 [thread overview]
Message-ID: <874kmmuwji.fsf@linaro.org> (raw)
In-Reply-To: <20201021135847.15236-1-robert.bradford@intel.com>
Rob Bradford <robert.bradford@intel.com> writes:
> Reserve an ID for a watchdog device which may be used to ensure that the
> guest is responsive. This is equivalent of a hardware watchdog device
> and will trigger the reboot of the guest if the the host does not
> periodic ping from the the guest.
Out of interest is your watchdog device also going to allow for straight
power/reset control?
The use case I'm thinking of is QEMU's -m virt machine which is a purely
virtual machine which is a target for a number of firmware/bootcode
projects. QEMU provides a firmware emulation that will do the right
thing if you issue PSCI supervisor calls and you have directly loaded a
kernel. However if you are testing firmware - for example EDK2 or Arm
Trusted Firmware it is expected to make the final hw appropriate twiddle
to reboot the machine and of course that is undefined for -m virt.
> Signed-off-by: Rob Bradford <robert.bradford@intel.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-10-22 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 13:58 [virtio-comment] [PATCH] content: Reserve virtio-watchog device ID Rob Bradford
2020-10-22 15:09 ` Alex Bennée [this message]
2020-10-23 13:48 ` Stefan Hajnoczi
2020-10-29 9:25 ` Cornelia Huck
2020-10-29 10:36 ` Michael S. Tsirkin
2020-10-30 16:34 ` [virtio-comment] [PATCH] content: Reserve virtio-watchdog " Rob Bradford
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=874kmmuwji.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=robert.bradford@intel.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=virtio-comment@lists.oasis-open.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.