From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Having troubles binding an SR-IOV VF to
 uio_pci_generic on Amazon instance
Date: Thu, 1 Oct 2015 12:29:11 +0300
Message-ID: <20151001121638-mutt-send-email-mst@redhat.com>
References: <20150930151632-mutt-send-email-mst@redhat.com>
 <560BDE24.8000308@scylladb.com>
 <20150930165359-mutt-send-email-mst@redhat.com>
 <560BF782.4070308@scylladb.com>
 <20150930175848-mutt-send-email-mst@redhat.com>
 <560C0171.7080507@scylladb.com> <20150930204016.GA29975@redhat.com>
 <20151001113828-mutt-send-email-mst@redhat.com>
 <560CF44A.60102@scylladb.com> <560CF9C5.8050901@scylladb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: Avi Kivity <avi@scylladb.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id D7F608E61
 for <dev@dpdk.org>; Thu,  1 Oct 2015 11:29:15 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <560CF9C5.8050901@scylladb.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, Oct 01, 2015 at 12:15:49PM +0300, Avi Kivity wrote:
>     What userspace can't be allowed to do:
>=20
>             access BAR
>             write rings
>=20
>=20
>=20
>=20
> It can access the BAR by mmap()ing the resourceN files under sysfs.=A0 =
You're not
> denying userspace the ability to oops the kernel, just the ability to d=
o useful
> things with hardware.


This interface has to stay there to support existing applications.  A
variety of measures (selinux, secureboot) can be used to make sure
modern ones to not get to touch it. Most distributions enable
some or all of these by default.

And it doesn't mean modern drivers can do this kind of thing.

Look, without an IOMMU, sysfs can not be used securely:
you need some other interface. This is what this driver is missing.

--=20
MST