On Fri, Oct 18, 2019 at 10:33:47AM +0200, David Marchand wrote:
> On Fri, Oct 18, 2019 at 10:19 AM Tiwei Bie wrote:
> > On Thu, Oct 17, 2019 at 01:56:28PM +0200, David Marchand wrote:
> > > On x86, iopl permissions are only needed when the virtio devices are
> > > bound to a uio kernel module.
> >
On Fri, Oct 18, 2019 at 10:19 AM Tiwei Bie wrote:
>
> On Thu, Oct 17, 2019 at 01:56:28PM +0200, David Marchand wrote:
> > On x86, iopl permissions are only needed when the virtio devices are
> > bound to a uio kernel module.
> >
> > When running a dpdk application as non root, the virtio driver wa
On Thu, Oct 17, 2019 at 01:56:28PM +0200, David Marchand wrote:
> On x86, iopl permissions are only needed when the virtio devices are
> bound to a uio kernel module.
>
> When running a dpdk application as non root, the virtio driver was
> refusing to register because of this check while it could
On x86, iopl permissions are only needed when the virtio devices are
bound to a uio kernel module.
When running a dpdk application as non root, the virtio driver was
refusing to register because of this check while it could work when
binding the device to vfio (requires to have a vIOMMU configured
4 matches
Mail list logo