From: Manu Bretelle <chantr4@gmail.com>
To: chantr4@gmail.com, bpf@vger.kernel.org, andrii@kernel.org,
mykolal@fb.com, daniel@iogearbox.net, martin.lau@linux.dev,
yhs@fb.com
Subject: [PATCH bpf-next 3/4] selftests/bpf: Update vmtests.sh to support aarch64
Date: Fri, 21 Oct 2022 14:07:00 -0700 [thread overview]
Message-ID: <20221021210701.728135-4-chantr4@gmail.com> (raw)
In-Reply-To: <20221021210701.728135-1-chantr4@gmail.com>
Add handling of aarch64 when setting QEMU options and provide the right
path to aarch64 kernel image.
Signed-off-by: Manu Bretelle <chantr4@gmail.com>
---
tools/testing/selftests/bpf/vmtest.sh | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tools/testing/selftests/bpf/vmtest.sh b/tools/testing/selftests/bpf/vmtest.sh
index a29aa05ebb3e..316a56d680f2 100755
--- a/tools/testing/selftests/bpf/vmtest.sh
+++ b/tools/testing/selftests/bpf/vmtest.sh
@@ -21,6 +21,12 @@ x86_64)
QEMU_FLAGS=(-cpu host -smp 8)
BZIMAGE="arch/x86/boot/bzImage"
;;
+aarch64)
+ QEMU_BINARY=qemu-system-aarch64
+ QEMU_CONSOLE="ttyAMA0,115200"
+ QEMU_FLAGS=(-M virt,gic-version=3 -cpu host -smp 8)
+ BZIMAGE="arch/arm64/boot/Image"
+ ;;
*)
echo "Unsupported architecture"
exit 1
--
2.30.2
next prev parent reply other threads:[~2022-10-21 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:06 [PATCH bpf-next 0/4] Add support for aarch64 to selftests/bpf/vmtest.sh Manu Bretelle
2022-10-21 21:06 ` [PATCH bpf-next 1/4] selftests/bpf: Remove entries from config.s390x already present in config Manu Bretelle
2022-10-21 21:06 ` [PATCH bpf-next 2/4] selftests/bpf: Add config.aarch64 Manu Bretelle
2022-10-21 21:07 ` Manu Bretelle [this message]
2022-10-21 21:07 ` [PATCH bpf-next 4/4] selftests/bpf: Initial DENYLIST for aarch64 Manu Bretelle
2022-10-21 23:27 ` Andrii Nakryiko
2022-10-21 23:30 ` [PATCH bpf-next 0/4] Add support for aarch64 to selftests/bpf/vmtest.sh patchwork-bot+netdevbpf
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=20221021210701.728135-4-chantr4@gmail.com \
--to=chantr4@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--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