From: Michael Ellerman <mpe@ellerman.id.au>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: tpearson@raptorengineering.com
Subject: [PATCH 4/5] selftests/powerpc: Run fpu_preempt test for 60 seconds
Date: Wed, 29 Nov 2023 00:27:47 +1100 [thread overview]
Message-ID: <20231128132748.1990179-4-mpe@ellerman.id.au> (raw)
In-Reply-To: <20231128132748.1990179-1-mpe@ellerman.id.au>
The FPU preempt test only runs for 20 seconds, which is not particularly
long. Run it for 60 seconds to increase the chance of detecting
corruption.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
tools/testing/selftests/powerpc/math/fpu_preempt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/powerpc/math/fpu_preempt.c b/tools/testing/selftests/powerpc/math/fpu_preempt.c
index 97dff3690136..9ddede0770ed 100644
--- a/tools/testing/selftests/powerpc/math/fpu_preempt.c
+++ b/tools/testing/selftests/powerpc/math/fpu_preempt.c
@@ -22,7 +22,7 @@
#include "fpu.h"
/* Time to wait for workers to get preempted (seconds) */
-#define PREEMPT_TIME 20
+#define PREEMPT_TIME 60
/*
* Factor by which to multiply number of online CPUs for total number of
* worker threads
--
2.41.0
next prev parent reply other threads:[~2023-11-28 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:27 [PATCH 1/5] selftests/powerpc: Fix error handling in FPU/VMX preemption tests Michael Ellerman
2023-11-28 13:27 ` [PATCH 2/5] selftests/powerpc: Check all FPRs in fpu_preempt Michael Ellerman
2023-11-28 13:27 ` [PATCH 3/5] selftests/powerpc: Generate better bit patterns for FPU tests Michael Ellerman
2023-11-28 13:27 ` Michael Ellerman [this message]
2023-11-28 13:27 ` [PATCH 5/5] selftests/powerpc: Check all FPRs in fpu_syscall test Michael Ellerman
2023-12-21 10:38 ` [PATCH 1/5] selftests/powerpc: Fix error handling in FPU/VMX preemption tests Michael Ellerman
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=20231128132748.1990179-4-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tpearson@raptorengineering.com \
/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;
as well as URLs for NNTP newsgroup(s).