From: Stephane Eranian <eranian@hpl.hp.com>
To: perfmon2-devel@lists.sourceforge.net
Cc: perfmon@napali.hpl.hp.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, Stephane Eranian <eranian@hpl.hp.com>
Subject: conflict between tickless and perfmon2
Date: Fri, 09 Nov 2007 10:44:38 +0000 [thread overview]
Message-ID: <20071109104438.GB18909@frankl.hpl.hp.com> (raw)
Hello,
We have identified a conflict between TICKLESS (CONFIG_NO_HZ) and
the current perfmon2 implementation. The problem impacts system-wide
sessions using timeout-based event set multiplexing.
Event set multiplexing allows monitoring tools to measure more events
than there are actual performance counters on the processor. Events
are grouped in sets which are then multiplexed onto the actual counters.
Switching can be triggered either by a timeout or by a counter overflow.
This is supported for per-thread and system-wide sessions.
For timeout-based switching, the duration expressed in nanoseconds is
meant to represent wall-clock time in system-wide mode, and execution
time in per-thread mode. Granularity is limited by HZ.
The current implementation for timeout is a simple hook on the timer
interrupt path in apic_*.c:smp_local_timer_interrupt(). Unfortunately,
this does not work when tickless is enabled: we get much less set
switches than expected on an idle system.
It looks like a solution would be to change the implementation of
timeout-based switching to use HR timers instead. Similar to what is
done for ITIMER_REAL and ITIMER_VIRTUAL.
Unless someone has a better proposal, I will experiment with this on
2.6.24-rc2.
Thanks.
--
-Stephane
next reply other threads:[~2007-11-09 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 10:44 Stephane Eranian [this message]
2007-11-09 10:59 ` conflict between tickless and perfmon2 Peter Zijlstra
2007-11-09 18:40 ` Thomas Gleixner
2007-11-09 20:17 ` Stephane Eranian
2007-11-14 16:34 ` [perfmon] " Stephane Eranian
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=20071109104438.GB18909@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perfmon2-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.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