From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Rob Bradford <robert.bradford@intel.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH] content: Reserve virtio-watchog device ID
Date: Thu, 29 Oct 2020 06:36:13 -0400 [thread overview]
Message-ID: <20201029063557-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20201029102536.4c8965a8.cohuck@redhat.com>
On Thu, Oct 29, 2020 at 10:25:36AM +0100, Cornelia Huck wrote:
> On Wed, 21 Oct 2020 14:58:47 +0100
> Rob Bradford <robert.bradford@intel.com> wrote:
>
> > 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.
> >
> > Signed-off-by: Rob Bradford <robert.bradford@intel.com>
> > ---
> > content.tex | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/content.tex b/content.tex
> > index bc26674..6f8ec8f 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -2819,6 +2819,8 @@ \chapter{Device Types}\label{sec:Device Types}
> > \hline
> > 33 & NitroSecureModule \\
> > \hline
> > +35 & Watchdog \\
> > +\hline
> > \end{tabular}
> >
> > Some of the devices above are unspecified by this document,
>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>
> Time to vote on this (and the patch reserving 34 for I2C?)
Send Fixes: tag then?
>
> 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/
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-29 10:36 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
2020-10-23 13:48 ` Stefan Hajnoczi
2020-10-29 9:25 ` Cornelia Huck
2020-10-29 10:36 ` Michael S. Tsirkin [this message]
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=20201029063557-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=robert.bradford@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox