From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>,
Aaron Conole <aconole@redhat.com>
Cc: dev <dev@dpdk.org>, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
stable@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] [RFC 2/2] nfp: allow for non-root user
Date: Fri, 20 Apr 2018 15:12:28 +0100 [thread overview]
Message-ID: <5d0e69b9-3655-f3f6-9cbb-1090b9471813@intel.com> (raw)
In-Reply-To: <CAD+H993ZxZ=idsEM1P=on3r7DFPMz7gaea1QmBjO9Uw2o6Nu=A@mail.gmail.com>
On 4/19/2018 7:05 AM, Alejandro Lucero wrote:
> On Wed, Apr 18, 2018 at 1:32 PM, Aaron Conole <aconole@redhat.com> wrote:
>
>> Alejandro Lucero <alejandro.lucero@netronome.com> writes:
>>
>>> On Tue, Apr 17, 2018 at 8:19 PM, Aaron Conole <aconole@redhat.com>
>> wrote:
>>>
>>> Alejandro Lucero <alejandro.lucero@netronome.com> 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 <alejandro.lucero@netronome.com>
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.
next prev parent reply other threads:[~2018-04-20 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180412222208.11770-1-aconole@redhat.com>
[not found] ` <CAD+H9916Rjwup_RVkBiLP6yM60n-T+XhdKHYA_q_4pw94XW9Cw@mail.gmail.com>
[not found] ` <f7tin8vz1dz.fsf@dhcp-25.97.bos.redhat.com>
2018-04-13 15:36 ` [dpdk-stable] [RFC 0/2] nfp driver fixes Alejandro Lucero
[not found] ` <20180412222208.11770-3-aconole@redhat.com>
[not found] ` <CAD+H991rVEhppb1ubjer9mjd0kg6aYBunuqd-mufKa=EPPJ3-w@mail.gmail.com>
[not found] ` <f7ta7u7z10q.fsf@dhcp-25.97.bos.redhat.com>
[not found] ` <CAD+H990SjAFWFjgF=xj7hTZuhnZ42bGkwuesaH6UaWM4UKb8Zg@mail.gmail.com>
2018-04-17 15:44 ` [dpdk-stable] [RFC 2/2] nfp: allow for non-root user Alejandro Lucero
2018-04-17 15:54 ` Alejandro Lucero
2018-04-17 19:19 ` Aaron Conole
2018-04-18 10:53 ` Alejandro Lucero
2018-04-18 12:32 ` Aaron Conole
2018-04-19 6:05 ` Alejandro Lucero
2018-04-20 14:12 ` Ferruh Yigit [this message]
2018-04-20 14:56 ` Aaron Conole
2018-04-17 15:54 ` Thomas Monjalon
2018-04-17 16:24 ` Alejandro Lucero
2018-04-17 19:06 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d0e69b9-3655-f3f6-9cbb-1090b9471813@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aconole@redhat.com \
--cc=adrien.mazarguil@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).