public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@nvidia.com>
To: David Laight <david.laight.linux@gmail.com>
Cc: "Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Crt Mori" <cmo@melexis.com>, "Nuno Sá" <nuno.sa@analog.com>,
	"Richard Genoud" <richard.genoud@bootlin.com>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Yury Norov" <yury.norov@gmail.com>,
	"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
	"Matt Coster" <matt.coster@imgtec.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] bitfield.h: Ensure FIELD_PREP_CONST() is constant
Date: Sat, 11 Apr 2026 00:24:28 -0400	[thread overview]
Message-ID: <adnM_K4zJk1gc3k0@yury> (raw)
In-Reply-To: <20260410194539.560b5fdc@pumpkin>

On Fri, Apr 10, 2026 at 07:45:38PM +0100, David Laight wrote:
> On Fri, 10 Apr 2026 12:55:25 -0400
> Yury Norov <ynorov@nvidia.com> wrote:
 
 ...

> > > Note that when 'val' is a variable 'val << constant' is likely
> > > to execute faster than 'val * (1 << constant)'.
> > > So the normal FIELD_PREP() is best left alone.  
> > 
> > Do you have any numbers? I'd prefer to have the codebase consistent
> > when possible.
> 
> I think the multiply instruction will have a higher latency than the shift.
> So you are talking about a very small number of clocks if the expression
> is in the critical register dependency path.
> However FIELD_GET() would need to use a divide - and that would be a lot
> worse.
>
> Having written that, ISTR that 'mask' is required to be a constant.
> So the compiler may use a shift anyway - if the divide is unsigned.
> But for non-constant mask you definitely want a 'shift right'.

Non-constant masks are handled with __field_get(), which doesn't use
__bf_shf().

> While you might think that it only makes sense to use unsigned values,
> I've found one piece of code (IIRC in the x86 fault handler) that
> passes a signed value to FIELD_GET() and needs the result sign extended.
> So, unless that is changed, FIELD_GET() must use an explicit right shift.
> (Of course, right shift of negative values is probably UB...)

FIELD_GET() is quite fine with the change:

 #define __FIELD_GET(mask, reg, pfx)                                    \
         ({                                                              \
                 __BF_FIELD_CHECK_MASK(mask, 0U, pfx);                   \
 -               (typeof(mask))(((reg) & (mask)) >> __bf_shf(mask));     \
 +               (typeof(mask))(((reg) & (mask)) / __bf_low_bit(mask));  \
         })
 
void my_test(void)
{
        f3 0f 1e fa             endbr64
        48 83 ec 08             sub    $0x8,%rsp
        volatile int i = -1;

        pr_err("%lx\n", FIELD_GET(GENMASK(10,5), i));
        48 c7 c7 13 e3 51 82    mov    $0xffffffff8251e313,%rdi
        volatile int i = -1;
        c7 44 24 04 ff ff ff    movl   $0xffffffff,0x4(%rsp)
        ff 
        pr_err("%lx\n", FIELD_GET(GENMASK(10,5), i));
        8b 74 24 04             mov    0x4(%rsp),%esi

}
        48 83 c4 08             add    $0x8,%rsp
        pr_err("%lx\n", FIELD_GET(GENMASK(10,5), i));
        81 e6 e0 07 00 00       and    $0x7e0,%esi
        48 c1 ee 05             shr    $0x5,%rsi
        e9 32 aa b9 ff          jmp    <_printk>

Thanks,
Yury

  reply	other threads:[~2026-04-11  4:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  9:09 [PATCH 1/1] bitfield.h: Ensure FIELD_PREP_CONST() is constant david.laight.linux
2026-04-10 16:55 ` Yury Norov
2026-04-10 18:45   ` David Laight
2026-04-11  4:24     ` Yury Norov [this message]
2026-04-11 10:54       ` David Laight

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=adnM_K4zJk1gc3k0@yury \
    --to=ynorov@nvidia.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=cmo@melexis.com \
    --cc=david.laight.linux@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=matt.coster@imgtec.com \
    --cc=nuno.sa@analog.com \
    --cc=richard.genoud@bootlin.com \
    --cc=yury.norov@gmail.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