From: Simon Horman <horms@kernel.org>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Petr Oros <poros@redhat.com>,
netdev@vger.kernel.org, ivecera@redhat.com,
przemyslaw.kitszel@intel.com,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Marcin Szycik <marcin.szycik@linux.intel.com>,
Konrad Knitter <konrad.knitter@intel.com>,
Marcin Domagala <marcinx.domagala@intel.com>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@lists.osuosl.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] ice: use proper macro for testing bit
Date: Mon, 17 Jun 2024 20:04:03 +0100 [thread overview]
Message-ID: <20240617190403.GZ8447@kernel.org> (raw)
In-Reply-To: <da984106-43eb-42cc-a8c0-be859c6e84e9@intel.com>
On Mon, Jun 17, 2024 at 02:58:59PM +0200, Alexander Lobakin wrote:
> From: Simon Horman <horms@kernel.org>
> Date: Sat, 15 Jun 2024 16:16:41 +0100
>
> > On Fri, Jun 14, 2024 at 11:43:38AM +0200, Petr Oros wrote:
> >> Do not use _test_bit() macro for testing bit. The proper macro for this
> >> is one without underline.
> >
> > Hi Petr,
> >
> > it might be nice to include a brief explanation as to
> > why test_bit() is correct.
>
> Let me explain this as the author of all those bitops wrappers :D
> Petr is free to include either this or his own brief into v2.
>
> _test_bit() is what test_bit() was prior to my const-optimization. It
> directly calls arch_test_bit(), i.e. the arch-specific implementation
> (or the generic one). It's strictly _internal_ and shouldn't be used
> anywhere outside the actual test_bit() macro.
>
> test_bit() is a wrapper which checks whether the bitmap and the bit
> number are compile-time constants and if so, it calls the optimized
> function which evaluates this call to a compile-time constant as well.
> If either of them is not a compile-time constant, it just calls _test_bit().
> test_bit() is the actual function to use anywhere in the kernel.
>
> IOW, calling _test_bit() avoids potential compile-time optimizations.
>
> >From what I see in the code, &sensors is not a compile-time constant,
> thus most probably there are no object code changes before and after
> the patch. But anyway, we shouldn't call internal wrappers instead of
> the actual API, so this fix is correct.
Thanks for this very comprehensive description, now I know :)
> >> Fixes: 4da71a77fc3b ("ice: read internal temperature sensor")
> >> Signed-off-by: Petr Oros <poros@redhat.com>
> >> Acked-by: Ivan Vecera <ivecera@redhat.com>
>
> To be added to v2:
>
> Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
>
> Thanks,
> Olek
>
prev parent reply other threads:[~2024-06-17 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 9:43 [PATCH net v2] ice: use proper macro for testing bit Petr Oros
2024-06-15 15:16 ` Simon Horman
2024-06-17 12:58 ` Alexander Lobakin
2024-06-17 19:04 ` Simon Horman [this message]
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=20240617190403.GZ8447@kernel.org \
--to=horms@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=konrad.knitter@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=marcinx.domagala@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslaw.kitszel@intel.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).