From: Vojtech Pavlik <vojtech@suse.cz>
To: george anzinger <george@mvista.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Bjorn Helgaas <bjorn_helgaas@hp.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] joydev: fix HZ->millisecond transformation
Date: Sat, 21 Dec 2002 10:18:51 +0100 [thread overview]
Message-ID: <20021221101851.A29004@ucw.cz> (raw)
In-Reply-To: <3E035E7B.D3B60845@mvista.com>; from george@mvista.com on Fri, Dec 20, 2002 at 10:16:27AM -0800
On Fri, Dec 20, 2002 at 10:16:27AM -0800, george anzinger wrote:
> Vojtech Pavlik wrote:
> >
> > On Fri, Dec 20, 2002 at 09:24:58AM -0800, george anzinger wrote:
> > > Vojtech Pavlik wrote:
> > > >
> > > > On Fri, Dec 20, 2002 at 02:41:50AM -0800, george anzinger wrote:
> > > > > Bjorn Helgaas wrote:
> > > > > >
> > > > > > * fix a problem with HZ->millisecond transformation on
> > > > > > non-x86 archs (from 2.5 change by vojtech@suse.cz)
> > > > > >
> > > > > > Applies to 2.4.20.
> > > > > >
> > > > > > diff -Nru a/drivers/input/joydev.c b/drivers/input/joydev.c
> > > > > > --- a/drivers/input/joydev.c Mon Dec 16 12:16:32 2002
> > > > > > +++ b/drivers/input/joydev.c Mon Dec 16 12:16:32 2002
> > > > > > @@ -50,6 +50,8 @@
> > > > > > #define JOYDEV_MINORS 32
> > > > > > #define JOYDEV_BUFFER_SIZE 64
> > > > > >
> > > > > > +#define MSECS(t) (1000 * ((t) / HZ) + 1000 * ((t) % HZ) / HZ)
> > > > > Uh...
> > > > > ^^^^^^^^^^^^^^^^
> > > > > by definition this is zero, is it not?
> > > >
> > > > No, both parts of the equaition can be nonzero.
> > >
> > > I don't think so. s%HZ has to be less than HZ. Then
> > > dividing that by HZ should result in zero. Where is my
> > > thinking flawed?
> >
> > You first multiply it by 1000.
>
> But then it should read: (1000 * (t)) % HZ) / HZ
The expression is evaluated from left to right. No need for parentheses
here.
> But this is still zero. There is no way that ((X % HZ) /
> HZ) is other than zero, me thinks.
Example:
HZ = 100
t = 70
1000 * (t % HZ) / HZ = 1000 * 70 / 100 = 700 != 0
Anyway (x % HZ) / HZ must be zero, but that's something different.
> > > > Though it might be easier to say (1000 * t) / HZ, now that I think about
> > > > it.
> > >
> > > That overflows... As does the other if HZ is less than 1000....
> >
> > You're right, t can be all 32 bits.
>
> What, exactly, is this code trying to do? It looks like the
> number is being passed to user space...
It's trying to convert jiffies to microseconds from computer start (or
any other arbitrary point in time), thus making the value independent of
HZ.
> --
> George Anzinger george@mvista.com
> High-res-timers:
> http://sourceforge.net/projects/high-res-timers/
> Preemption patch:
> http://www.kernel.org/pub/linux/kernel/people/rml
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-12-21 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 19:27 [PATCH] joydev: fix HZ->millisecond transformation Bjorn Helgaas
2002-12-20 10:41 ` george anzinger
2002-12-20 13:24 ` Vojtech Pavlik
2002-12-20 14:52 ` Joe Korty
2002-12-20 17:24 ` george anzinger
2002-12-20 17:35 ` Vojtech Pavlik
2002-12-20 18:16 ` george anzinger
2002-12-21 9:18 ` Vojtech Pavlik [this message]
2002-12-21 16:46 ` george anzinger
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=20021221101851.A29004@ucw.cz \
--to=vojtech@suse.cz \
--cc=bjorn_helgaas@hp.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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