diff options
author | Mark Brown <broonie@kernel.org> | 2021-12-02 19:51:07 +0300 |
---|---|---|
committer | Catalin Marinas <catalin.marinas@arm.com> | 2021-12-14 21:41:56 +0300 |
commit | 2c94ebedc844d64459bfe73b25ae725c3f040526 (patch) | |
tree | 6b05841b015d5626544a55986902f371860f43af /arch/arm64/lib | |
parent | b77e995e3b9638e759d482e93deba1fa0760cb26 (diff) | |
download | linux-2c94ebedc844d64459bfe73b25ae725c3f040526.tar.xz |
kselftest/arm64: Add pidbench for floating point syscall cases
Since it's likely to be useful for performance work with SVE let's have a
pidbench that gives us some numbers for consideration. In order to ensure
that we test exactly the scenario we want this is written in assembly - if
system libraries use SVE this would stop us exercising the case where the
process has never used SVE.
We exercise three cases:
- Never having used SVE.
- Having used SVE once.
- Using SVE after each syscall.
by spinning running getpid() for a fixed number of iterations with the
time measured using CNTVCT_EL0 reported on the console. This is obviously
a totally unrealistic benchmark which will show the extremes of any
performance variation but equally given the potential gotchas with use of
FP instructions by system libraries it's good to have some concrete code
shared to make it easier to compare notes on results.
Testing over multiple SVE vector lengths will need to be done with vlset
currently, the test could be extended to iterate over all of them if
desired.
Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20211202165107.1075259-1-broonie@kernel.org
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm64/lib')
0 files changed, 0 insertions, 0 deletions