content: Reserve virtio-watchog device ID
PATCH 1/1 content: Reserve virtio-watchog device ID
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.
--- content.tex | 2 ++ 1 file changed, 2 insertions(+)
content.tex +2 -0
@@ -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,
Signature · 18 lines
2.26.2 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: [email protected] Unsubscribe: [email protected] List help: [email protected] 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/
Quoted 4 lines · Rob Bradford
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.
Quoted 1 line
Signed-off-by Rob Bradford <[email protected]>
Signature · 17 lines
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: [email protected] Unsubscribe: [email protected] List help: [email protected] 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/
Quoted 9 lines · Rob Bradford
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 <[email protected]>--- content.tex | 2 ++ 1 file changed, 2 insertions(+)
Quoted 15 lines · On Wed, 21 Oct 2020 14:58:47 +0100 Rob Bradford <[email protected]>…
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 <[email protected]>--- content.tex | 2 ++ 1 file changed, 2 insertions(+)content.tex +0
-0
content.tex \chapter{Device Types}\label{sec:Device Types} · line 2826
Quoted 8 lines
content.tex +2
-0@@ -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,
Time to vote on this (and the patch reserving 34 for I2C?)
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
Quoted 25 lines · Cornelia Huck
Quoted 22 lines · On Wed, 21 Oct 2020 14:58:47 +0100 Rob Bradford <[email protected]>…
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 <[email protected]>--- content.tex | 2 ++ 1 file changed, 2 insertions(+)content.tex +2
-0@@ -2819,6 +2819,8 @@ \chapter{Device Types}\label{sec:Device Types} \hline 33 & NitroSecureModule \\ \hline +35 & Watchdog \\ +\hline \end{tabular}
Quoted 5 lines
content.tex \chapter{Device Types}\label{sec:Device Types} · line 2826
Quoted 1 line
content.tex +0
-0Some of the devices above are unspecified by this document,Reviewed-by Cornelia Huck <[email protected]>Time to vote on this (and the patch reserving 34 for I2C?)
Send Fixes: tag then?
Quoted 8 lines
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.
Quoted 8 lines
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/
PATCH 1/1 content: Reserve virtio-watchdog device ID
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.
--- content.tex | 2 ++ 1 file changed, 2 insertions(+)
content.tex +2 -0
@@ -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,
Signature · 18 lines
2.26.2 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: [email protected] Unsubscribe: [email protected] List help: [email protected] 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/