From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id A1B2A7E9D for ; Wed, 12 Nov 2014 15:39:57 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 12 Nov 2014 06:49:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,369,1413270000"; d="scan'208";a="606621932" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga001.jf.intel.com with ESMTP; 12 Nov 2014 06:49:50 -0800 Received: from irsmsx110.ger.corp.intel.com (163.33.3.25) by IRSMSX101.ger.corp.intel.com (163.33.3.153) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 12 Nov 2014 14:49:09 +0000 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.101]) by IRSMSX110.ger.corp.intel.com ([169.254.15.3]) with mapi id 14.03.0195.001; Wed, 12 Nov 2014 14:49:08 +0000 From: "Burakov, Anatoly" To: Morten Jagd Christensen , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Valgrind and DPDK - RDRAND + RTE_MACHINE obstacle Thread-Index: Ac/+XS3f0D4iVvefQQ6/MOHiF6J12QAKhBWw Date: Wed, 12 Nov 2014 14:49:08 +0000 Message-ID: References: <002001cffe5d$2ecf1290$8c6d37b0$@xenanetworks.com> In-Reply-To: <002001cffe5d$2ecf1290$8c6d37b0$@xenanetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Valgrind and DPDK - RDRAND + RTE_MACHINE obstacle X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2014 14:39:58 -0000 Hi Morten I'm not that familiar with valgrind, but as far as I know it's using some k= ind of CPU emulation. Most likely the processor being emulated by valgrind = doesn't have the capabilities your actual CPU has (sort of like trying to r= un a AVX2-compiled code on a QEMU machine emulating Westmere). You may try = to edit the config file to change the RTE_MACHINE to compile DPDK for anoth= er platform. Thanks, Anatoly -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Morten Jagd Christense= n Sent: Wednesday, November 12, 2014 9:44 AM To: dev@dpdk.org Subject: Re: [dpdk-dev] Valgrind and DPDK - RDRAND + RTE_MACHINE obstacle Hi all, Thanks to Marc for sharinghis experiment and great to hear that others migh= t benefit form the latest developments. I can add the following experience: Last night I downloaded Valgrind 3.10.0, applied the patch and built Valgri= nd with success. Unfortunately on my hardware (Xeon E5 processors) and dpdk-1.7.1 I now get = the following error: $ sudo /usr/local/valgrind/bin/valgrind ./build/myprogram -c 0xffff -n 4 = =3D=3D24093=3D=3D Memcheck, a memory error detector =3D=3D24093=3D=3D Copyr= ight (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. =3D=3D24093=3D=3D Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyr= ight info =3D=3D24093=3D=3D Command: ./build/myprogram -c 0xffff -n 4 =3D= =3D24093=3D=3D ERROR: This system does not support "RDRAND". Please check that RTE_MACHINE is set correctly. Has anyone experienced the same? Cheers Morten -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc Sune Sent: 7. november 2014 04:36 To: Matthew Hall Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Valgrind and DPDK - does it work ? On 07/11/14 02:04, Matthew Hall wrote: > On Fri, Nov 07, 2014 at 01:22:49AM +0100, Marc Sune wrote: >> Found some time to have a close look. I also wanted to check a DPDK=20 >> app against valgrind. It works! >> >> I downloaded and compiled valgrind from sources (3.10.0) and applied >> (manually) this patch: >> >> https://bugs.kde.org/attachment.cgi?id=3D85950&action=3Dedit >> >> (Applied around line 2216) >> >> From this post: >> >> http://valgrind.10908.n7.nabble.com/mpich-unable-to-munmap-hugepages- >> td49150.html >> >> Happy debugging >> Marc > Marc, > > This is just AMAZING!!! I have wished for it for many years for DPDK,=20 > ever since I used it in beta before it went GA. Thanks Most kudos though (if not all), should go to T. Janjusic. I just found it a= nd backported to the latest stable: https://bugs.kde.org/show_bug.cgi?id=3D333051 > > Would it be possible to post your modification of Valgrind in Github,=20 > Bitbucket, or some other repo? I'd like to try this out on my app, too. Sure, it is a good idea. I just did a quick&dirty import of the latest stable release 3.10.0. No git= -svn , or anything fancy (github import failed, silently ignoring files...) no gitignore too. And then I applied the patch: https://github.com/bisdn/valgrind-hugepages Please note the comment in README.md, I cannot provide any support or take = any responsibility. We will also delete this repo once there is a stable re= lease. But you can at least try it, should work ;) > > Also, not sure if anybody sent this upstream to Valgrind, but if not,=20 > we really should, so it just works by default from now on. It already is, there is simply no stable release yet (see Phillipe comment)= : https://bugs.kde.org/show_bug.cgi?id=3D333051#c8 Cheers Marc > > Thanks, > Matthew.