[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [PATCH] content: Replace guest OS with driver
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? > 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? when do they set ACKNOWLEDGE and when DRIVER? > > > > BTW somewhat related, I would maybe fix > > device-types/mem/description.tex:change > > not to say "device driver", just "driver" for brevity. > > > Ok. will fix.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]