linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	 Stephen Boyd <sboyd@kernel.org>,
	 "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>
Subject: RE: [linux-next:master 2742/4710] drivers/clk/clk-versaclock3.c:404:2-8: WARNING: do_div() does a 64-by-32 division, please consider using div64_ul instead. (fwd)
Date: Thu, 27 Jul 2023 10:43:40 +0200 (CEST)	[thread overview]
Message-ID: <bf5c77ec-fc9f-419a-d0e8-15ad54df2fb@inria.fr> (raw)
In-Reply-To: <OS0PR01MB59227764417EB66A9CBDE69F8601A@OS0PR01MB5922.jpnprd01.prod.outlook.com>



On Thu, 27 Jul 2023, Biju Das wrote:

> Hi,
>
> The reproduce link is not working for me.
>
> https://download.01.org/0day-ci/archive/20230727/202307270841.yr5HxYIl-lkp@intel.com/reproduce
>
> Can you please provide instruction to reproduce this issue?

I don't think it's intended to be reproduced.  The issue is just that a
long value is being passed to an integer that is 32 bit.  If the long
value will never be very big, then you can just ignore the warning.

julia

>
> Cheers,
> Biju
>
> > versaclock3.c:404:2-8: WARNING: do_div() does a 64-by-32 division,
> > please consider using div64_ul instead. (fwd)
> >
> >
> >
> > ---------- Forwarded message ----------
> > Date: Thu, 27 Jul 2023 08:50:37 +0800
> > From: kernel test robot <lkp@intel.com>
> > To: oe-kbuild@lists.linux.dev
> > Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
> > Subject: [linux-next:master 2742/4710] drivers/clk/clk-
> > versaclock3.c:404:2-8:
> >     WARNING: do_div() does a 64-by-32 division,
> >     please consider using div64_ul instead.
> >
> > BCC: lkp@intel.com
> > CC: oe-kbuild-all@lists.linux.dev
> > CC: Linux Memory Management List <linux-mm@kvack.org>
> > TO: Biju Das <biju.das.jz@bp.renesas.com>
> > CC: Stephen Boyd <sboyd@kernel.org>
> >
> > tree:
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new
> > version of the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Reported-by: Julia Lawall <julia.lawall@inria.fr>
> > | Closes:
> %2BsY49B78%3D&reserved=0
> >
> > cocci warnings: (new ones prefixed by >>)
> > >> drivers/clk/clk-versaclock3.c:404:2-8: WARNING: do_div() does a 64-
> > by-32 division, please consider using div64_ul instead.
> >
> > vim +404 drivers/clk/clk-versaclock3.c
> >
> > 6e9aff555db7b6 Biju Das 2023-07-05  382
> > 6e9aff555db7b6 Biju Das 2023-07-05  383  static long
> > vc3_pll_round_rate(struct clk_hw *hw, unsigned long rate,
> > 6e9aff555db7b6 Biju Das 2023-07-05  384  			       unsigned
> > long *parent_rate)
> > 6e9aff555db7b6 Biju Das 2023-07-05  385  {
> > 6e9aff555db7b6 Biju Das 2023-07-05  386  	struct vc3_hw_data *vc3 =
> > container_of(hw, struct vc3_hw_data, hw);
> > 6e9aff555db7b6 Biju Das 2023-07-05  387  	const struct vc3_pll_data *pll
> > = vc3->data;
> > 6e9aff555db7b6 Biju Das 2023-07-05  388  	u64 div_frc;
> > 6e9aff555db7b6 Biju Das 2023-07-05  389
> > 6e9aff555db7b6 Biju Das 2023-07-05  390  	if (rate < pll->vco_min)
> > 6e9aff555db7b6 Biju Das 2023-07-05  391  		rate = pll->vco_min;
> > 6e9aff555db7b6 Biju Das 2023-07-05  392  	if (rate > pll->vco_max)
> > 6e9aff555db7b6 Biju Das 2023-07-05  393  		rate = pll->vco_max;
> > 6e9aff555db7b6 Biju Das 2023-07-05  394
> > 6e9aff555db7b6 Biju Das 2023-07-05  395  	vc3->div_int = rate /
> > *parent_rate;
> > 6e9aff555db7b6 Biju Das 2023-07-05  396
> > 6e9aff555db7b6 Biju Das 2023-07-05  397  	if (pll->num == VC3_PLL2) {
> > 6e9aff555db7b6 Biju Das 2023-07-05  398  		if (vc3->div_int > 0x7ff)
> > 6e9aff555db7b6 Biju Das 2023-07-05  399  			rate = *parent_rate
> > * 0x7ff;
> > 6e9aff555db7b6 Biju Das 2023-07-05  400
> > 6e9aff555db7b6 Biju Das 2023-07-05  401  		/* Determine best
> > fractional part, which is 16 bit wide */
> > 6e9aff555db7b6 Biju Das 2023-07-05  402  		div_frc = rate %
> > *parent_rate;
> > 6e9aff555db7b6 Biju Das 2023-07-05  403  		div_frc *= BIT(16) - 1;
> > 6e9aff555db7b6 Biju Das 2023-07-05 @404  		do_div(div_frc,
> > *parent_rate);
> > 6e9aff555db7b6 Biju Das 2023-07-05  405
> > 6e9aff555db7b6 Biju Das 2023-07-05  406  		vc3->div_frc =
> > (u32)div_frc;
> > 6e9aff555db7b6 Biju Das 2023-07-05  407  		rate = (*parent_rate *
> > 6e9aff555db7b6 Biju Das 2023-07-05  408  			(vc3->div_int *
> > VC3_2_POW_16 + div_frc) / VC3_2_POW_16);
> > 6e9aff555db7b6 Biju Das 2023-07-05  409  	} else {
> > 6e9aff555db7b6 Biju Das 2023-07-05  410  		rate = *parent_rate *
> > vc3->div_int;
> > 6e9aff555db7b6 Biju Das 2023-07-05  411  	}
> > 6e9aff555db7b6 Biju Das 2023-07-05  412
> > 6e9aff555db7b6 Biju Das 2023-07-05  413  	return rate;
> > 6e9aff555db7b6 Biju Das 2023-07-05  414  }
> > 6e9aff555db7b6 Biju Das 2023-07-05  415
> >
> > --
> > 0-DAY CI Kernel Test Service
>


  reply	other threads:[~2023-07-27  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  5:10 Julia Lawall
2023-07-27  8:34 ` Biju Das
2023-07-27  8:43   ` Julia Lawall [this message]
2023-07-27  9:19     ` Biju Das
2023-07-27  9:25       ` Geert Uytterhoeven
2023-07-27 10:01         ` Biju Das

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=bf5c77ec-fc9f-419a-d0e8-15ad54df2fb@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sboyd@kernel.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