From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Yoni Bettan <ybettan@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, Amnon Ilan <ailan@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [RFC-PATCH] Introducing virtio-example device.
Date: Wed, 10 Apr 2019 21:30:56 -0400 [thread overview]
Message-ID: <20190410213001-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJSP0QVpPGKO_NH2CXpdYtQfLsMF+OjKx2QzjtKJVkOnnoBHdw@mail.gmail.com>
On Wed, Apr 10, 2019 at 08:15:32PM +0100, Stefan Hajnoczi wrote:
> On Wed, Apr 10, 2019 at 4:45 PM Yoni Bettan <ybettan@redhat.com> wrote:
> > On 4/9/19 4:17 PM, Stefan Hajnoczi wrote:
> > > On Mon, Apr 01, 2019 at 02:18:43PM +0300, Yoni Bettan wrote:
> > The final purpose is to have:
> >
> > 1. device specification
> >
> > 2. device implementation
> >
> > 3. device driver
> >
> > 4. blog
> >
> > maybe I should have written it at the beginning, this is not the entire
> > project but it is its start.
>
> The way I'd design VIRTIO devices without prior knowledge is:
>
> 1. Learn the VIRTIO device model. Understand the concepts in VIRTIO.
> <-- this is hard today, there's not much good documentation
Best doc is still probably Rusty's whitepaper. It only covers 0.X
spec so somewhat outdated but it does explain the concepts I think.
> 2. Design an initial version of the device spec. Mostly configuration
> layout, virtqueues, and request structs. Not much text is necessary
> at this point, but it's critical for thinking through features before
> implementation.
>
> 3. Implement guest driver and device emulation.
>
> 4. Iterate on spec and implementation until it's functionally complete.
>
> 5. Submit the spec to the VIRTIO Technical Committee.
>
> 6. Submit driver and device emulation patches. They can be merged
> when the spec is approved/close to approved.
>
> Are you jumping to #3? This is likely to lead to poor quality
> implementations and specs because the fundamental VIRTIO concepts
> weren't understood.
>
> If the point is to educate others and/or do it "the right way", then I
> would really avoid hacking around without first doing the other steps.
>
> Stefan
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Yoni Bettan <ybettan@redhat.com>, Amnon Ilan <ailan@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [RFC-PATCH] Introducing virtio-example device.
Date: Wed, 10 Apr 2019 21:30:56 -0400 [thread overview]
Message-ID: <20190410213001-mutt-send-email-mst@kernel.org> (raw)
Message-ID: <20190411013056.aB_ieZUEb2MYAG0xVmRV98QXY4CLXW5Oe__rCwKZwik@z> (raw)
In-Reply-To: <CAJSP0QVpPGKO_NH2CXpdYtQfLsMF+OjKx2QzjtKJVkOnnoBHdw@mail.gmail.com>
On Wed, Apr 10, 2019 at 08:15:32PM +0100, Stefan Hajnoczi wrote:
> On Wed, Apr 10, 2019 at 4:45 PM Yoni Bettan <ybettan@redhat.com> wrote:
> > On 4/9/19 4:17 PM, Stefan Hajnoczi wrote:
> > > On Mon, Apr 01, 2019 at 02:18:43PM +0300, Yoni Bettan wrote:
> > The final purpose is to have:
> >
> > 1. device specification
> >
> > 2. device implementation
> >
> > 3. device driver
> >
> > 4. blog
> >
> > maybe I should have written it at the beginning, this is not the entire
> > project but it is its start.
>
> The way I'd design VIRTIO devices without prior knowledge is:
>
> 1. Learn the VIRTIO device model. Understand the concepts in VIRTIO.
> <-- this is hard today, there's not much good documentation
Best doc is still probably Rusty's whitepaper. It only covers 0.X
spec so somewhat outdated but it does explain the concepts I think.
> 2. Design an initial version of the device spec. Mostly configuration
> layout, virtqueues, and request structs. Not much text is necessary
> at this point, but it's critical for thinking through features before
> implementation.
>
> 3. Implement guest driver and device emulation.
>
> 4. Iterate on spec and implementation until it's functionally complete.
>
> 5. Submit the spec to the VIRTIO Technical Committee.
>
> 6. Submit driver and device emulation patches. They can be merged
> when the spec is approved/close to approved.
>
> Are you jumping to #3? This is likely to lead to poor quality
> implementations and specs because the fundamental VIRTIO concepts
> weren't understood.
>
> If the point is to educate others and/or do it "the right way", then I
> would really avoid hacking around without first doing the other steps.
>
> Stefan
next prev parent reply other threads:[~2019-04-11 1:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 11:18 [Qemu-devel] [RFC-PATCH] Introducing virtio-example device Yoni Bettan
2019-04-05 21:30 ` Eduardo Habkost
2019-04-05 21:30 ` Eduardo Habkost
2019-04-09 13:17 ` Stefan Hajnoczi
2019-04-09 13:17 ` Stefan Hajnoczi
2019-04-10 15:45 ` Yoni Bettan
2019-04-10 15:45 ` Yoni Bettan
2019-04-10 19:15 ` Stefan Hajnoczi
2019-04-10 19:15 ` Stefan Hajnoczi
2019-04-11 1:30 ` Michael S. Tsirkin [this message]
2019-04-11 1:30 ` Michael S. Tsirkin
2019-04-10 19:25 ` Stefan Hajnoczi
2019-04-10 19:25 ` Stefan Hajnoczi
2019-04-14 11:20 ` Yoni Bettan
2019-04-14 11:20 ` Yoni Bettan
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=20190410213001-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ailan@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=ybettan@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).