From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by dpdk.org (Postfix) with ESMTP id 305801AFFF; Fri, 20 Apr 2018 16:56:08 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C671781A88A0; Fri, 20 Apr 2018 14:56:07 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.61]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 58D29AFD6E; Fri, 20 Apr 2018 14:56:07 +0000 (UTC) From: Aaron Conole To: Ferruh Yigit Cc: Alejandro Lucero , dev , Adrien Mazarguil , stable@dpdk.org, Thomas Monjalon References: <20180412222208.11770-1-aconole@redhat.com> <20180412222208.11770-3-aconole@redhat.com> <5d0e69b9-3655-f3f6-9cbb-1090b9471813@intel.com> Date: Fri, 20 Apr 2018 10:56:06 -0400 In-Reply-To: <5d0e69b9-3655-f3f6-9cbb-1090b9471813@intel.com> (Ferruh Yigit's message of "Fri, 20 Apr 2018 15:12:28 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Fri, 20 Apr 2018 14:56:07 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Fri, 20 Apr 2018 14:56:07 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'aconole@redhat.com' RCPT:'' Subject: Re: [dpdk-stable] [RFC 2/2] nfp: allow for non-root user X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2018 14:56:08 -0000 Ferruh Yigit writes: > On 4/19/2018 7:05 AM, Alejandro Lucero wrote: >> On Wed, Apr 18, 2018 at 1:32 PM, Aaron Conole wrote: >> >>> Alejandro Lucero writes: >>> >>>> On Tue, Apr 17, 2018 at 8:19 PM, Aaron Conole >>> wrote: >>>> >>>> Alejandro Lucero writes: >>>> >>>> > I was just wondering, if device device PCI sysfs resource files or >>> VFIO group /dev files >>>> require to change >>>> > permissions for non-root users, does it not make sense to adjust also >>> /var/lock in the >>>> system? >>>> >>>> For the /dev, we use udev rules - so the correct individual vfio device >>>> files get assigned the correct permissions. No such mechanism exists >>>> for /var/lock as far as I can tell. >>>> >>>> Ex. see: >>>> >>>> https://github.com/openvswitch/ovs/blob/master/ >>> rhel/usr_lib_udev_rules.d_91-vfio.rules >>>> >>>> >>>> Maybe something similar exists that we could use to generate the lock >>>> file automatically? >>>> >>>> What about /sysfs/bus/pci/device/$PCI_DEV/resource file? >>>> >>>> Is RH forcing OVS DPDK to only work if the host has IOMMU support? >>> >>> Yes. >>> >> >> Ok then. It makes sense now to apply this patch to stable versions. >> >> Acked-by: Alejandro Lucero > > Since the target is the stable tree, I will drop them from patchwork as not > applicable. > > Can you please send v1 of the patch to the stable mail list, it can be good idea > to cc stable maintainers as well. Will do. I'll spin into a proper series and submit next week. Sorry for the extra noise, Ferruh.