DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: "Stanisław Kardach" <kda@semihalf.com>
Cc: dev <dev@dpdk.org>,  Frank Zhao <Frank.Zhao@starfivetech.com>,
	 Sam Grove <sam.grove@sifive.com>,
	 Marcin Wojtas <mw@semihalf.com>,
	upstream@semihalf.com,
	 David Marchand <david.marchand@redhat.com>,
	Michael Santana <msantana@redhat.com>
Subject: Re: [PATCH v3 8/8] ci: add RISCV64 cross compilation job
Date: Fri, 13 May 2022 10:33:56 -0400	[thread overview]
Message-ID: <f7t4k1tmrhn.fsf@redhat.com> (raw)
In-Reply-To: <CALVGJWKCsOOv1C-Yb3nE1GEnedZCaRXtFXaYFqmd9pViskK8HA@mail.gmail.com> (=?utf-8?Q?=22Stanis=C5=82aw?= Kardach"'s message of "Thu, 12 May 2022 18:07:24 +0200")

Stanisław Kardach <kda@semihalf.com> writes:

> On Thu, 12 May 2022, 17:47 Aaron Conole, <aconole@redhat.com> wrote:
>
>  Stanislaw Kardach <kda@semihalf.com> writes:
>
>  > Checks cross-compilation using Ubuntu 20.04 x86.
>  >
>  > Signed-off-by: David Marchand <david.marchand@redhat.com>
>  > Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
>  > ---
>  >  .ci/linux-build.sh          |  4 ++++
>  >  .github/workflows/build.yml | 11 ++++++++++-
>  >  2 files changed, 14 insertions(+), 1 deletion(-)
>
>  Seems there is still a failure in this series - once that is resolved I
>  think this can go in.
>
> I suspect the failure is due to this series depending on 3 other patches which I've marked with Depends-on in the
> offending patch. Is CI utilizing those tags? If not, is there a way to relaunch it once dependencies are integrated?

Ahh okay - yes 0day bot doesn't currently use that.  It's planned for
after the system upgrade (date on that is pending).

>  > diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
>  > index 877243c9c8..aa5e9ec114 100755
>  > --- a/.ci/linux-build.sh
>  > +++ b/.ci/linux-build.sh
>  > @@ -74,6 +74,10 @@ if [ "$PPC64LE" = "true" ]; then
>  >      cross_file=config/ppc/ppc64le-power8-linux-gcc-ubuntu
>  >  fi
>  >  
>  > +if [ "$RISCV64" = "true" ]; then
>  > +    cross_file=config/riscv/riscv64_linux_gcc
>  > +fi
>  > +
>  >  if [ -n "$cross_file" ]; then
>  >      OPTS="$OPTS --cross-file $cross_file"
>  >  fi
>  > diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
>  > index e2f94d786b..ca468da8fa 100644
>  > --- a/.github/workflows/build.yml
>  > +++ b/.github/workflows/build.yml
>  > @@ -25,6 +25,7 @@ jobs:
>  >        MINI: ${{ matrix.config.mini != '' }}
>  >        PPC64LE: ${{ matrix.config.cross == 'ppc64le' }}
>  >        REF_GIT_TAG: v22.03
>  > +      RISCV64: ${{ matrix.config.cross == 'riscv64' }}
>  >        RUN_TESTS: ${{ contains(matrix.config.checks, 'tests') }}
>  >  
>  >      strategy:
>  > @@ -73,6 +74,10 @@ jobs:
>  >              compiler: gcc
>  >              library: shared
>  >              cross: ppc64le
>  > +          - os: ubuntu-20.04
>  > +            compiler: gcc
>  > +            library: shared
>  > +            cross: riscv64
>  >  
>  >      steps:
>  >      - name: Checkout sources
>  > @@ -131,8 +136,12 @@ jobs:
>  >        if: env.PPC64LE == 'true'
>  >        run: sudo apt install -y gcc-powerpc64le-linux-gnu libc6-dev-ppc64el-cross
>  >          pkg-config-powerpc-linux-gnu
>  > +    - name: Install riscv64 cross compiling packages
>  > +      if: env.RISCV64 == 'true'
>  > +      run: sudo apt install -y gcc-riscv64-linux-gnu libc6-dev-riscv64-cross
>  > +        pkg-config-riscv64-linux-gnu
>  >      - name: Install test tools packages
>  > -      if: env.AARCH64 != 'true' || env.PPC64LE != 'true' || env.RUN_TESTS == 'true'
>  > +      if: env.AARCH64 != 'true' || env.PPC64LE != 'true' || env.RISCV64 != 'true' || env.RUN_TESTS == 'true'
>  >        run: sudo apt install -y gdb
>  >      - name: Install doc generation packages
>  >        if: env.BUILD_DOCS == 'true'


  reply	other threads:[~2022-05-13 14:34 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 17:29 [PATCH 00/11] Introduce support for RISC-V architecture Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 01/11] lpm: add a scalar version of lookupx4 function Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 02/11] examples/l3fwd: fix scalar LPM compilation Stanislaw Kardach
2022-05-05 17:39   ` Stephen Hemminger
2022-05-05 17:49     ` Stanisław Kardach
2022-05-05 18:09       ` Stephen Hemminger
2022-05-05 17:29 ` [PATCH 03/11] eal: add initial support for RISC-V architecture Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 04/11] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 05/11] net/memif: set memfd syscall ID on RISC-V Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 06/11] net/tap: set BPF syscall ID for RISC-V Stanislaw Kardach
2022-05-05 17:29 ` [PATCH 07/11] examples/l3fwd: enable RISC-V operation Stanislaw Kardach
2022-05-05 17:30 ` [PATCH 08/11] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-05-05 17:30 ` [PATCH 09/11] test/ring: disable problematic tests for RISC-V Stanislaw Kardach
2022-05-05 17:35   ` Stephen Hemminger
2022-05-05 17:43     ` Stanisław Kardach
2022-05-05 18:06       ` Stephen Hemminger
2022-05-10 23:28   ` Honnappa Nagarahalli
2022-05-11 10:07     ` Stanisław Kardach
2022-05-05 17:30 ` [PATCH 10/11] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-05-05 17:30 ` [PATCH 11/11] test/hash: report non HTM numbers for single r/w Stanislaw Kardach
2022-05-06  9:13 ` [PATCH 00/11] Introduce support for RISC-V architecture David Marchand
2022-05-09 12:24   ` Stanisław Kardach
2022-05-09 12:30     ` Thomas Monjalon
2022-05-11  8:09       ` Morten Brørup
2022-05-11 10:28         ` Stanisław Kardach
2022-05-11 11:06           ` Thomas Monjalon
2022-05-09 14:30     ` David Marchand
2022-05-10 11:21       ` Stanisław Kardach
2022-05-10 12:31         ` Thomas Monjalon
2022-05-10 14:00           ` Stanisław Kardach
2022-05-10 14:23             ` Thomas Monjalon
2022-05-10 15:07 ` [PATCH v2 0/8] " Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 1/8] eal: add initial " Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 2/8] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 3/8] net/memif: set memfd syscall ID on RISC-V Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 4/8] net/tap: set BPF syscall ID for RISC-V Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 5/8] examples/l3fwd: enable RISC-V operation Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 6/8] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-05-10 15:07   ` [PATCH v2 7/8] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-05-10 15:35     ` Stanisław Kardach
2022-05-10 15:07   ` [PATCH v2 8/8] ci: add RISCV64 cross compilation job Stanislaw Kardach
2022-05-10 15:48   ` [PATCH v3 0/8] Introduce support for RISC-V architecture Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 1/8] eal: add initial " Stanislaw Kardach
2022-05-13  6:50       ` Heinrich Schuchardt
2022-05-13  8:42         ` Stanisław Kardach
2022-05-13 10:51           ` Heinrich Schuchardt
2022-05-13 11:47             ` Stanisław Kardach
2022-05-13 15:37         ` Stephen Hemminger
2022-05-16  8:00           ` Stanisław Kardach
2022-05-10 15:48     ` [PATCH v3 2/8] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 3/8] net/memif: set memfd syscall ID on RISC-V Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 4/8] net/tap: set BPF syscall ID for RISC-V Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 5/8] examples/l3fwd: enable RISC-V operation Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 6/8] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 7/8] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-05-10 15:48     ` [PATCH v3 8/8] ci: add RISCV64 cross compilation job Stanislaw Kardach
2022-05-12 15:47       ` Aaron Conole
2022-05-12 16:07         ` Stanisław Kardach
2022-05-13 14:33           ` Aaron Conole [this message]
2022-05-12  8:04 ` [PATCH 00/11] Introduce support for RISC-V architecture Heinrich Schuchardt
2022-05-12  8:35   ` Stanisław Kardach
2022-05-12  9:46     ` Heinrich Schuchardt
2022-05-12 13:56       ` Stanisław Kardach
2022-05-12 21:06         ` Heinrich Schuchardt

Reply instructions:

You may reply publicly 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=f7t4k1tmrhn.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=Frank.Zhao@starfivetech.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kda@semihalf.com \
    --cc=msantana@redhat.com \
    --cc=mw@semihalf.com \
    --cc=sam.grove@sifive.com \
    --cc=upstream@semihalf.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).