From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 05FCFA0A05 for ; Tue, 19 Jan 2021 22:02:39 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 141FC140DD3; Tue, 19 Jan 2021 22:02:39 +0100 (CET) Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) by mails.dpdk.org (Postfix) with ESMTP id 0AF91140DD2 for ; Tue, 19 Jan 2021 22:02:38 +0100 (CET) Received: by mail-io1-f52.google.com with SMTP id q2so40920409iow.13 for ; Tue, 19 Jan 2021 13:02:37 -0800 (PST) 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:content-transfer-encoding; bh=niwpu4aeB1oZmCExoMS9M78/t0uFVxqcS2RswXzR6nc=; b=RW+eHZ1V6DmeE4K3zI6nTbaBqd5YUX0uavhCMHqgFOrKG9n8qITiKJ5VfdjmBX3/Lf AEgMrvxx2HBCKv7unuihpf7npW/uD7IXNeXyM6TmF8+hq82sqsl4ry4RQb2lYniUDwjz 2scZBRvO+SS4edBfP1pBxIEGuHF7MMQ+A6iQ4= 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:content-transfer-encoding; bh=niwpu4aeB1oZmCExoMS9M78/t0uFVxqcS2RswXzR6nc=; b=He49PGEBFJ8qw1IV8hVCT01QRBW0jiK0g3szvrgikab3pARrXDeuRy0tRtkmCyDOSF JGZ5M1gTXQKAl9HDVUtqiifaPRYOQeWox5nalQ2BRMUGm+o+g2h9yvjcLrlFGU3vpcdE 2XoNB+Dq5XSMqe5LfLnZgtJFg3l/eTmiclH6jHUSshIYS1ixVMLG7GqEBk9Gk8aWYXrD Z54PDfNZMDnGcaLQxB7o3BMJQTKcZZj+4Ro6x9x8RZDhNZTfyeFqah+GylRpiBNlpuch OuF+Rr3e4EuampNgSXrBTOaJt99bb/k1Am7MVOyUzAE69b+JwEe78oYZ9JWZ/WZrMQJN ZU0w== X-Gm-Message-State: AOAM5310zGnGBipojw8VfWQNeCiN7wswyneYaxSFOj0Lk6mUpk2kMYI7 C7uqDf9PJ6ehREkdn4D2UJncdMyFtrxBmEnSvrUKvQ== X-Google-Smtp-Source: ABdhPJwTE4eAU4wcr/C3im8ojutvxGXieqefiUPXDRisR6ohZlrcQOr1WhcpW+oX/SY97SaxsQfcI7I3n8JVjHUV4nA= X-Received: by 2002:a6b:dc17:: with SMTP id s23mr4350662ioc.170.1611090157238; Tue, 19 Jan 2021 13:02:37 -0800 (PST) MIME-Version: 1.0 References: <5fb3ef95ee654029a72600241a6843a3@pantheon.tech> <57460d91-a51f-f69a-eee5-9b84e36f67b9@iol.unh.edu> In-Reply-To: <57460d91-a51f-f69a-eee5-9b84e36f67b9@iol.unh.edu> From: Brandon Lo Date: Tue, 19 Jan 2021 16:02:01 -0500 Message-ID: To: Hemant Agrawal , Ruoshan Shi Cc: "X.f. Ren" , ci@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-ci] Upgraded DTS Version for NXP X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" Hi everyone, I am looking to set up the NXP switch in the UNH-IOL lab for performance and functional testing using DTS after it lost functionality due to the shift from make to meson. Is there anyone that is familiar with the way DTS is set up? It seems like the ports that are used for DTS are not exposed in the same way that machines are typically set up. Thanks, Brandon On Thu, Dec 3, 2020 at 11:53 AM Brandon Lo wrote: > > Hi everyone, > > > Has anybody got a chance to look at this issue? > > I'm not sure if the NXP system specifically needs the DTS version from > your local BitBucket repository. It seems that there are some obstacles > that the original DTS repository is not able to deal with. Could > somebody point me in the right direction to get this set up? > > > Thanks, > > Brandon > > On 10/22/2020 1:26 PM, Brandon Lo wrote: > > Hi everyone, > > > > It seems that the DTS instance on the community lab's NXP system uses > > a DTS that is internal to your bitbucket which makes it unable to be > > pulled for the new changes. > > I have gotten past the point of compiling DPDK manually, but DTS is > > still the outdated version that relies on make. > > > > I have attempted to use a new, clean version of DTS pulled directly > > from the repo, but I am having a bit of trouble with setting it up. > > Which interfaces are used for testing between the DUT and the tester? > > The ports I have found within the conf/ports.cfg file do not seem to > > match up. > > It also seems that mydut.py and project_mydut.py change the behavior > > of DTS itself. > > > > Could someone help look into this issue? > > > > Thanks, > > Brandon > > > > On Tue, Sep 22, 2020 at 10:06 AM Brandon Lo wrote: > >> Hi Juraj, > >> > >> Running a `file` command shows me that the fixdep is ARM aarch64. > >> fixdep: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), > >> dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for > >> GNU/Linux 3.7.0, > >> BuildID[sha1]=3D2024bac4b13890933f59d28a2aa1a82eef2e02f2, not stripped > >> > >> It seems right to me(?) since `uname -m` prints aarch64. > >> I will continue investigating this and see if I can get any further. > >> > >> Thanks, > >> Brandon > >> > >> On Tue, Sep 22, 2020 at 1:56 AM Juraj Linke=C5=A1 wrote: > >>> Hi Brandon, > >>> > >>> The Exec format error looks like an error which happens when you try = to run an arm binary on an x86 machine (or in general the binary format doe= sn't match the host architecture). What does "file scripts/basic/fixdep" sa= y and what's the host architecture? > >>> > >>> Juraj > >>> > >>>> -----Original Message----- > >>>> From: ci On Behalf Of Brandon Lo > >>>> Sent: Friday, September 18, 2020 6:56 PM > >>>> To: Hemant Agrawal > >>>> Cc: Ruoshan Shi ; X.f. Ren ; > >>>> ci@dpdk.org; Lincoln Lavoie > >>>> Subject: Re: [dpdk-ci] Upgraded DTS Version for NXP > >>>> > >>>> Hi Hemant, > >>>> > >>>> I have gotten more progress into building; now I am running into a d= ifferent > >>>> issue. > >>>> There is currently an issue building a kernel module: "FAILED: > >>>> kernel/linux/igb_uio/igb_uio.ko" > >>>> > >>>> I believe this issue is related to the following message: "/bin/sh: = 1: > >>>> scripts/basic/fixdep: Exec format error" > >>>> Any ideas of where this error comes from? > >>>> > >>>> Thanks, > >>>> Brandon > >>>> > >>>> On Fri, Sep 18, 2020 at 7:52 AM Hemant Agrawal > >>>> wrote: > >>>>> HI, > >>>>> What is the issue are you observing ? > >>>>> > >>>>> 1. install ARM cross tool chain > >>>>> > >>>>> sudo apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu su= do > >>>>> apt-get install build-essential autoconf libtool cmake pkg-config g= it > >>>>> python-dev swig3.0 libpcre3-dev nodejs-dev > >>>>> > >>>>> 2. If you want to build kernel mods > >>>>> Specify the kernel_dir > >>>>> meson arm64-build --cross-file config/arm/arm64_dpaa_linux_gcc > >>>>> -Dexamples=3Dall --werror -Denable_kmods=3DTrue -Dlibdir=3Dlib > >>>>> --default-library=3Dstatic ninja -C arm64-build > >>>>> > >>>>> 3. or build with kmods > >>>>> meson arm64-build --cross-file config/arm/arm64_dpaa_linux_gcc > >>>>> -Dexamples=3Dall --werror -Dlibdir=3Dlib --default-library=3Dstatic= ninja -C > >>>>> arm64-build > >>>>> > >>>>> > >>>>> Regards, > >>>>> Hemant > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: ci On Behalf Of Brandon Lo > >>>>>> Sent: Friday, September 18, 2020 2:30 AM > >>>>>> To: Ruoshan Shi > >>>>>> Cc: X.f. Ren ; ci@dpdk.org; Lincoln Lavoie > >>>>>> > >>>>>> Subject: [dpdk-ci] Upgraded DTS Version for NXP > >>>>>> > >>>>>> Hi Ruoshan, > >>>>>> > >>>>>> Since DPDK has discontinued make support for compiling, a DTS > >>>>>> upgrade is needed for performance testing to continue on all syste= ms. > >>>>>> > >>>>>> I am attempting to upgrade DTS on the NXP machine, but it seems th= at > >>>>>> it is a fork of DTS that is from NXP's bitbucket server. > >>>>>> Is it possible to pull from the upstream DPDK DTS repository and u= se > >>>>>> that instead? > >>>>>> > >>>>>> I also installed meson and ninja on the machine which is needed fo= r > >>>>>> the new version, but I am having trouble building. > >>>>>> It uses these commands to build (172.18.0.202 in /root/dpdk): > >>>>>> 1. CC=3Dgcc meson --werror -Denable_kmods=3DTrue -Dlibdir=3Dlib --= default- > >>>>>> library=3Dstatic arm64-dpaa-linuxapp-gcc 2. ninja -C > >>>>>> arm64-dpaa-linuxapp-gcc -j > >>>>>> 8 > >>>>>> > >>>>>> Could you help me look into this? > >>>>>> > >>>>>> Thanks, > >>>>>> Brandon > >>>>>> > >>>>>> -- > >>>>>> Brandon Lo > >>>>>> > >>>>>> UNH InterOperability Laboratory > >>>>>> > >>>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824 > >>>>>> > >>>>>> blo@iol.unh.edu > >>>>>> > >>>>>> https://eur01.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2= Fwww > >>>>>> .i > >>>>>> > >>>> ol.unh.edu%2F&data=3D02%7C01%7Chemant.agrawal%40nxp.com%7Ce3 > >>>> d40a1a7c8246676acf08d85b4cbe49%7C686ea1d3bc2b4c6fa92cd99c5c301635 > >>>> % > >>>> 7C0%7C0%7C637359732457337624&sdata=3DIrFBG%2BvSBQi8uodqX%2FX > >>>>>> QmIPnB7CVg6EbDK%2Fq3bOtdbQ%3D&reserved=3D0 > >>>> > >>>> > >>>> -- > >>>> > >>>> Brandon Lo > >>>> > >>>> UNH InterOperability Laboratory > >>>> > >>>> 21 Madbury Rd, Suite 100, Durham, NH 03824 > >>>> > >>>> blo@iol.unh.edu > >>>> > >>>> www.iol.unh.edu > >> > >> -- > >> > >> Brandon Lo > >> > >> UNH InterOperability Laboratory > >> > >> 21 Madbury Rd, Suite 100, Durham, NH 03824 > >> > >> blo@iol.unh.edu > >> > >> www.iol.unh.edu > > > > --=20 Brandon Lo UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 blo@iol.unh.edu www.iol.unh.edu