RE: [PATCH] content: Replace guest OS with driver

[Parav Pandit <parav@nvidia.com>]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, May 16, 2023 4:48 PM
> 
> On Tue, May 16, 2023 at 07:50:48PM +0000, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin <mst@redhat.com>
> > > Sent: Tuesday, May 16, 2023 6:05 AM
> >
> > >
> > > SO I propose:
> > >
> > > \item[ACKNOWLEDGE (1)] Indicates that a transport driver has found the
> > >     device and recognized it as a valid virtio device transport.
> > >
> > > \item[DRIVER (2)] Indicates that a device type specific driver was found
> > >     and will attempt to attach to the device.
> > >
> > Above bisection is a implementation specific example of Linux (though valid
> and widely used one).
> >
> > The UEFI virtio driver doesn't even have such two drivers.
> > In some OS variant drivers are merged to single kernel binary.
> 
> which one?
> 
Flavor of a RHEL has inbuilt.

> > Does driver only matter with device_driver structure or module binary?...
> 
> Can't parse your question.
> 
> > Driver is largely the software entity that drives the device.
> > I think we can keep the spec simple enough to not mix these details and just
> call it a "driver".
> 
> Not just linux there are lots of drivers like this.  the two bits pass useful
> information the way you changed it this distinction is lots.
> I agree it is worth thinking what exactly does it mean.
> Since you researched it - what exactly do drivers such as uefi and the unnamed
> "some OS variant" do exactly?
There is just one "driver" virtio_net_pci that has sets the required bits.

> when do they set ACKNOWLEDGE and when DRIVER?
> 
Not any different flow.
Entity is one.