From: Jules Bashizi Irenge <jbi.octave@gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf/x86/amd/power: Use div64_u64 onstead of do_div()
Date: Thu, 2 May 2024 17:34:46 +0100 [thread overview]
Message-ID: <ZjPApuDc0gL9Pchm@octinomon.home> (raw)
In-Reply-To: <41180245c6e94a06b789cd44b8aebd62@AcuMS.aculab.com>
On Thu, May 02, 2024 at 04:25:58PM +0000, David Laight wrote:
> From: Jules Irenge <jbi.octave@gmail.com>
> > Sent: 28 April 2024 17:40
> >
> > do_div() truncates a u64 divisor to 32 bit.
> > This can lead to non-zero being truncated to zero for division.
> >
> > Fix coccinelle warning
> > WARNING: do_div() does a 64-by-32 division, please consider using div64_u64 instead
> >
> > Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
> > ---
> > arch/x86/events/amd/power.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/events/amd/power.c b/arch/x86/events/amd/power.c
> > index 37d5b380516e..ff003c1a645b 100644
> > --- a/arch/x86/events/amd/power.c
> > +++ b/arch/x86/events/amd/power.c
> > @@ -64,7 +64,7 @@ static void event_update(struct perf_event *event)
> > delta *= cpu_pwr_sample_ratio * 1000;
> > tdelta = new_ptsc - prev_ptsc;
> >
> > - do_div(delta, tdelta);
> > + div64_u64(delta, tdelta);
>
> Nak - you've not tested it.
>
> David
>
No, I later realised it's for 32bit here. It may be very expensive for
a 32bit.
I think I got it wrong here.
Thanks for reply.
Jules
next prev parent reply other threads:[~2024-05-02 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 16:40 [PATCH] perf/x86/amd/power: Use div64_u64 onstead of do_div() Jules Irenge
2024-05-02 16:25 ` David Laight
2024-05-02 16:34 ` Jules Bashizi Irenge [this message]
2024-05-02 22:18 ` David Laight
2024-05-02 22:59 ` Linus Torvalds
2024-05-04 22:53 ` David Laight
2024-05-05 19:38 ` Linus Torvalds
2024-05-06 16:39 ` David Laight
2024-05-06 16:45 ` Linus Torvalds
2024-05-06 17:26 ` Linus Torvalds
2024-05-06 20:25 ` David Laight
2024-05-06 17:43 ` 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=ZjPApuDc0gL9Pchm@octinomon.home \
--to=jbi.octave@gmail.com \
--cc=David.Laight@aculab.com \
--cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).