From: Carlos O'Donell <carlos@systemhalted.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Tres Melton <tres@mindspring.com>,
parisc-linux@lists.parisc-linux.org,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] [Testers wanted] New glibc with profiling fixed.
Date: Tue, 26 Jul 2005 13:01:35 -0400 [thread overview]
Message-ID: <20050726170109.GQ30182@systemhalted.org> (raw)
In-Reply-To: <42E647E8.3000505@tausq.org>
On Tue, Jul 26, 2005 at 10:25:44PM +0800, Randolph Chung wrote:
> >User space should not "know" what HZ the kernel is using. Instead, all
> >interfaces should be properly reported in terms of whatever HZ userspace
> >used to assume (100 on i386, other values on other platforms). I don't
> >know what interface gprof is using, but it needs to be fixed.
>
> I thought gprof uses a SIGPROF timer using the setitimer interface. Why
> is it HZ dependent?
Even though you get a signal you have to calculate the elapsed time.
The profiling codes prefers "times" to "getrusage" to "clock."
Unfortunately to interpret "times" information you need to multiply by
ticks_to_msec.
IMO any interface exporting/using ticks is broken. Accurate time can
be provided through other interfaces. Userspace should never see ticks,
only converted time.
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-26 17:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 12:56 [parisc-linux] [Testers wanted] New glibc with profiling fixed Tres Melton
2005-07-25 0:09 ` Grant Grundler
[not found] ` <1122272788.10644.71.camel@thor.tres.org>
2005-07-26 13:24 ` Grant Grundler
2005-07-26 13:37 ` Tres Melton
2005-07-26 14:18 ` Matthew Wilcox
2005-07-26 14:25 ` Randolph Chung
2005-07-26 17:01 ` Carlos O'Donell [this message]
2005-07-26 17:09 ` Matthew Wilcox
2005-07-26 18:08 ` Carlos O'Donell
2005-07-26 15:26 ` Tres Melton
2005-07-26 17:16 ` Carlos O'Donell
[not found] <no.id>
2004-01-07 21:14 ` John David Anglin
2004-01-07 21:14 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 19:48 Carlos O'Donell
2004-01-05 19:48 Carlos O'Donell
2004-01-05 19:48 ` Carlos O'Donell
2004-01-05 19:48 ` Carlos O'Donell
2004-01-11 4:09 ` Grant Grundler
2004-01-11 20:43 ` Carlos O'Donell
2004-01-12 16:38 ` Grant Grundler
2004-01-12 16:38 ` Grant Grundler
2004-01-13 5:42 ` Grant Grundler
2004-01-13 5:42 ` Grant Grundler
2004-01-13 8:46 ` Joel Soete
2004-01-13 8:46 ` Joel Soete
2004-01-11 20:43 ` Carlos O'Donell
2004-01-11 4:09 ` Grant Grundler
2004-01-05 20:45 ` Grant Grundler
2004-01-05 20:45 ` Grant Grundler
2004-01-05 22:00 ` Carlos O'Donell
2004-01-05 22:00 ` Carlos O'Donell
2004-01-07 21:04 ` John David Anglin
2004-01-07 21:04 ` John David Anglin
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=20050726170109.GQ30182@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
--cc=tres@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.