test suite reviews and discussions
 help / color / 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: Thu, 30 Jul 2020 12:54:52 -0400
Message-ID: <CAHx6DYDJGareBnmajrR6wZE=w0QhyQTn1XQ1boq=No0fnGdWUQ@mail.gmail.com> (raw)
In-Reply-To: <c70020a2-8948-dda4-bf1f-f5c29ec151b1@intel.com>

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

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?

Thanks

On Wed, Jul 29, 2020 at 11:35 AM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:

> On 29-Jul-20 3:34 PM, Owen Hilyard wrote:
> > Hello all,
> >
> > I was wondering what everyone's thoughts on doing both userspace testing
> > and unprivileged testing of dpdk applications is. DTS currently runs all
> > commands on the tester and the dut as the root user. Please correct me if
> > I'm wrong, but I was under the assumption that most applications written
> > with dpdk would not run as root. This could present a problem since it is
> > possible that permissions errors could arise and we wouldn't notice it
> due
> > to the way we currently test. Given that, I was wondering what should and
> > should not be possible as a normal (non-root) user, and what would be the
> > best way to go about verifying this.
> >
> > Thanks
> >
>
> This is useful, but not everything is supposed to work with limited
> privileges. Things that definitely *won't* work are KNI and anything
> igb_uio-related. Everything VFIO should work fine, and setting up
> correct permissions for hugepages and VFIO is one of the trickier things
> that even I don't know how to do correctly off the top of my head :D
>
> An easy stopgap way of running almost everything as an unprivileged user
> is to use in-memory mode (--in-memory EAL switch); this will cause EAL
> to reserve hugepages etc. without touching the filesystem, sacrificing
> secondary process support in the process (so e.g. EAL autotest won't
> work in --in-memory mode as it relies on secondary process support).
>
> So, i would say that it would be a valuable thing to test for, but be
> aware that not everything is expected to work.
>
> --
> Thanks,
> Anatoly
>

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

<div dir="ltr"><div dir="ltr">Thanks for the advice.<br><br>I was wondering about the state of the &quot;Setup VFIO permissions&quot; option in the setup script. It seems to just modify the character device&#39;s permissions and then check their memory limit. Should this option also handle the hugepages setup?<div><br></div><div>Thanks</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 29, 2020 at 11:35 AM Burakov, Anatoly &lt;<a href="mailto:anatoly.burakov@intel.com">anatoly.burakov@intel.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 29-Jul-20 3:34 PM, Owen Hilyard wrote:<br>
&gt; Hello all,<br>
&gt; <br>
&gt; I was wondering what everyone&#39;s thoughts on doing both userspace testing<br>
&gt; and unprivileged testing of dpdk applications is. DTS currently runs all<br>
&gt; commands on the tester and the dut as the root user. Please correct me if<br>
&gt; I&#39;m wrong, but I was under the assumption that most applications written<br>
&gt; with dpdk would not run as root. This could present a problem since it is<br>
&gt; possible that permissions errors could arise and we wouldn&#39;t notice it due<br>
&gt; to the way we currently test. Given that, I was wondering what should and<br>
&gt; should not be possible as a normal (non-root) user, and what would be the<br>
&gt; best way to go about verifying this.<br>
&gt; <br>
&gt; Thanks<br>
&gt; <br>
<br>
This is useful, but not everything is supposed to work with limited <br>
privileges. Things that definitely *won&#39;t* work are KNI and anything <br>
igb_uio-related. Everything VFIO should work fine, and setting up <br>
correct permissions for hugepages and VFIO is one of the trickier things <br>
that even I don&#39;t know how to do correctly off the top of my head :D<br>
<br>
An easy stopgap way of running almost everything as an unprivileged user <br>
is to use in-memory mode (--in-memory EAL switch); this will cause EAL <br>
to reserve hugepages etc. without touching the filesystem, sacrificing <br>
secondary process support in the process (so e.g. EAL autotest won&#39;t <br>
work in --in-memory mode as it relies on secondary process support).<br>
<br>
So, i would say that it would be a valuable thing to test for, but be <br>
aware that not everything is expected to work.<br>
<br>
-- <br>
Thanks,<br>
Anatoly<br>
</blockquote></div></div>

  parent reply index

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   ` Owen Hilyard [this message]
     [not found]     ` <bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@intel.com>
2020-08-03 14:31       ` [dts] [dpdk-dev] " Owen Hilyard
2020-07-31  7:43 ` David Marchand

Reply instructions:

You may reply publically 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='CAHx6DYDJGareBnmajrR6wZE=w0QhyQTn1XQ1boq=No0fnGdWUQ@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

test suite reviews and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dts/0 dts/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dts dts/ http://inbox.dpdk.org/dts \
		dts@dpdk.org
	public-inbox-index dts


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dts


AGPL code for this site: git clone https://public-inbox.org/ public-inbox