qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoni Bettan <ybettan@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Amnon Ilan <ailan@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC-PATCH] Introducing virtio-example device.
Date: Sun, 14 Apr 2019 14:20:36 +0300	[thread overview]
Message-ID: <f5f1fafe-4eda-03bd-ba1f-38c08cb381a3@redhat.com> (raw)
In-Reply-To: <CAJSP0QWYS+UHmXyvhtLcLW9iumfi29Fa7AJdGPC9OwagwekWmg@mail.gmail.com>


On 4/10/19 10:25 PM, 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:
>>> There are multiple problems with the code, but the larger issue is that
>>> this example device is just helping people shoot themselves in the foot
>>> more easily.
>>
>> If you can point me to those problem I will be glad so I can update the
>> code and understand those problems you are talking about.
> Please see Eduardo's reply.  I didn't review much since he already
> pointed out many things.
>
> One thing he didn't mention:
> +    elem = virtqueue_pop(vq, sizeof(VirtQueueElement));
>
> The return value can be NULL.  Spurious notifications could happen so
> the code shouldn't crash when this returns NULL.
>
> I apologize for the critical replies.  What you're doing is valuable.
> I think explaining the VIRTIO device model and the order in which
> things are done will lead to higher quality devices so I'm making a
> lot of noise about it :).


It is OK, I will write some basic specification for the device and start 
iterating spec-device-driver according to Rustie's paper, Eduardo's 
review, and you advice.


Thanks.

>
> Stefan

WARNING: multiple messages have this Message-ID (diff)
From: Yoni Bettan <ybettan@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Michael S. Tsirkin" <mst@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: Sun, 14 Apr 2019 14:20:36 +0300	[thread overview]
Message-ID: <f5f1fafe-4eda-03bd-ba1f-38c08cb381a3@redhat.com> (raw)
Message-ID: <20190414112036.ESb2pTVlzvQq4Ua03ir78ID8T7hEvuszOnp5aAhAT8A@z> (raw)
In-Reply-To: <CAJSP0QWYS+UHmXyvhtLcLW9iumfi29Fa7AJdGPC9OwagwekWmg@mail.gmail.com>


On 4/10/19 10:25 PM, 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:
>>> There are multiple problems with the code, but the larger issue is that
>>> this example device is just helping people shoot themselves in the foot
>>> more easily.
>>
>> If you can point me to those problem I will be glad so I can update the
>> code and understand those problems you are talking about.
> Please see Eduardo's reply.  I didn't review much since he already
> pointed out many things.
>
> One thing he didn't mention:
> +    elem = virtqueue_pop(vq, sizeof(VirtQueueElement));
>
> The return value can be NULL.  Spurious notifications could happen so
> the code shouldn't crash when this returns NULL.
>
> I apologize for the critical replies.  What you're doing is valuable.
> I think explaining the VIRTIO device model and the order in which
> things are done will lead to higher quality devices so I'm making a
> lot of noise about it :).


It is OK, I will write some basic specification for the device and start 
iterating spec-device-driver according to Rustie's paper, Eduardo's 
review, and you advice.


Thanks.

>
> Stefan


  parent reply	other threads:[~2019-04-14 11:20 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
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 [this message]
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=f5f1fafe-4eda-03bd-ba1f-38c08cb381a3@redhat.com \
    --to=ybettan@redhat.com \
    --cc=ailan@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).