From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, ak@linux.intel.com,
acme@redhat.com, jolsa@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH v5 1/2] perf: use hrtimer for event multiplexing
Date: Mon, 25 Mar 2013 12:13:34 +0100 [thread overview]
Message-ID: <1364210014.5053.2.camel@laptop> (raw)
In-Reply-To: <1363949499-3728-2-git-send-email-eranian@google.com>
On Fri, 2013-03-22 at 11:51 +0100, Stephane Eranian wrote:
> +#define PERF_CPU_HRTIMER (1000 / HZ)
> +static enum hrtimer_restart perf_cpu_hrtimer_handler(struct hrtimer
> *hr)
> +{
> + struct perf_cpu_context *cpuctx;
> + enum hrtimer_restart ret = HRTIMER_NORESTART;
> + unsigned long flags;
> + int rotations = 0;
> +
> + cpuctx = container_of(hr, struct perf_cpu_context, hrtimer);
> +
> + local_irq_save(flags);
> +
> + rotations = perf_rotate_context(cpuctx);
> +
> + local_irq_restore(flags);
IIRC hrtimer callbacks are always ran with interrupts disabled.. not a
big deal though. I'll continue reading.
next prev parent reply other threads:[~2013-03-25 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:51 [PATCH v5 0/2] perf: use hrtimer for event multiplexing Stephane Eranian
2013-03-22 10:51 ` [PATCH v5 1/2] " Stephane Eranian
2013-03-25 11:13 ` Peter Zijlstra [this message]
2013-03-25 17:58 ` Stephane Eranian
2013-03-22 10:51 ` [PATCH v5 2/2] perf: add sysfs entry to adjust multiplexing interval per PMU Stephane Eranian
2013-03-25 11:43 ` Peter Zijlstra
2013-03-25 12:15 ` Stephane Eranian
2013-03-22 13:54 ` [PATCH v5 0/2] perf: use hrtimer for event multiplexing Frederic Weisbecker
2013-03-25 12:08 ` Peter Zijlstra
2013-03-25 12:21 ` Frederic Weisbecker
2013-03-22 17:33 ` Andi Kleen
2013-03-22 17:36 ` 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=1364210014.5053.2.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.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.