From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f68.google.com (mail-pg0-f68.google.com [74.125.83.68]) by dpdk.org (Postfix) with ESMTP id 464A01BA42 for ; Thu, 21 Jun 2018 17:15:07 +0200 (CEST) Received: by mail-pg0-f68.google.com with SMTP id i7-v6so1578642pgp.2 for ; Thu, 21 Jun 2018 08:15:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=EDzWPsKPS+fdquvOdfeaX6bzwPusyhOkIFVqkMvcdb8=; b=FXtx/izD9iLfx0/hXJKi9/2oDp+2T2kmLCS1xjterdFoGdstug8jFfX/Nh6ocpqOHE 5xveG1etAXOCYfC7/SFGCspZkPBHfX6AN7noHgFp6LNfA+6qwRZKM8VgJpHX6N1Czv0G /gkUKHynGoD+z6kLcEbCFIznND9fT881lacxHqc546nZWu1wpcWfOaf8ow+1NaxfDQ/V csTDYnpnaiMRdOLxfGvbtxjh28PuAbHimIKTWblqw+xkTiO359k/Hm8n6yfpt2fqY2qP Pz7kzdfA0QdaBJri6GiXGOCFVSBNrFsd/ls8ean1scNxoMvDdN+GoZPm+p/ez2cBDqoq FZ7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=EDzWPsKPS+fdquvOdfeaX6bzwPusyhOkIFVqkMvcdb8=; b=RI1VGlm/Sie/LoZrvhEUPHirZZ5YFpAKxRuCGLCTTjouOa2Y6jYw8yWlXUPtcry+06 k9/C8lR4VX7Keo2MaJViD0+cy1rIQeqsfdPCKq73KGIrZ48AROh6YV86HyFrT63piu7Y S6JLxfp6Z1ZhlXfNNenIg/JpOW4iUVUSxek76QpaMhLLpO9D7RZzKO36Rp47s3v0Yjfi OV96kod3P6IN45YSX7jPJwliU+1Qm9felxtt6M1DIIlnzVx3N+Ttv3WxDbBqhyTQXJTp LJAQiquYXW+1YeL9ZNIAPiNQODW4BPMPGKrl8PNAIY0FYglpYAX64I1LJbNqyn3ajeDM QirA== X-Gm-Message-State: APt69E10AN6eay/83pToPwCUcZJNvlLoFXq2bSv0RPSr6D6KovTQ/A7t 7iChvAdgd2itMhitaDqCEze+mg== X-Google-Smtp-Source: ADUXVKJaV4Ni6X/UEpj4ZXIGRBOWGivkt+F09/Ky7UCDFFpHQgWq0whpUV1lWar1kQpwPIBIKO2n9Q== X-Received: by 2002:aa7:82d9:: with SMTP id f25-v6mr27603977pfn.218.1529593636038; Thu, 21 Jun 2018 08:07:16 -0700 (PDT) Received: from xeon-e3 (204-195-35-107.wavecable.com. [204.195.35.107]) by smtp.gmail.com with ESMTPSA id r7-v6sm8091520pfh.52.2018.06.21.08.07.15 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Jun 2018 08:07:15 -0700 (PDT) Date: Thu, 21 Jun 2018 08:07:13 -0700 From: Stephen Hemminger To: Martin =?UTF-8?B?RHJhxaFhcg==?= Cc: "Avi Cohen (A)" , "Rosen, Rami" , "users@dpdk.org" Message-ID: <20180621080713.44313c33@xeon-e3> In-Reply-To: References: <34c3f20b-dcbb-5a47-d8c0-6af6635bc41a@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672C6986@HASMSX110.ger.corp.intel.com> <5dde9d52-3662-72ae-04a6-b5ad3e122562@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672C7B30@HASMSX110.ger.corp.intel.com> <9B0331B6EBBD0E4684FBFAEDA55776F9672C7B86@HASMSX110.ger.corp.intel.com> <586d777c-063a-1e0e-a6a8-bdcae3360ed6@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672CBC5E@HASMSX110.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 15:15:08 -0000 On Thu, 21 Jun 2018 13:02:34 +0200 Martin Dra=C5=A1ar wrote: > Dne 21.6.2018 v 7:58 Avi Cohen (A) napsal(a): > > Look at this=20 > > https://stackoverflow.com/questions/8213671/mmap-operation-not-permitte= d =20 >=20 > Hello Avi, >=20 > thank you for chiming in. Neither iomem runtime parameter or allowing > mmap on 0 page helped me. As for the latter, DPDK correctly maps to PCI > region, so that is not the problem. >=20 > Looking at the mmap source, there are basically only two points that > result in EPERM error. First one is related to incorrect flag > combination (not a DPDK case) the second is related to the file > descriptor of the resource being locked (should not be, but it is the > only possibility). >=20 > That lock may have to do something with Secure boot being on, as almost > the same system without secure boot is working ok. I built a custom > kernel with CONFIG_STRICT_DEVMEM turned off, but it's going to take me > some time to hammer it into the system, mainly because I am leaving for > a vacation today. >=20 > But it would be great if anyone, who has experience running DPDK on > secure booted systems, could share their experience. Secure boot disables direct access to memory which is required for DPDK via uio. This is by design since UIO would allow userspace (as root) to read or write any location in memory. Secure boot should work with VFIO. As long as you have an IOMMU, VFIO is a much better solution.