From: David Matlack <dmatlack@google.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Sean Christopherson <seanjc@google.com>,
Matt Evans <mattev@meta.com>, Ted Logan <tedlogan@fb.com>,
Alex Williamson <alex@shazbot.org>, Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] vfio: selftests: only build tests on arm64 and x86_64
Date: Tue, 28 Apr 2026 23:02:29 +0000 [thread overview]
Message-ID: <afE8hX3s-O-8yROu@google.com> (raw)
In-Reply-To: <20260428225528.GA3225388@nvidia.com>
On 2026-04-28 07:55 PM, Jason Gunthorpe wrote:
> On Tue, Apr 28, 2026 at 03:53:01PM -0700, David Matlack wrote:
> > > > If it is then we don't even need the __LP64__ stuff I posted.
> > > >
> > > > But when I look at the top-level Makefile and imagine running make
> > > > without setting ARCH on the command line on a 32-bit x86 host, ARCH
> > > > will be set to SUBARCH, which will be x86.
> > >
> > > Yep. So the big question is, why doesn't anyone complain about KVM selftests not
> > > building on 32-bit? Because they most definitely don't build.
> >
> > I guess no one's building on 32-bit hosts anymore? :)
>
> Well, if that's the case and kvm is broken too, then just ignore it
> and turn on vfio for x86 like kvm does?
>
> No sense in just fixing it for VFIO..
That's fair... So something like this?
From: David Matlack <dmatlack@google.com>
Date: Tue, 28 Apr 2026 22:57:48 +0000
Subject: [PATCH] vfio: selftests: Allow builds when ARCH=x86
Allow builds when ARCH=x86 since the top-level Makefile can set ARCH=x86
even for 64-bit x86 builds. ARCH=x86 can also be set if the host is
32-bit x86, but based on the fact that KVM selftests allow ARCH=x86 but
also don't build for 32-bit x86, this isn't an issue in practice.
Reported-by: Jason Gunthorpe <jgg@nvidia.com>
Signed-off-by: David Matlack <dmatlack@google.com>
diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
index 0684932d91bf..40165d087a0b 100644
--- a/tools/testing/selftests/vfio/Makefile
+++ b/tools/testing/selftests/vfio/Makefile
@@ -1,6 +1,6 @@
ARCH ?= $(shell uname -m)
-ifeq (,$(filter $(ARCH),aarch64 arm64 x86_64))
+ifeq (,$(filter $(ARCH),aarch64 arm64 x86 x86_64))
# Do nothing on unsupported architectures
include ../lib.mk
else
/usr/local/google/home/dmatlack/kernel/trees/vfio
prev parent reply other threads:[~2026-04-28 23:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 1:23 [PATCH v2] vfio: selftests: only build tests on arm64 and x86_64 Ted Logan
2026-02-06 17:54 ` David Matlack
2026-02-06 22:05 ` Alex Williamson
2026-03-17 13:55 ` Matt Evans
2026-03-17 19:05 ` Ted Logan
2026-04-27 23:12 ` Jason Gunthorpe
2026-04-28 1:55 ` Sean Christopherson
2026-04-28 19:02 ` David Matlack
2026-04-28 19:52 ` Sean Christopherson
2026-04-28 20:08 ` David Matlack
2026-04-28 22:03 ` Sean Christopherson
2026-04-28 22:53 ` David Matlack
2026-04-28 22:55 ` Jason Gunthorpe
2026-04-28 23:02 ` David Matlack [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=afE8hX3s-O-8yROu@google.com \
--to=dmatlack@google.com \
--cc=alex@shazbot.org \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mattev@meta.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tedlogan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.