test suite reviews and discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dts@dpdk.org, dev@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: Re: [dts] [dpdk-dev] Userspace testing
Date: Mon, 3 Aug 2020 10:31:16 -0400	[thread overview]
Message-ID: <CAHx6DYBNEwNrTcbEXOv6ifOTbTu0cGrE8jW9-G5QCfdHSotJ_g@mail.gmail.com> (raw)
In-Reply-To: <bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@intel.com>

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

On Fri, Jul 31, 2020 at 5:12 AM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:

> On 30-Jul-20 5:54 PM, Owen Hilyard wrote:
> > Thanks for the advice.
> >
> > I was wondering about the state of the "Setup VFIO permissions" option
> > in the setup script. It seems to just modify the character device's
> > permissions and then check their memory limit. Should this option also
> > handle the hugepages setup?
>
> I was under the (mis?)impression that the hugepage setup part of the
> script did that?
>
>
It doesn't appear to set them up so that non-root users can use them. From
what I can tell it only creates the pages, but doesn't change permissions
on them in any way.

[-- Attachment #2: Type: text/html, Size: 1090 bytes --]

  parent reply	other threads:[~2020-08-03 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 14:34 [dts] " Owen Hilyard
     [not found] ` <c70020a2-8948-dda4-bf1f-f5c29ec151b1@intel.com>
2020-07-30 16:54   ` [dts] [dpdk-dev] " Owen Hilyard
     [not found]     ` <bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@intel.com>
2020-08-03 14:31       ` Owen Hilyard [this message]
2020-07-31  7:43 ` David Marchand

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=CAHx6DYBNEwNrTcbEXOv6ifOTbTu0cGrE8jW9-G5QCfdHSotJ_g@mail.gmail.com \
    --to=ohilyard@iol.unh.edu \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    /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).