From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13820] timer.profile(NNN) variant using perf probes
Date: Thu, 08 Mar 2012 01:49:00 -0000 [thread overview]
Message-ID: <bug-13820-6586-1yJamdOXlb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13820-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13820
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> 2012-03-08 01:48:28 UTC ---
e.g.
probe timer.profile.hz(997) { }
could map on a 2000 MHz core to perf.hw.cpu_clock
probe perf.type(0).config(0).sample(2006018) { }
(where 2006018 would be 2,000,000,000 / 997).
This would have to be calculated at module startup time.
And it may be that we'd actually need a more complicated
function, or even some sort of baby PLL, to approximate
the desired frequency.
It would probably be unwise to map timer.{hz,ms,etc.}(NNN)
to this because this uses up scarce resources, so can't be
unprivileged-safe.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-03-08 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 1:34 [Bug translator/13820] New: " fche at redhat dot com
2012-03-08 1:49 ` fche at redhat dot com [this message]
2015-12-02 21:30 ` [Bug translator/13820] " flu at redhat dot com
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=bug-13820-6586-1yJamdOXlb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).