Re: [trace:latency/for-next 33/38] ERROR: modpost: "__udivdi3" [kernel/trace/rv/rv_monitors_test.ko] undefined!

On Mon, 2026-08-03 at 08:58 +0200, Nam Cao wrote:
> kernel test robot <[email protected]> writes:
> > tree:=C2=A0=C2=A0
> > https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace=C2=A0=
latency/fo
> > r-next
> > head:=C2=A0=C2=A0 984b5a36fd12d1849511a45fda32036fe2b0d004
> > commit: 8da2a88383658dac97769ed8f807ef6100a69480 [33/38] rv: Add KUnit =
tests
> > for some DA/HA monitors
> > config: i386-allmodconfig
> > (https://download.01.org/0day-ci/archive/20260802/202608020311.hYjqOG5k=
-lkp@
> > intel.com/config)
> > compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> > reproduce (this is a W=3D1 build):
> > (https://download.01.org/0day-ci/archive/20260802/202608020311.hYjqOG5k=
-lkp@
> > intel.com/reproduce)
> >=20
> > If you fix the issue in a separate patch/commit (i.e. not just a new ve=
rsion
> > of
> > the same patch/commit), kindly add following tags
> > > Reported-by: kernel test robot <[email protected]>
> > > Closes:
> > > https://lore.kernel.org/oe-kbuild-all/202608020311.hYjqOG5k-lkp@intel=
.com/
> >=20
> > All errors (new ones prefixed by >>, old ones prefixed by <<):
> >=20
> > > > ERROR: modpost: "__udivdi3" [kernel/trace/rv/rv_monitors_test.ko]
> > > > undefined!
>=20
> We could switch the division to div64_u64(), or we could change
> deadline_thresh's type to u32.
>=20
> Gabriele, can deadline_thresh fits in u32?

That would make it limited to 4.29 s which is probably way more than enough=
 on
normal systems, but this limit would be driven purely by the KUnit test, I'=
m not
fond of that.

Probably the best thing here is to use div64_u64() (or even do_div() though=
 we
don't really care about performance).

I can send a quick fix.

Thanks,
Gabriele