From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>, Lincoln Dale <ltd@cisco.com>
Cc: David Luyer <david_luyer@pacific.net.au>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew
Date: Wed, 31 Jul 2002 20:34:22 -0700 [thread overview]
Message-ID: <771740373.1028147661@[10.10.2.3]> (raw)
In-Reply-To: <200208010133.g711Xq7338295@saturn.cs.uml.edu>
> No shit. Now, how do you create a ps executable that handles
> a 2.4.xx kernel with a modified HZ value? People did this all
> the time. I got many bug reports from these people, so don't
> go saying they don't exist. Remember: one executable, running
> on both of the these:
>
> <rant deleted>
Is it somehow impossible to just export HZ in /proc, and read it?
Doesn't seem too hard to me.
M.
next prev parent reply other threads:[~2002-08-01 3:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 11:01 David Luyer
2002-07-31 13:28 ` Alan Cox
2002-07-31 12:59 ` David Luyer
2002-07-31 14:26 ` Alan Cox
2002-07-31 13:18 ` David Luyer
2002-07-31 13:31 ` Dana Lacoste
2002-07-31 13:38 ` David Luyer
2002-07-31 15:04 ` Alan Cox
2002-07-31 13:57 ` David Luyer
2002-07-31 16:15 ` NMI watchdog, die(), & console_loglevel Jonathan Lundell
2002-07-31 19:14 ` Linux 2.4.19ac3rc3 on IBM x330/x340 SMP - "ps" time skew Albert D. Cahalan
2002-08-01 0:37 ` Alan Cox
2002-07-31 23:49 ` Dave Jones
2002-08-01 1:30 ` Alan Cox
2002-08-01 0:19 ` Dave Jones
2002-07-31 23:42 ` Lincoln Dale
2002-08-01 1:33 ` Albert D. Cahalan
2002-08-01 3:34 ` Martin J. Bligh [this message]
2002-08-01 14:16 ` Alan Cox
2002-08-01 8:49 ` Benjamin Herrenschmidt
2002-08-01 11:40 ` Lincoln Dale
2002-08-01 18:26 ` Albert D. Cahalan
2002-08-01 14:15 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 2:46 David Luyer
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='771740373.1028147661@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david_luyer@pacific.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.com \
/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
all inboxes | Powered by JetHome®