From: Yury Norov <yury.norov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v1 1/2] lib/test_bitmap: Correct test data offsets for 32-bit
Date: Wed, 8 Jan 2020 12:43:07 -0800 [thread overview]
Message-ID: <20200108204307.GC14503@yury-thinkpad> (raw)
In-Reply-To: <20200108202654.GJ32742@smile.fi.intel.com>
On Wed, Jan 08, 2020 at 10:26:54PM +0200, Andy Shevchenko wrote:
> On Wed, Jan 08, 2020 at 11:24:37AM -0800, Yury Norov wrote:
> > On Wed, Jan 08, 2020 at 08:46:10PM +0200, Andy Shevchenko wrote:
> > > On 32-bit platform the size of long is only 32 bits which makes wrong offset
> > > in the array of 64 bit size.
> > >
> > > Calculate offset based on BITS_PER_LONG.
> > >
> > > Fixes: 30544ed5de43 ("lib/bitmap: introduce bitmap_replace() helper")
> > > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> > > unsigned int nbits = 64;
> > > + unsigned int step = DIV_ROUND_UP(nbits, BITS_PER_LONG);
> >
> > Step is already defined in this file:
> > #define step (sizeof(u64) / sizeof(unsigned long))
>
> ...and later undefined.
>
> > to avoid the same problem in other test cases. Introducing another variant of
> > it looks messy.
>
> I don't see any problem.
The problem is that you reimplement the functionality instead of
reuse.
> > > DECLARE_BITMAP(bmap, 1024);
> > >
> > > bitmap_zero(bmap, 1024);
> > > - bitmap_replace(bmap, &exp2[0], &exp2[1], exp2_to_exp3_mask, nbits);
> > > + bitmap_replace(bmap, &exp2[0 * step], &exp2[1 * step], exp2_to_exp3_mask, nbits);
> > > expect_eq_bitmap(bmap, exp3_0_1, nbits);
> >
> > If nbits is always 64, why don't you pass 64 directly?
>
> We may use any setting. For now it's 64, but nothing prevents us to extend to,
> let's say, 75.
>
> --
> With Best Regards,
> Andy Shevchenko
>
next prev parent reply other threads:[~2020-01-08 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 18:46 [PATCH v1 1/2] lib/test_bitmap: Correct test data offsets for 32-bit Andy Shevchenko
2020-01-08 18:46 ` [PATCH v1 2/2] lib/test_bitmap: Fix address space when test user buffer Andy Shevchenko
2020-01-08 19:24 ` [PATCH v1 1/2] lib/test_bitmap: Correct test data offsets for 32-bit Yury Norov
2020-01-08 20:26 ` Andy Shevchenko
2020-01-08 20:43 ` Yury Norov [this message]
2020-01-09 10:27 ` 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=20200108204307.GC14503@yury-thinkpad \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.