From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Bradford, Robert" <robert.bradford@intel.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] Next VirtIO device for Project Stratos?
Date: Wed, 08 Jun 2022 13:38:03 +0100 [thread overview]
Message-ID: <87r13ztjkq.fsf@linaro.org> (raw)
In-Reply-To: <819567d71d72495b6ab71eda915dcfdb8470467b.camel@intel.com>
"Bradford, Robert" <robert.bradford@intel.com> writes:
> On Tue, 2022-05-31 at 09:07 +0100, Alex Bennée wrote:
>> Watchdog / 35
>> -------------
>>
>> Discussion about this is usually conflated with reset functionality
>> as
>> the two are intimately related.
>>
>> An early interest in this was for providing a well specified reset
>> functionality firmware running on the -M virt machine model in QEMU.
>> The
>> need has been reduced somewhat with the provision of the sbsa-ref
>> model
>> which does have a defined reset pin.
>>
>> Other questions that would need to be answered include how the
>> functionality would interact with the hypervisor given a vCPU could
>> easily not be scheduled by it and therefore miss its kick window.
>>
>
> I guess this a risk with any use of a watchdog whether it be emulating
> a physical device or a paravirtualised one. In practice we have never
> seen this.
>
>> Currently there have been no proposals for the spec or
>> implementations.
>
> I was the one who requested the ID be reserved. We have an
> implementation in Cloud Hypervisor:
> https://github.com/cloud-hypervisor/cloud-hypervisor/blob/main/virtio-devices/src/watchdog.rs
>
Ahh good. I guess it could be another cloud hypervisor component that
makes the transition to rust-vmm if there is interest?
> As well as the kernel side:
>
> https://github.com/cloud-hypervisor/linux/commit/cc8f7579faad79cdf02f9b6a742510cd1b1cf340
>
> I admit writing up a patch for the specification fell through the
> cracks. That's something I will try to rectify in the near future as it
> would also be nice to be able to upstream the kernel patch.
Thanks, please feel free to Cc me on any such patches and we can take a
look.
--
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:[~2022-06-08 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 8:07 [virtio-comment] Next VirtIO device for Project Stratos? Alex Bennée
2022-06-06 9:35 ` Bradford, Robert
2022-06-08 12:38 ` Alex Bennée [this message]
[not found] ` <80aace95-6c39-c7b9-61ba-70d60bcd08b2@quicinc.com>
[not found] ` <c642058f36321cb7dfdfaa4664f5323841b65450.camel@sipsolutions.net>
[not found] ` <a3856ec8-90d6-df19-2b5f-bc42700b09db@quicinc.com>
2022-06-08 12:28 ` [virtio-comment] Re: [Stratos-dev] " Alex Bennée
2022-09-03 7:43 ` [virtio-dev] " Alyssa Ross
2022-09-05 15:22 ` [virtio-comment] " Alex Bennée
2022-09-06 7:47 ` [virtio-dev] Re: [Stratos-dev] " Alyssa Ross
2022-09-05 20:27 ` [virtio-comment] " Stefan Hajnoczi
2022-09-06 17:33 ` Dr. David Alan Gilbert
2022-09-06 18:12 ` Stefan Hajnoczi
2022-09-07 14:09 ` Dr. David Alan Gilbert
2022-09-07 17:15 ` Stefan Hajnoczi
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=87r13ztjkq.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--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 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.