From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 71A56A052B; Thu, 30 Jul 2020 18:55:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BDA78E07; Thu, 30 Jul 2020 18:55:30 +0200 (CEST) Received: from mail-ot1-f67.google.com (mail-ot1-f67.google.com [209.85.210.67]) by dpdk.org (Postfix) with ESMTP id 0CB8F3B5 for ; Thu, 30 Jul 2020 18:55:29 +0200 (CEST) Received: by mail-ot1-f67.google.com with SMTP id t7so6785298otp.0 for ; Thu, 30 Jul 2020 09:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sn1Xn9sBz4zw5VIXSkV38d4nWNcFQ7n3dFLovEP9thg=; b=dmCImG9oXJ5xlLj8LirJ9HUBLbbQMlyvQ7IH59Ni3FADS8i3JTjsdHsrDCJVHcYfmY elzdoycAzV79aTKr0YDUP8u6AfVzO9GPPlCarZeZ6kojbFYlZgGa5CjKUDOBc75W0qOy jcfiy1uNG0d7r5etjN68dFF0gAvwWkVS0I/Z8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sn1Xn9sBz4zw5VIXSkV38d4nWNcFQ7n3dFLovEP9thg=; b=qFed/Oe411yO8/SSkMEyc5zppumwibuP4+r+AALdWrdWZnkvtOYzzNUfS0AODj/PTN e36r0T6LCszrPRmlMjgv99ywsUNNMep7jFZzg/BvA9fEQS5mwkEkFc7qALKq+KmmqlHW 5VZFmx0szcHmo90XFjZ7A79r5BKTablmThxl2piyNx3oz5tFUnr5nMgfoTkrW3YPd/be kLpZLaARC4HkbysB9MVcx6neiE1zN/8JaP9DKI8jbbW5yPJx6CtmhRrWifocIfwOgpzZ z4zd7qf8NyM4oSwqtZGxtH9yY15MfY7liyC6I+DqxTw25eTGEVdO1o8N9M0HXr8oKbFb bxbA== X-Gm-Message-State: AOAM533/qQ9uc3shKZN8ueakL1T7G2brAGXzZ5ffVnR78Cr7Z3jWNkf3 iFODCy7ZqDoJBy40mhT2Dxpauaq7G60tpwScqSFx8Q== X-Google-Smtp-Source: ABdhPJx08hi75SSy9VmBRgm0zFytO8jWvPtpl5YciD9secBAeqmxR5x6qJKFGIbfKJx+nIc++nVrNI/N88slC2EI0sg= X-Received: by 2002:a05:6830:1e67:: with SMTP id m7mr2798100otr.359.1596128128325; Thu, 30 Jul 2020 09:55:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Owen Hilyard Date: Thu, 30 Jul 2020 12:54:52 -0400 Message-ID: To: "Burakov, Anatoly" Cc: dts@dpdk.org, dev@dpdk.org, Lincoln Lavoie Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Userspace testing X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 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 >