On 24/12/2015 15:51, Alex Williamson wrote:
> No. A privileged entity needs to grant a user ownership of a group and
> sufficient locked memory limits to make it useful, but then use of the
> group does not require root permission.
So we're thinking how we can force the VFs in these cases to be
inux-
> > p...@vger.kernel.org
> > Cc: bhelg...@google.com; Noa Osherovich <no...@mellanox.com>;
> > Haggai
> > Eran <hagg...@mellanox.com>; Or Gerlitz <ogerl...@mellanox.com>;
> > Liran
> > Liss <lir...@mellanox.com>
> > Subject:
el.org;
linux-...@vger.kernel.org
Cc: bhelg...@google.com; Noa Osherovich <no...@mellanox.com>; Haggai Eran
<hagg...@mellanox.com>; Or Gerlitz <ogerl...@mellanox.com>; Liran Liss
<lir...@mellanox.com>
Subject: Re: [RFC 0/2] VFIO SRIOV support
On Tue, 2015-12-22 at 15
On Wed, 2015-12-23 at 07:43 +, Ilya Lesokhin wrote:
> Hi Alex,
> Regarding driver_override, as far as I know you can only use it on
> devices that were already discovered. Since the devices do not exist
> before the call to pci_enable_sriov(...)
> and are already probed after the call it
no...@mellanox.com>; Haggai
> Eran <hagg...@mellanox.com>; Or Gerlitz <ogerl...@mellanox.com>; Liran
> Liss <lir...@mellanox.com>
> Subject: Re: [RFC 0/2] VFIO SRIOV support
>
> On Wed, 2015-12-23 at 07:43 +, Ilya Lesokhin wrote:
> > Hi A
On Tue, 2015-12-22 at 15:42 +0200, Ilya Lesokhin wrote:
> Today the QEMU hypervisor allows assigning a physical device to a VM,
> facilitating driver development. However, it does not support
> enabling
> SR-IOV by the VM kernel driver. Our goal is to implement such
> support,
> allowing
Today the QEMU hypervisor allows assigning a physical device to a VM,
facilitating driver development. However, it does not support enabling
SR-IOV by the VM kernel driver. Our goal is to implement such support,
allowing developers working on SR-IOV physical function drivers to work
inside VMs as
