From: Tabris <tabris@tabris.net>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: lkml <linux-kernel@vger.kernel.org>, <bero@arklinux.org>,
<saint@arklinux.org>, Alan Cox <alan@redhat.com>
Subject: Re: Jiffies_64 for 2.4.22-ac
Date: Fri, 12 Sep 2003 11:07:03 -0400 [thread overview]
Message-ID: <200309121107.06021.tabris@tabris.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0309121541180.21331-100000@gans.physik3.uni-rostock.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 12 September 2003 10:00 am, Tim Schmielau wrote:
> On Fri, 12 Sep 2003, Tabris wrote:
> > I took Tim Schmielau's jiffies_64 patch, and ported it to -ac
> >
> > currently running on my machine here.
> > comments? did i screw up horribly?
>
> see my comments below:
> > +#define get_uidle_64()
> > get_64bits(&(init_tasks[0]->times.tms_utime),\ +
> > &uidle_msb_flips)
> > +#define get_sidle_64()
> > get_64bits(&(init_tasks[0]->times.tms_stime),\ +
> > &sidle_msb_flips)
>
> for -ac this needs to be
>
> +#define get_uidle_64() get_64bits(&(init_task.times.tms_utime),\
> + &uidle_msb_flips)
> +#define get_sidle_64() get_64bits(&(init_task.times.tms_stime),\
> + &sidle_msb_flips)
>
> > + check_one(init_tasks[0]->times.tms_utime, &uidle_msb_flips);
> > + check_one(init_tasks[0]->times.tms_stime, &sidle_msb_flips);
>
> ditto
>
>
> +#define get_uidle_64() (init_tasks[0]->times.tms_utime)
> +#define get_sidle_64() (init_tasks[0]->times.tms_stime)
>
> ditto
>
> > - unsigned long uptime;
> > - unsigned long idle;
> > + u64 uptime, idle;
> > int len;
>
> the declaration
> unsigned long uptime_remainder, idle_remainder;
> is missing
>
> > #if HZ!=100
> > len = sprintf(page,"%lu.%02lu %lu.%02lu\n",
> > - uptime / HZ,
> > - (((uptime % HZ) * 100) / HZ) % 100,
> > - idle / HZ,
> > - (((idle % HZ) * 100) / HZ) % 100);
> > + (unsigned long) uptime,
> > + uptime_remainder,
> > + (unsigned long) idle / HZ,
> > + idle_remainder);
>
> since we're in the HZ!=100 branch, this needs to be
>
> + (uptime_remainder * 100) / HZ,
> + (unsigned long) idle,
> + (idle_remainder * 100) / HZ);
>
>
>
> I wonder it actually compiled, but otherwise it looks good.
>
> Tim
>
oops.
yeah, i merged it originally against a different tree... that patch didn't
apply against 2.4.22-ac
and i forgot to compile test it since i was too tired.
updated/fixed patch later today.
- --
tabris
- -
"...A strange enigma is man!"
"Someone calls him a soul concealed in an animal," I suggested.
"Winwood Reade is good upon the subject," said Holmes. "He remarked
that, while the individual man is an insoluble puzzle, in the aggregate he
becomes a mathematical certainty. You can, for example, never foretell
what any one man will do, but you can say with precision what an average
number will be up to. Individuals vary, but percentages remain constant.
So says the statistician."
-- Sherlock Holmes, "The Sign of Four"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/YeEYtTgrITXtL+8RAm6zAJ93ljgW0p70fgrrjvhu52Dod+fOawCcCLjc
Ns6HWVXlCbIHWf8t2FB9BzI=
=ya6P
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-09-12 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 4:35 Jiffies_64 for 2.4.22-ac Tabris
2003-09-12 14:00 ` Tim Schmielau
2003-09-12 15:07 ` Tabris [this message]
2003-09-12 16:00 ` Tabris
2003-09-12 17:10 ` Tim Schmielau
2003-09-12 17:38 ` Tabris
2003-09-13 1:46 ` Tim Schmielau
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=200309121107.06021.tabris@tabris.net \
--to=tabris@tabris.net \
--cc=alan@redhat.com \
--cc=bero@arklinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saint@arklinux.org \
--cc=tim@physik3.uni-rostock.de \
/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