From: Michael Ellerman <mpe@ellerman.id.au>
To: Fathi Boudra <fathi.boudra@linaro.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Emilio López" <emilio.lopez@collabora.co.uk>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Fathi Boudra" <fathi.boudra@linaro.org>
Subject: Re: [PATCH 1/1] selftests: sync: add config fragment for testing sync framework
Date: Thu, 11 May 2017 14:52:57 +1000 [thread overview]
Message-ID: <87ziekhu52.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170505050550.30102-1-fathi.boudra@linaro.org>
Fathi Boudra <fathi.boudra@linaro.org> writes:
> Unless the software synchronization objects (CONFIG_SW_SYNC) is enabled,
> the sync test will fail:
>
> Additional Information:
> Running tests in sync
> ========================================
> [RUN] Testing sync framework
> [RUN] Executing test_alloc_timeline
> [ERROR] Failure allocating timeline
It would be better if the test just detected that the kernel didn't
support the API.
It seems to rely on /sys/kernel/debug/sync/sw_sync existing.
How about this?
diff --git a/tools/testing/selftests/sync/sync_test.c b/tools/testing/selftests/sync/sync_test.c
index 9ea08d9f0b13..62fa666e501a 100644
--- a/tools/testing/selftests/sync/sync_test.c
+++ b/tools/testing/selftests/sync/sync_test.c
@@ -29,6 +29,7 @@
#include <unistd.h>
#include <stdlib.h>
#include <sys/types.h>
+#include <sys/stat.h>
#include <sys/wait.h>
#include "synctest.h"
@@ -52,10 +53,22 @@ static int run_test(int (*test)(void), char *name)
exit(test());
}
+static int sync_api_supported(void)
+{
+ struct stat sbuf;
+
+ return 0 == stat("/sys/kernel/debug/sync/sw_sync", &sbuf);
+}
+
int main(void)
{
int err = 0;
+ if (!sync_api_supported()) {
+ printf("SKIP: Sync framework not supported by kernel\n");
+ return 0;
+ }
+
printf("[RUN]\tTesting sync framework\n");
err += RUN_TEST(test_alloc_timeline);
cheers
next prev parent reply other threads:[~2017-05-11 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 5:05 Fathi Boudra
2017-05-11 4:52 ` Michael Ellerman [this message]
2017-05-11 6:29 ` Fathi Boudra
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=87ziekhu52.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=emilio.lopez@collabora.co.uk \
--cc=fathi.boudra@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sumit.semwal@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
all inboxes | Powered by JetHome®