Re: [virtio-comment] Formal specification of virtIO

["Michael S. Tsirkin" <mst@redhat.com>]

On Sun, Nov 10, 2019 at 03:33:20PM +0100, Matias Vara wrote:
> Hello everyone,
> 
> I have started to think of the formalization of the virtIO specification.
> Roughly speaking, I could use a formal language to "code" the virtIO spec. As
> far as I can think, this has three benefits: 
> 1. You can validate any implementation.
> 2. You can generate the implementation for a given target. For example, you
> could be able to generate the implementation of a virtIO device in VHDL. 
> 3. You can provide simulation and verification before any implementation. In
> automotive, this is interesting because you ease the certification so
> formalization pays off. 
> 
> Do you think this may be interesting work to do to become the virtIO
> specification more robust? 
> 
> Regards, Matias.       

I think the most intersting thing to model would be the virtqueue for
systems with weak memory concurrency. Right now we have two virtqueue
formats and getting concurrency right is the hardest part.  Having a
formal model would be useful so we can extend the ring. Paul E.
McKenney's talks gave me the impression that modeling any kind of weak
memory concurrency is very challenging though.

-- 
MST


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/