From: Robert Richter <robert.richter@amd.com>
To: eranian@google.com
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, paulus@samba.org, fweisbec@gmail.com,
perfmon2-devel@lists.sf.net, eranian@gmail.com
Subject: Re: [PATCH] perf_events: add sampling period randomization support
Date: Tue, 2 Mar 2010 11:53:14 +0100 [thread overview]
Message-ID: <20100302105314.GF13205@erda.amd.com> (raw)
In-Reply-To: <1267510029-19750-1-git-send-email-eranian@google.com>
On 01.03.10 22:07:09, eranian@google.com wrote:
> This patch adds support for randomizing the sampling period.
> Randomization is very useful to mitigate the bias that exists
> with sampling. The random number generator does not need to
> be sophisticated. This patch uses the builtin random32()
> generator.
>
> The user activates randomization by setting the perf_event_attr.random
> field to 1 and by passing a bitmask to control the range of variation
> above the base period. Period will vary from period to period & mask.
> Note that randomization is not available when a target interrupt rate
> (freq) is enabled.
Instead of providing a mask I would prefer to either use a bit width
parameter there the mask can be calculated from or to specify a range
the period may vary.
>
> The last used period can be collected using the PERF_SAMPLE_PERIOD flag
> in sample_type.
>
> The patch has been tested on X86. There is also code for PowerPC but
> I could not test it.
>
> Signed-off-by: Stephane Eranian <eranian@google.com>
>
> --
> arch/powerpc/kernel/perf_event.c | 3 +++
> arch/x86/kernel/cpu/perf_event.c | 2 ++
> arch/x86/kernel/cpu/perf_event_intel.c | 4 ++++
I agree with Peter, I also don't see the need to touch arch specific
code.
> include/linux/perf_event.h | 7 +++++--
> kernel/perf_event.c | 24 ++++++++++++++++++++++++
> 5 files changed, 38 insertions(+), 2 deletions(-)
>
[...]
> +void perf_randomize_event_period(struct perf_event *event)
> +{
> + u64 new_seed;
> + u64 mask = event->attr.random_mask;
> +
> + event->hw.last_period = event->hw.sample_period;
> +
> + new_seed = random32();
> +
> + if (unlikely(mask >> 32))
> + new_seed |= (u64)random32() << 32;
> +
> + event->hw.sample_period = event->attr.sample_period + (new_seed & mask);
Only adding the random value will lead to longer sample periods on
average. To compensate this you could calculate something like:
event->hw.sample_period = event->attr.sample_period + (new_seed & mask) - (mask >> 1);
Or, the offset is already in sample_period.
Also a range check for sample_period is necessary to avoid over- or
underflows.
-Robert
> +}
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2010-03-02 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 6:07 [PATCH] perf_events: add sampling period randomization support eranian
2010-03-02 6:20 ` David Miller
2010-03-02 8:21 ` Peter Zijlstra
2010-03-02 10:53 ` Robert Richter [this message]
2010-03-02 11:41 ` Peter Zijlstra
2010-03-02 14:18 ` Robert Richter
2010-03-02 13:10 ` Frederic Weisbecker
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=20100302105314.GF13205@erda.amd.com \
--to=robert.richter@amd.com \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=peterz@infradead.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 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.