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

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

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


Subject: RE: [virtio-comment] RE: [PATCH v13] virtio-net: support the virtqueue coalescing moderation


> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Wednesday, March 22, 2023 12:44 PM
> 
> >> Well, I think we want to avoid having to add a normative statement
> >> for the device, so we need to be strict with what the driver is allowed to do.
> > Drivers are untrusted entities.
> > device normative statement is needed, it will do the checks anyway where it
> is applying the config.
> 
> But isn't that implementation specific? I.e. if the driver sends junk, the device
> needs to be able to deal with it in any case.
Not sure which part is implementation specific.
The device will deal with it and return an error code when supplied qid is invalid (of cvq or of disabled vq).


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