From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Mark Brown <broonie@kernel.org>
Cc: Aishwarya TCV <aishwarya.tcv@arm.com>,
adhemerval.zanella@linaro.org, linux-kernel@vger.kernel.org,
Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH v2] selftests: vDSO: don't include generated headers for chacha test
Date: Wed, 11 Sep 2024 16:40:41 +0200 [thread overview]
Message-ID: <ZuGr6S_At40u4WVY@zx2c4.com> (raw)
In-Reply-To: <8d4c1292-1e4d-4d11-b6c2-66dbb5aedb6d@sirena.org.uk>
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
prev parent reply other threads:[~2024-09-11 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 15:58 [PATCH] selftests: vDSO: don't include generated headers for chacha test Jason A. Donenfeld
2024-09-04 16:19 ` Adhemerval Zanella Netto
2024-09-10 22:52 ` Aishwarya TCV
2024-09-11 2:44 ` Jason A. Donenfeld
2024-09-11 10:14 ` Mark Brown
2024-09-11 12:47 ` Jason A. Donenfeld
2024-09-11 13:01 ` Jason A. Donenfeld
2024-09-11 13:33 ` Jason A. Donenfeld
2024-09-11 13:36 ` [PATCH v2] " Jason A. Donenfeld
2024-09-11 14:12 ` Mark Brown
2024-09-11 14:40 ` Jason A. Donenfeld [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=ZuGr6S_At40u4WVY@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=aishwarya.tcv@arm.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.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