From: Eduard Zingerman <eddyz87@gmail.com>
To: Pu Lehui <pulehui@huaweicloud.com>,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org
Cc: "Björn Töpel" <bjorn@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>, "Yonghong Song" <yhs@fb.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@kernel.org>,
"Stanislav Fomichev" <sdf@google.com>,
"Hao Luo" <haoluo@google.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Mykola Lysenko" <mykolal@fb.com>,
"Manu Bretelle" <chantr4@gmail.com>,
"Pu Lehui" <pulehui@huawei.com>
Subject: Re: [PATCH bpf-next 0/5] Support local vmtest for riscv64
Date: Fri, 29 Mar 2024 11:08:27 +0200 [thread overview]
Message-ID: <32b3358903bf8ba408812a2636f39a275493eb91.camel@gmail.com> (raw)
In-Reply-To: <20240328124916.293173-1-pulehui@huaweicloud.com>
On Thu, 2024-03-28 at 12:49 +0000, Pu Lehui wrote:
> Patch 1 is to enable cross platform testing for local vmtest. The
> remaining patch adds local vmtest support for riscv64. It relies on
> commit [0] [1] for better regression.
>
> We can now perform cross platform testing for riscv64 bpf using the
> following command:
>
> PLATFORM=riscv64 CROSS_COMPILE=riscv64-linux-gnu- \
> tools/testing/selftests/bpf/vmtest.sh -- \
> ./test_progs -d \
> \"$(cat tools/testing/selftests/bpf/DENYLIST.riscv64 \
> | cut -d'#' -f1 \
> | sed -e 's/^[[:space:]]*//' \
> -e 's/[[:space:]]*$//' \
> | tr -s '\n' ','\
> )\"
>
> The test platform is x86_64 architecture, and the versions of relevant
> components are as follows:
> QEMU: 8.2.0
> CLANG: 17.0.6 (align to BPF CI)
> OpenSBI: 1.3.1 (default by QEMU)
> ROOTFS: ubuntu jammy (generated by [2])
>
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?id=ea6873118493 [0]
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=443574b033876c85 [1]
> Link: https://github.com/libbpf/ci/blob/main/rootfs/mkrootfs_debian.sh [2]
Hello,
I wanted to do a test run for this patch-set but did not figure out
how to build rootfs for riscv64 system.
I modified mkrootfs_debian.sh as below, but build command fails:
$ ./rootfs/mkrootfs_debian.sh -d jammy -a riscv64 -m http://de.archive.ubuntu.com/ubuntu
...
E: Couldn't download http://de.archive.ubuntu.com/ubuntu/dists/jammy/main/binary-riscv64/Packages
Apparently jammy does not have binaries built for riscv64, or I'm failing to find correct mirror.
Could you please provide some instructions on how to prepare rootfs?
Thanks,
Eduard
--
diff --git a/rootfs/mkrootfs_debian.sh b/rootfs/mkrootfs_debian.sh
index dfe957e..1d5b769 100755
--- a/rootfs/mkrootfs_debian.sh
+++ b/rootfs/mkrootfs_debian.sh
@@ -16,6 +16,7 @@ CPUTABLE="${CPUTABLE:-/usr/share/dpkg/cputable}"
deb_arch=$(dpkg --print-architecture)
distro="bullseye"
+mirror=""
function usage() {
echo "Usage: $0 [-a | --arch architecture] [-h | --help]
@@ -25,6 +26,7 @@ By default build an image for the architecture of the host running the script.
-a | --arch: architecture to build the image for. Default (${deb_arch})
-d | --distro: distribution to build. Default (${distro})
+ -m | --mirror: mirror for distribution to build. Default (${mirror})
"
}
@@ -44,7 +46,7 @@ function qemu_static() {
# Given a Debian architecture find the location of the matching
# qemu-${gnu_arch}-static binary.
gnu_arch=$(debian_to_gnu "${1}")
- echo "qemu-${gnu_arch}-static"
+ echo "qemu-${gnu_arch}"
}
function check_requirements() {
@@ -95,7 +97,7 @@ function check_requirements() {
fi
}
-TEMP=$(getopt -l "arch:,distro:,help" -o "a:d:h" -- "$@")
+TEMP=$(getopt -l "arch:,distro:,mirror:,help" -o "a:d:m:h" -- "$@")
if [ $? -ne 0 ]; then
usage
fi
@@ -113,6 +115,10 @@ while true; do
distro="$2"
shift 2
;;
+ --mirror | -m)
+ mirror="$2"
+ shift 2
+ ;;
--help | -h)
usage
exit
@@ -162,7 +168,8 @@ debootstrap --include="$packages" \
--arch="${deb_arch}" \
"$@" \
"${distro}" \
- "$root"
+ "$root" \
+ "${mirror}"
qemu=$(which $(qemu_static ${deb_arch}))
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-03-29 9:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 12:49 [PATCH bpf-next 0/5] Support local vmtest for riscv64 Pu Lehui
2024-03-28 12:49 ` [PATCH bpf-next 1/5] selftests/bpf: Enable cross platform testing for local vmtest Pu Lehui
2024-03-28 12:49 ` [PATCH bpf-next 2/5] riscv, bpf: Relax restrictions on Zbb instructions Pu Lehui
2024-03-28 19:34 ` Stefan O'Rear
2024-03-28 22:07 ` Conor Dooley
2024-03-29 10:05 ` Pu Lehui
2024-04-02 14:25 ` Björn Töpel
2024-04-02 17:38 ` Conor Dooley
2024-04-02 19:00 ` Björn Töpel
2024-04-03 1:20 ` Conor Dooley
2024-04-03 10:05 ` Pu Lehui
2024-04-03 12:29 ` Conor Dooley
2024-03-29 11:23 ` Conor Dooley
2024-03-30 10:19 ` Pu Lehui
2024-03-30 10:19 ` Pu Lehui
2024-03-31 17:49 ` Samuel Holland
2024-04-02 14:18 ` Björn Töpel
2024-04-02 14:27 ` Björn Töpel
2024-04-02 16:03 ` Daniel Borkmann
2024-04-03 10:19 ` Pu Lehui
2024-03-28 12:49 ` [PATCH bpf-next 3/5] selftests/bpf: Add config.riscv64 Pu Lehui
2024-03-28 12:49 ` [PATCH bpf-next 4/5] selftests/bpf: Add DENYLIST.riscv64 Pu Lehui
2024-03-28 12:49 ` [PATCH bpf-next 5/5] selftests/bpf: Add riscv64 configurations to local vmtest Pu Lehui
2024-03-29 9:08 ` Eduard Zingerman [this message]
2024-03-29 10:10 ` [PATCH bpf-next 0/5] Support local vmtest for riscv64 Pu Lehui
2024-03-29 19:46 ` Eduard Zingerman
2024-03-30 10:12 ` Pu Lehui
2024-03-30 10:12 ` Pu Lehui
2024-04-02 23:40 ` Eduard Zingerman
2024-04-03 10:31 ` Pu Lehui
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=32b3358903bf8ba408812a2636f39a275493eb91.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantr4@gmail.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.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