From: Steven Rostedt <rostedt@goodmis.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, cleger@rivosinc.com,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 2/2] selftests/user_events: Fix abi_test for BE archs
Date: Tue, 3 Oct 2023 20:59:08 -0400 [thread overview]
Message-ID: <20231003205908.391d17f5@gandalf.local.home> (raw)
In-Reply-To: <20230925230829.341-3-beaub@linux.microsoft.com>
Note, this doesn't seem to apply to my tree so I only added the first
patch. I think this needs to go through Shuah's tree.
-- Steve
On Mon, 25 Sep 2023 23:08:29 +0000
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> The abi_test currently uses a long sized test value for enablement
> checks. On LE this works fine, however, on BE this results in inaccurate
> assert checks due to a bit being used and assuming it's value is the
> same on both LE and BE.
>
> Use int type for 32-bit values and long type for 64-bit values to ensure
> appropriate behavior on both LE and BE.
>
> Fixes: 60b1af8de8c1 ("tracing/user_events: Add ABI self-test")
> Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> ---
> tools/testing/selftests/user_events/abi_test.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/user_events/abi_test.c b/tools/testing/selftests/user_events/abi_test.c
> index 5125c42efe65..67af4c491c0c 100644
> --- a/tools/testing/selftests/user_events/abi_test.c
> +++ b/tools/testing/selftests/user_events/abi_test.c
> @@ -46,7 +46,7 @@ static int change_event(bool enable)
> return ret;
> }
>
> -static int reg_enable(long *enable, int size, int bit)
> +static int reg_enable(void *enable, int size, int bit)
> {
> struct user_reg reg = {0};
> int fd = open(data_file, O_RDWR);
> @@ -68,7 +68,7 @@ static int reg_enable(long *enable, int size, int bit)
> return ret;
> }
>
> -static int reg_disable(long *enable, int bit)
> +static int reg_disable(void *enable, int bit)
> {
> struct user_unreg reg = {0};
> int fd = open(data_file, O_RDWR);
> @@ -89,12 +89,14 @@ static int reg_disable(long *enable, int bit)
> }
>
> FIXTURE(user) {
> - long check;
> + int check;
> + long check_long;
> };
>
> FIXTURE_SETUP(user) {
> change_event(false);
> self->check = 0;
> + self->check_long = 0;
> }
>
> FIXTURE_TEARDOWN(user) {
> @@ -131,9 +133,9 @@ TEST_F(user, bit_sizes) {
>
> #if BITS_PER_LONG == 8
> /* Allow 0-64 bits for 64-bit */
> - ASSERT_EQ(0, reg_enable(&self->check, sizeof(long), 63));
> - ASSERT_NE(0, reg_enable(&self->check, sizeof(long), 64));
> - ASSERT_EQ(0, reg_disable(&self->check, 63));
> + ASSERT_EQ(0, reg_enable(&self->check_long, sizeof(long), 63));
> + ASSERT_NE(0, reg_enable(&self->check_long, sizeof(long), 64));
> + ASSERT_EQ(0, reg_disable(&self->check_long, 63));
> #endif
>
> /* Disallowed sizes (everything beside 4 and 8) */
> @@ -195,7 +197,7 @@ static int clone_check(void *check)
> for (i = 0; i < 10; ++i) {
> usleep(100000);
>
> - if (*(long *)check)
> + if (*(int *)check)
> return 0;
> }
>
next prev parent reply other threads:[~2023-10-04 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 23:08 [PATCH 0/2] tracing/user_events: Fix alignment issues for 32 on 64-bit and BE Beau Belgrave
2023-09-25 23:08 ` [PATCH 1/2] tracing/user_events: Align set_bit() address for all archs Beau Belgrave
2023-09-25 23:08 ` [PATCH 2/2] selftests/user_events: Fix abi_test for BE archs Beau Belgrave
2023-10-04 0:59 ` Steven Rostedt [this message]
2023-10-04 15:10 ` Shuah Khan
2023-10-04 15:14 ` Steven Rostedt
2023-10-04 16:38 ` Shuah Khan
2023-10-05 14:48 ` Shuah Khan
2023-10-05 15:08 ` Steven Rostedt
2023-10-05 16:52 ` Beau Belgrave
2023-10-05 17:46 ` Steven Rostedt
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=20231003205908.391d17f5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=cleger@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).