From: Ted Logan <tedlogan@fb.com>
To: David Matlack <dmatlack@google.com>
Cc: Alex Williamson <alex@shazbot.org>, Shuah Khan <shuah@kernel.org>,
<kvm@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Matt Evans <mattev@meta.com>
Subject: Re: [PATCH] vfio: selftests: Build tests on aarch64
Date: Thu, 19 Mar 2026 15:55:38 -0700 [thread overview]
Message-ID: <abx+6mcpGwt0MzrG@devvm6375.cco0.facebook.com> (raw)
In-Reply-To: <abw5ng4M14Je2OfU@google.com>
Hi David,
On Thu, Mar 19, 2026 at 05:59:58PM +0000, David Matlack wrote:
> On 2026-03-17 04:25 PM, Ted Logan wrote:
> > Also build vfio self-tests on aarch64 variants, in addition to arm64 and
>
> s/self-tests/selftests/
>
> > x86_64.
>
> This could be worded better to clarify that this is about fixing the
> VFIO selftests to allow native builds on arm64 host platforms.
>
> >
> > Reported-by: Matt Evans <mattev@meta.com>
> > Closes: https://lore.kernel.org/all/e51b4ff2-13c4-47d4-b781-3dcbd740d274@meta.com/
>
> Please also add a fixes tag, since it was not the intent of the original
> commit was to disallow native arm64 builds.
>
> Fixes: a55d4bbbe644 ("vfio: selftests: only build tests on arm64 and x86_64")
Thanks for the feedback, I'll add that to the next version.
> > ---
> > Signed-off-by: Ted Logan <tedlogan@fb.com>
> > ---
> > tools/testing/selftests/vfio/Makefile | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
> > index 8e90e409e91d..98bc8d6271a4 100644
> > --- a/tools/testing/selftests/vfio/Makefile
> > +++ b/tools/testing/selftests/vfio/Makefile
> > @@ -1,4 +1,4 @@
> > -ARCH ?= $(shell uname -m)
> > +ARCH ?= $(shell uname -m | sed -e 's/aarch64.*/arm64/')
>
> Perhaps we can just include tools/scripts/Makefile.arch to avoid having
> to maintain yet another "uname -m" translation?
I took a look at tools/scripts/Makefile.arch and it includes a
translation from x85_64 to x86, so it doesn't look like we can use it to
distinguish architectures here. It sounds like the simplest thing to do
is add aarch64 to the list of allowed architectures so I'll do that in
the next patch.
> This would make it harder to prevent aarch64_be though, which Alex
> indicated we might want to do.
>
> >
> > ifeq (,$(filter $(ARCH),arm64 x86_64))
> > # Do nothing on unsupported architectures
> >
> > ---
> > base-commit: 96ca4caf9066f5ebd35b561a521af588a8eb0215
> > change-id: 20260317-vfio-selftests-aarch64-636abf0f7674
> >
> > Best regards,
> > --
> > Ted Logan <tedlogan@fb.com>
> >
prev parent reply other threads:[~2026-03-19 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 23:25 [PATCH] vfio: selftests: Build tests on aarch64 Ted Logan
2026-03-18 22:55 ` Alex Williamson
2026-03-19 13:51 ` Matt Evans
2026-03-19 14:37 ` Alex Williamson
2026-03-19 15:01 ` Matt Evans
2026-03-19 17:59 ` David Matlack
2026-03-19 22:55 ` Ted Logan [this message]
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=abx+6mcpGwt0MzrG@devvm6375.cco0.facebook.com \
--to=tedlogan@fb.com \
--cc=alex@shazbot.org \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mattev@meta.com \
--cc=shuah@kernel.org \
/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