search for: device_needs_reset

...and report to userspace, or recover the device by > resetting it. Unfortunately, virtio 1 spec does not have a conformance statement that requires driver to recover. We merely have a non-normative looking text: Note: For example, the driver can?t assume requests in flight will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that they have not been completed. A good implementation will try to recover by issuing a reset. Implementing this reset for all devices in a race-free manner might also be far from trivial. I think we'd need a feature bit for this. OTOH as long as we make this a n...

...and report to userspace, or recover the device by > resetting it. Unfortunately, virtio 1 spec does not have a conformance statement that requires driver to recover. We merely have a non-normative looking text: Note: For example, the driver can?t assume requests in flight will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that they have not been completed. A good implementation will try to recover by issuing a reset. Implementing this reset for all devices in a race-free manner might also be far from trivial. I think we'd need a feature bit for this. OTOH as long as we make this a n...

...ting it. > > > > Unfortunately, virtio 1 spec does not have a conformance statement > > that requires driver to recover. We merely have a non-normative looking > > text: > > Note: For example, the driver can?t assume requests in flight > > will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that > > they have not been completed. A good implementation will try to recover > > by issuing a reset. > > > > Implementing this reset for all devices in a race-free manner might also > > be far from trivial. I think we'd need a feat...

...ting it. > > > > Unfortunately, virtio 1 spec does not have a conformance statement > > that requires driver to recover. We merely have a non-normative looking > > text: > > Note: For example, the driver can?t assume requests in flight > > will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that > > they have not been completed. A good implementation will try to recover > > by issuing a reset. > > > > Implementing this reset for all devices in a race-free manner might also > > be far from trivial. I think we'd need a feat...

...the device by > > resetting it. > > Unfortunately, virtio 1 spec does not have a conformance statement > that requires driver to recover. We merely have a non-normative looking > text: > Note: For example, the driver can?t assume requests in flight > will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that > they have not been completed. A good implementation will try to recover > by issuing a reset. > > Implementing this reset for all devices in a race-free manner might also > be far from trivial. I think we'd need a feature bit for this. > OT...

...> > Unfortunately, virtio 1 spec does not have a conformance statement > > > that requires driver to recover. We merely have a non-normative looking > > > text: > > > Note: For example, the driver can?t assume requests in flight > > > will be completed if DEVICE_NEEDS_RESET is set, nor can it assume that > > > they have not been completed. A good implementation will try to recover > > > by issuing a reset. > > > > > > Implementing this reset for all devices in a race-free manner might also > > > be far from trivial. I t...