From: Jason Gunthorpe <jgg@nvidia.com>
To: David Matlack <dmatlack@google.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 19:55:28 -0300 [thread overview]
Message-ID: <20260428225528.GA3225388@nvidia.com> (raw)
In-Reply-To: <CALzav=e08+Kh60daAM=A7rAwRU-SFs8m7k2JqSb6v+=T9RZGSQ@mail.gmail.com>
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..
<sigh wishes to have a better build system for userspace selftests>
Jason
next prev parent reply other threads:[~2026-04-28 22:55 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 [this message]
2026-04-28 23:02 ` David Matlack
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=20260428225528.GA3225388@nvidia.com \
--to=jgg@nvidia.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox