diff options
| author |   Mark Brown <broonie@kernel.org> | 2021-12-10 18:41:01 +0000 |
|---|---|---|
| committer |   Catalin Marinas <catalin.marinas@arm.com> | 2021-12-14 18:35:10 +0000 |
| commit | 9331a604858a0f399ef8f886a88dd94927f136aa (patch) | |
| tree | 841a742e7c4c89d0a0f93146ddf195fcff2d2d47 /tools/testing | |
| parent | kselftest/arm64: Parameterise ptrace vector length information (diff) | |
| download | linux-dev-9331a604858a0f399ef8f886a88dd94927f136aa.tar.xz linux-dev-9331a604858a0f399ef8f886a88dd94927f136aa.zip | |
kselftest/arm64: Allow signal tests to trigger from a function
Currently we have the facility to specify custom code to trigger a signal
but none of the tests use it and for some reason the framework requires us
to also specify a signal to send as a trigger in order to make use of a
custom trigger. This doesn't seem to make much sense, instead allow the
use of a custom trigger function without specifying a signal to inject.
Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20211210184133.320748-6-broonie@kernel.org
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'tools/testing')
| -rw-r--r-- | tools/testing/selftests/arm64/signal/test_signals_utils.c | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/tools/testing/selftests/arm64/signal/test_signals_utils.c b/tools/testing/selftests/arm64/signal/test_signals_utils.c index 22722abc9dfa..2f8c23af3b5e 100644 --- a/tools/testing/selftests/arm64/signal/test_signals_utils.c +++ b/tools/testing/selftests/arm64/signal/test_signals_utils.c @@ -310,14 +310,12 @@ int test_setup(struct tdescr *td) int test_run(struct tdescr *td) { - if (td->sig_trig) { - if (td->trigger) - return td->trigger(td); - else - return default_trigger(td); - } else { + if (td->trigger) + return td->trigger(td); + else if (td->sig_trig) + return default_trigger(td); + else return td->run(td, NULL, NULL); - } } void test_result(struct tdescr *td) |