Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, bjorn.andersson@linaro.org,
	evgreen@chromium.org, cpratapa@codeaurora.org,
	subashab@codeaurora.org, lkp@intel.com, elder@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipa: always inline ipa_aggr_granularity_val()
Date: Wed, 11 Aug 2021 15:02:38 +0300	[thread overview]
Message-ID: <YRO8Xtd9+RRMqw1J@unreal> (raw)
In-Reply-To: <20210810160213.2257424-1-elder@linaro.org>

On Tue, Aug 10, 2021 at 11:02:13AM -0500, Alex Elder wrote:
> It isn't required, but all callers of ipa_aggr_granularity_val()
> pass a constant value (IPA_AGGR_GRANULARITY) as the usec argument.
> Two of those callers are in ipa_validate_build(), with the result
> being passed to BUILD_BUG_ON().
> 
> Evidently the "sparc64-linux-gcc" compiler (at least) doesn't always
> inline ipa_aggr_granularity_val(), so the result of the function is
> not constant at compile time, and that leads to build errors.
> 
> Define the function with the __always_inline attribute to avoid the
> errors.  And given that the function is inline, we can switch the
> WARN_ON() there to be BUILD_BUG_ON().
> 
> Fixes: 5bc5588466a1f ("net: ipa: use WARN_ON() rather than assertions")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
> 
> David/Jakub, this fixes a bug in a commit in net-next/master.  -Alex
> 
>  drivers/net/ipa/ipa_main.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ipa/ipa_main.c b/drivers/net/ipa/ipa_main.c
> index 25bbb456e0078..f90b3521e266b 100644
> --- a/drivers/net/ipa/ipa_main.c
> +++ b/drivers/net/ipa/ipa_main.c
> @@ -255,9 +255,9 @@ ipa_hardware_config_qsb(struct ipa *ipa, const struct ipa_data *data)
>   * less than the number of timer ticks in the requested period.  0 is not
>   * a valid granularity value.
>   */
> -static u32 ipa_aggr_granularity_val(u32 usec)
> +static __always_inline u32 ipa_aggr_granularity_val(u32 usec)
>  {
> -	WARN_ON(!usec);
> +	BUILD_BUG_ON(!usec);

So what exactly are you checking here if all callers pass same value?
It is in-kernel API, declared as static inside one module. There is no
need to protect from itself.

Thanks

>  
>  	return DIV_ROUND_CLOSEST(usec * TIMER_FREQUENCY, USEC_PER_SEC) - 1;
>  }
> -- 
> 2.27.0
> 

  reply	other threads:[~2021-08-11 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 16:02 Alex Elder
2021-08-11 12:02 ` Leon Romanovsky [this message]
2021-08-11 12:06   ` Alex Elder
2021-08-11 12:12     ` Leon Romanovsky

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=YRO8Xtd9+RRMqw1J@unreal \
    --to=leon@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cpratapa@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=elder@kernel.org \
    --cc=elder@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=subashab@codeaurora.org \
    --subject='Re: [PATCH net-next] net: ipa: always inline ipa_aggr_granularity_val()' \
    /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

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).