On 26/10/2023 20:55, Alex Williamson wrote:
On Thu, 26 Oct 2023 15:08:12 +0300
Yishai Hadas wrote:
On 25/10/2023 22:13, Alex Williamson wrote:
On Wed, 25 Oct 2023 17:35:51 +0300
Yishai Hadas wrote:
On 24/10/2023 22:57, Alex Williamson wrote:
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai
On Thu, Oct 26, 2023 at 11:55:39AM -0600, Alex Williamson wrote:
> On Thu, 26 Oct 2023 15:08:12 +0300
> Yishai Hadas wrote:
>
> > On 25/10/2023 22:13, Alex Williamson wrote:
> > > On Wed, 25 Oct 2023 17:35:51 +0300
> > > Yishai Hadas wrote:
> > >
> > >> On 24/10/2023 22:57, Alex Williamson
On Thu, 26 Oct 2023 15:08:12 +0300
Yishai Hadas wrote:
> On 25/10/2023 22:13, Alex Williamson wrote:
> > On Wed, 25 Oct 2023 17:35:51 +0300
> > Yishai Hadas wrote:
> >
> >> On 24/10/2023 22:57, Alex Williamson wrote:
> >>> On Tue, 17 Oct 2023 16:42:17 +0300
> >>> Yishai Hadas wrote:
>
> From: Michael S. Tsirkin
> Sent: Thursday, October 26, 2023 9:16 PM
> On Thu, Oct 26, 2023 at 03:09:13PM +, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin
> > > Sent: Thursday, October 26, 2023 8:36 PM
> > >
> > > On Thu, Oct 26, 2023 at 01:28:18PM +, Parav Pandit wrote:
> >
On Thu, Oct 26, 2023 at 03:09:13PM +, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin
> > Sent: Thursday, October 26, 2023 8:36 PM
> >
> > On Thu, Oct 26, 2023 at 01:28:18PM +, Parav Pandit wrote:
> > >
> > > > From: Michael S. Tsirkin
> > > > Sent: Thursday, October 26, 2023 6:45
> From: Michael S. Tsirkin
> Sent: Thursday, October 26, 2023 8:36 PM
>
> On Thu, Oct 26, 2023 at 01:28:18PM +, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin
> > > Sent: Thursday, October 26, 2023 6:45 PM
> >
> > > > Followed by an open coded driver check for 0x1000 to 0x103f
On Thu, Oct 26, 2023 at 01:28:18PM +, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin
> > Sent: Thursday, October 26, 2023 6:45 PM
>
> > > Followed by an open coded driver check for 0x1000 to 0x103f range.
> > > Do you mean windows driver expects specific subsystem vendor id of 0x1af4?
>
> From: Michael S. Tsirkin
> Sent: Thursday, October 26, 2023 6:45 PM
> > Followed by an open coded driver check for 0x1000 to 0x103f range.
> > Do you mean windows driver expects specific subsystem vendor id of 0x1af4?
>
> Look it up, it's open source.
Those are not OS inbox drivers anyway.
On Thu, Oct 26, 2023 at 12:40:04PM +, Parav Pandit wrote:
> > From: Michael S. Tsirkin
> > Sent: Thursday, October 26, 2023 5:42 PM
> >
> > On Thu, Oct 26, 2023 at 03:08:12PM +0300, Yishai Hadas wrote:
> > > > > Makes sense ?
> > > > So do I understand correctly that virtio dictates the
> From: Michael S. Tsirkin
> Sent: Thursday, October 26, 2023 5:42 PM
>
> On Thu, Oct 26, 2023 at 03:08:12PM +0300, Yishai Hadas wrote:
> > > > Makes sense ?
> > > So do I understand correctly that virtio dictates the subsystem
> > > device ID for all subsystem vendor IDs that implement a legacy
On Thu, Oct 26, 2023 at 03:08:12PM +0300, Yishai Hadas wrote:
> > > Makes sense ?
> > So do I understand correctly that virtio dictates the subsystem device
> > ID for all subsystem vendor IDs that implement a legacy virtio
> > interface? Ok, but this device didn't actually implement a legacy
> >
On 25/10/2023 22:13, Alex Williamson wrote:
On Wed, 25 Oct 2023 17:35:51 +0300
Yishai Hadas wrote:
On 24/10/2023 22:57, Alex Williamson wrote:
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai Hadas wrote:
Introduce a vfio driver over virtio devices to support the legacy
interface functionality
On Wed, 25 Oct 2023 17:35:51 +0300
Yishai Hadas wrote:
> On 24/10/2023 22:57, Alex Williamson wrote:
> > On Tue, 17 Oct 2023 16:42:17 +0300
> > Yishai Hadas wrote:
> >
> >> Introduce a vfio driver over virtio devices to support the legacy
> >> interface functionality for VFs.
> >>
> >>
On Wed, Oct 25, 2023 at 05:35:51PM +0300, Yishai Hadas wrote:
> > Do we want to make this only probe the correct subsystem vendor ID or do
> > we want to emulate the subsystem vendor ID as well? I don't see this is
> > correct without one of those options.
>
> Looking in the 1.x spec we can see
On 24/10/2023 22:57, Alex Williamson wrote:
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai Hadas wrote:
Introduce a vfio driver over virtio devices to support the legacy
interface functionality for VFs.
Background, from the virtio spec [1].
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai Hadas wrote:
> Introduce a vfio driver over virtio devices to support the legacy
> interface functionality for VFs.
>
> Background, from the virtio spec [1].
>
> In some systems, there
On Wed, 18 Oct 2023 13:33:33 -0300
Jason Gunthorpe wrote:
> On Tue, Oct 17, 2023 at 02:24:48PM -0600, Alex Williamson wrote:
> > On Tue, 17 Oct 2023 16:42:17 +0300
> > Yishai Hadas wrote:
> > > +static int virtiovf_pci_probe(struct pci_dev *pdev,
> > > + const struct
> From: Alex Williamson
> Sent: Wednesday, October 18, 2023 6:22 PM
> Are we realistically extending this beyond virtio-net? Maybe all the
> descriptions
> should be limited to what is actually supported as proposed rather than
> aspirational goals. Thanks,
Virtio blk would the second user
On Wed, 18 Oct 2023 12:01:57 +0300
Yishai Hadas wrote:
> On 17/10/2023 23:24, Alex Williamson wrote:
> > On Tue, 17 Oct 2023 16:42:17 +0300
> > Yishai Hadas wrote:
> >> +static int virtiovf_pci_probe(struct pci_dev *pdev,
> >> +const struct pci_device_id *id)
> >> +{
>
On 17/10/2023 23:24, Alex Williamson wrote:
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai Hadas wrote:
+static int virtiovf_pci_probe(struct pci_dev *pdev,
+ const struct pci_device_id *id)
+{
+ const struct vfio_device_ops *ops = _acc_vfio_pci_ops;
+ struct
On Tue, 17 Oct 2023 16:42:17 +0300
Yishai Hadas wrote:
> +static int virtiovf_pci_probe(struct pci_dev *pdev,
> + const struct pci_device_id *id)
> +{
> + const struct vfio_device_ops *ops = _acc_vfio_pci_ops;
> + struct virtiovf_pci_core_device *virtvdev;
> +
Introduce a vfio driver over virtio devices to support the legacy
interface functionality for VFs.
Background, from the virtio spec [1].
In some systems, there is a need to support a virtio legacy driver with
a device that does
22 matches
Mail list logo
