[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZuGr6S_At40u4WVY@zx2c4.com>
Date: Wed, 11 Sep 2024 16:40:41 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Mark Brown <broonie@...nel.org>
Cc: Aishwarya TCV <aishwarya.tcv@....com>, adhemerval.zanella@...aro.org,
linux-kernel@...r.kernel.org,
Naresh Kamboju <naresh.kamboju@...aro.org>
Subject: Re: [PATCH v2] selftests: vDSO: don't include generated headers for
chacha test
On Wed, Sep 11, 2024 at 03:12:35PM +0100, Mark Brown wrote:
> On Wed, Sep 11, 2024 at 03:36:32PM +0200, Jason A. Donenfeld wrote:
>
> > It's not correct to use $(top_srcdir) for generated header files, for
> > builds that are done out of tree via O=, and $(objtree) isn't valid in
> > the selftests context. Instead, just obviate the need for these
> > generated header files by defining empty stubs in tools/include, which
> > is the same thing that's done for rwlock.h.
>
> ...
>
> > I'll replace the broken commit with this one. I've verified the
> > kselftests are fine now, particularly for kvm.
>
> Did you also check perf? For arm64 it uses the sysregs values though I
> don't off hand know if that includes any of the generated values. I
> would expect that KVM will start breaking for arm64 at some point even
> if it works for now, there was a desire to replace use of magic numbers
> for registers in the tests with defines.
I just booted an arm64 VM and built perf with all the various options
and such, and it works fine. Those header files in the fixup commit
aren't seen by perf.
Jason
Powered by blists - more mailing lists