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: [PATCH v6 3/4] admin: Add group member legacy register access commands



> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Monday, June 19, 2023 12:40 PM
> > >
> > > we can just say "the legacy interface of member devices"
> > >
> > What is the harm in telling explicitly what is currently supported, specially
> when it theory of operation description section.
> 
> The harm is that
> - making things generic on the 1st try is the only stick we have
>   as contributors always push to make their solutions as
>   specific to their needs as possible
> - people are lazy and they will copy text and then I get to repeat this argument
> all over again.
>

The "legacy interface of member device" is a vague term. As implementer, reader I don't understand what that means.
The commands clearly communicate the scope.
 
> If you want to also have a type specific text, be my guest "specifically, for an
> SRIOV type" ....
> 
SRIOV in generic section doesn't make sense. It is covered in the pci transport section.

> 
> > > > using following listed
> > >
> > > using the following
> > >
> > > > +administrative commands:
> > >
> > > administration not administrative
> > >
> > Ack.



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