From: Yury Norov <yury.norov@gmail.com>
To: Alexander Potapenko <glider@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org, pcc@google.com,
andreyknvl@gmail.com, andriy.shevchenko@linux.intel.com,
linux@rasmusvillemoes.dk, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, eugenis@google.com,
syednwaris@gmail.com, william.gray@linaro.org
Subject: Re: [PATCH v3 2/5] lib/test_bitmap: add tests for bitmap_{set,get}_value()
Date: Mon, 17 Jul 2023 09:11:50 -0700 [thread overview]
Message-ID: <ZLVoRkmy5IZYbjUV@yury-ThinkPad> (raw)
In-Reply-To: <20230717113709.328671-3-glider@google.com>
On Mon, Jul 17, 2023 at 01:37:05PM +0200, Alexander Potapenko wrote:
> Add basic tests ensuring that values can be added at arbitrary positions
> of the bitmap, including those spanning into the adjacent unsigned
> longs.
>
> Signed-off-by: Alexander Potapenko <glider@google.com>
Thanks for the test!
> ---
> This patch was previously called
> "lib/test_bitmap: add tests for bitmap_{set,get}_value_unaligned"
>
> v3:
> - switch to using bitmap_{set,get}_value()
> - change the expected bit pattern in test_set_get_value(),
> as the test was incorrectly assuming 0 is the LSB.
> ---
> lib/test_bitmap.c | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/lib/test_bitmap.c b/lib/test_bitmap.c
> index 187f5b2db4cf1..c2ab54040c249 100644
> --- a/lib/test_bitmap.c
> +++ b/lib/test_bitmap.c
> @@ -71,6 +71,17 @@ __check_eq_uint(const char *srcfile, unsigned int line,
> return true;
> }
>
> +static bool __init
> +__check_eq_ulong(const char *srcfile, unsigned int line,
> + const unsigned long exp_ulong, unsigned long x)
> +{
> + if (exp_ulong != x) {
> + pr_err("[%s:%u] expected %lu, got %lu\n",
> + srcfile, line, exp_ulong, x);
> + return false;
> + }
> + return true;
> +}
>
> static bool __init
> __check_eq_bitmap(const char *srcfile, unsigned int line,
> @@ -186,6 +197,7 @@ __check_eq_str(const char *srcfile, unsigned int line,
> })
>
> #define expect_eq_uint(...) __expect_eq(uint, ##__VA_ARGS__)
> +#define expect_eq_ulong(...) __expect_eq(ulong, ##__VA_ARGS__)
> #define expect_eq_bitmap(...) __expect_eq(bitmap, ##__VA_ARGS__)
> #define expect_eq_pbl(...) __expect_eq(pbl, ##__VA_ARGS__)
> #define expect_eq_u32_array(...) __expect_eq(u32_array, ##__VA_ARGS__)
> @@ -1222,6 +1234,25 @@ static void __init test_bitmap_const_eval(void)
> BUILD_BUG_ON(~var != ~BIT(25));
> }
>
> +static void __init test_set_get_value(void)
> +{
> + DECLARE_BITMAP(bitmap, BITS_PER_LONG * 2);
It's too short. Can you make it long enough to ensure it works as
expected when start is not in the 1st word, and start+nbits is in
the following word.
> + unsigned long val;
> + int i;
> +
> + for (i = 0; i < BITS_PER_LONG * 2 - 7; i++) {
> + bitmap_zero(bitmap, BITS_PER_LONG * 2);
> + bitmap_set_value(bitmap, 0b10101UL, i, 5);
> + val = bitmap_get_value(bitmap, i, 5);
> + expect_eq_ulong(0b10101UL, val);
Can you also check that the rest of bitmap is untouched?
Something like:
DECLARE_BITMAP(bitmap, ...);
DECLARE_BITMAP(orig, ...);
memset(orig, 0x5a, ...);
memset(bitmap, 0x5a, ...);
for (j = start; j < start + nbits; j++)
if (val & BIT(j - start))
__set_bit(j, orig);
else
__clear_bit(j, orig);
bitmap_set_value(bitmap, val, start, nbits);
expect_eq_bitmap(orig, bitmap, ...);
I like this kind of testing because it gives people a better
understanding of what happens behind all that optimization tricks.
Thanks,
Yury
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-17 16:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 11:37 [PATCH v3 0/5] Implement MTE tag compression for swapped pages Alexander Potapenko
2023-07-17 11:37 ` [PATCH v3 1/5] lib/bitmap: add bitmap_{set,get}_value() Alexander Potapenko
2023-07-17 13:01 ` Andy Shevchenko
2023-07-17 14:14 ` Alexander Potapenko
2023-07-17 14:29 ` Andy Shevchenko
2023-07-17 14:31 ` Andy Shevchenko
2023-07-17 16:15 ` Yury Norov
2023-07-17 14:53 ` Alexander Potapenko
2023-07-17 15:03 ` Andy Shevchenko
2023-07-17 16:29 ` Alexander Potapenko
2023-07-17 15:50 ` Yury Norov
2023-07-18 9:30 ` Alexander Potapenko
2023-07-18 14:01 ` Andy Shevchenko
2023-07-18 17:03 ` Yury Norov
2023-07-18 17:20 ` Andy Shevchenko
2023-07-19 9:00 ` Alexander Potapenko
2023-07-17 11:37 ` [PATCH v3 2/5] lib/test_bitmap: add tests for bitmap_{set,get}_value() Alexander Potapenko
2023-07-17 13:04 ` Andy Shevchenko
2023-07-18 10:19 ` Alexander Potapenko
2023-07-17 16:11 ` Yury Norov [this message]
2023-07-17 16:28 ` Andy Shevchenko
2023-07-17 16:42 ` Alexander Potapenko
2023-07-17 11:37 ` [PATCH v3 3/5] arm64: mte: implement CONFIG_ARM64_MTE_COMP Alexander Potapenko
2023-07-17 13:49 ` Andy Shevchenko
2023-07-18 15:33 ` Alexander Potapenko
2023-07-18 17:17 ` Andy Shevchenko
2023-07-19 12:16 ` Alexander Potapenko
2023-07-19 6:09 ` Yury Norov
2023-07-19 14:00 ` Alexander Potapenko
2023-07-19 21:06 ` Yury Norov
2023-07-20 12:00 ` Alexander Potapenko
2023-07-19 20:32 ` Evgenii Stepanov
2023-07-17 11:37 ` [PATCH v3 4/5] arm64: mte: add a test for MTE tags compression Alexander Potapenko
2023-07-17 11:37 ` [PATCH v3 5/5] arm64: mte: add compression support to mteswap.c Alexander Potapenko
2023-07-17 13:53 ` Andy Shevchenko
2023-07-18 10:48 ` Alexander Potapenko
2023-07-18 14:13 ` Andy Shevchenko
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=ZLVoRkmy5IZYbjUV@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=andreyknvl@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pcc@google.com \
--cc=syednwaris@gmail.com \
--cc=will@kernel.org \
--cc=william.gray@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