Re: [PATCH V8] virtio-transport: Add a section to define mandatory transport requirements

["Michael S. Tsirkin" <mst@redhat.com>]

On Wed, Jul 31, 2024 at 12:15:30PM +0200, Cornelia Huck wrote:
> On Wed, Jul 31 2024, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Wed, Jul 31, 2024 at 11:43:13AM +0200, Cornelia Huck wrote:
> >> On Wed, Jul 31 2024, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >> 
> >> > On 30-07-24, 09:14, Michael S. Tsirkin wrote:
> >> >> Let's order it sensibly though, in the order in which stuff is used
> >> >
> >> > Right.
> >> >
> >> > diff --git a/newtransport.tex b/newtransport.tex
> >> > new file mode 100644
> >> > index 000000000000..3b760250a4c0
> >> > --- /dev/null
> >> > +++ b/newtransport.tex
> >> > @@ -0,0 +1,44 @@
> >> > +\chapter{Creating New Transports}\label{sec:Creating New Transports}
> >> > +
> >> > +Devices and drivers utilize various transport methods to facilitate
> >> > +communication, such as PCI, MMIO, or Channel I/O. These transport
> >> > +methods determine multiple aspects of the interaction between the device
> >> > +and the driver, including device discovery, capability exchange,
> >> > +interrupt handling, and data transfer. For instance, in a host/guest
> >> > +architecture, the host might expose a device to the guest via a virtual
> >> > +PCI bus, and the guest would employ a PCI device driver to interface
> >> > +with the device.
> >> > +
> >> > +This section outlines the mandatory requirements that a transport method
> >> > +implements.
> >> > +
> >> > +A transport provides a mechanism to implement configuration space for
> >> > +the device.
> >> > +
> >> > +A transport provides a mechanism for the driver to identify the device
> >> > +type.
> >> > +
> >> > +A transport provides a mechanism for the driver to read the device's
> >> > +status bit.
> >> 
> >> Either "status bits", or "status" (as below.)
> >
> > It is actually "FEATURES_OK status bit" I think.
> 
> Also DEVICE_NEEDS_RESET?

Good point.

> I don't think it makes sense to say that the
> driver needs a way to read individual bits, it should be able to read
> the whole status.

It depends on the transport, I can imagine a transport that
saves some space by not keeping a copy of e.g. DRIVER.

-- 
MST