OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [Qemu-devel] [virtio-dev] Re: [v22 1/2] virtio-crypto: Add virtio crypto device specification

On 12/18/2017 02:51 PM, Michael S. Tsirkin wrote:
> On Mon, Dec 18, 2017 at 01:29:50PM +0100, Halil Pasic wrote:
>> It isn't a big structural thing, but inconsistent wording can make
>> difficult to understand stuff even more difficult to understand.
>> This wording stuff is not a show-stopper for me.
> Right. There's a working implementation upstream that people use,
> so at this point we really need a description of that upstream,
> and add wording tweaks on top. And it's too late to change the
> interface drastically, any change must be compatible using
> feature bits for anything we want changed.

I fully agree. Please bear with me if end up complaining about
minor stuff identified while reviewing the spec and cross check
it with the implementation to make sure there is nothing major wrong.

>>>> * I assume one request is supposed to correspond to one descriptor chain.
>>>> Right? If yes, could you tell me, where is this expressed in the spec.
>> You have ignored this one. Michael said it's the default for the whole
>> spec, but I still don't know where is this requirement to be found
>> in the spec.
> I was surprised to find this does not say this explicitly anywhere.
> I this we should add something like the below to the Virtqueues
> chapter:
> 	Driver makes requests available to device by adding an available buffer
> 	to the queue - i.e. adding a buffer describing the request to a
> 	virtqueue, and optionally triggering a driver event - i.e. sending a
> 	notification to the device.  Device executes the requests and - when
> 	complete - adds a used buffer to the queue - i.e. lets the driver know
> 	by marking the buffer as used. Device can then trigger a device event -
> 	i.e. send an interrupt to the driver.

Thanks for verifying this. I can spin a patch addressing the issue, if you like.

If I'm going to do the patch, I would like take your text as a starting
point of (with your kind permission), but I would rather see this as belonging
to "3.2 Device Operation". (It's not about how virtqueues work, but how
virtio devices use virtqueues to do their thing.)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]