All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Oleg Nesterov <oleg@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC][PATCH] perf, intel: Don't touch MSR_IA32_DEBUGCTLMSR from NMI context
Date: Wed, 12 Sep 2012 20:52:14 +0200	[thread overview]
Message-ID: <1347475934.15764.90.camel@twins> (raw)
In-Reply-To: <CABPqkBSgG3RhUH6L-XA6UK-M5dhA1FnEXUACGiiMeG69AKpctg@mail.gmail.com>

On Wed, 2012-09-12 at 20:50 +0200, Stephane Eranian wrote:

> > As for BTS, it looks like we don't throttle the thing at all, so we
> > shouldn't ever get to the asymmetric thing, right?
> No you do, in the same function:
> static void intel_pmu_disable_event(struct perf_event *event)
> {
>         struct hw_perf_event *hwc = &event->hw;
>         struct cpu_hw_events *cpuc = &__get_cpu_var(cpu_hw_events);
> 
>         if (unlikely(hwc->idx == INTEL_PMC_IDX_FIXED_BTS)) {
>                 intel_pmu_disable_bts();
>                 intel_pmu_drain_bts_buffer();
>                 return;
>         }

Right, but the main event loop in intel_pmu_handle_irq() is over the
MSR_CORE_PERF_GLOBAL_STATUS status bits, BTS is not included in those,
so we'd never end up calling x86_pmu_stop() on the associated event.

  reply	other threads:[~2012-09-12 18:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 16:22 [RFC][PATCH] perf, intel: Don't touch MSR_IA32_DEBUGCTLMSR from NMI context Peter Zijlstra
2012-09-12 16:42 ` Stephane Eranian
2012-09-12 17:37   ` Peter Zijlstra
2012-09-12 17:45     ` Peter Zijlstra
2012-09-12 18:00       ` Stephane Eranian
2012-09-12 18:17         ` Peter Zijlstra
2012-09-12 18:50           ` Stephane Eranian
2012-09-12 18:52             ` Peter Zijlstra [this message]
2012-09-12 19:00               ` Stephane Eranian
2012-09-12 17:36 ` Oleg Nesterov
2012-09-12 17:41   ` Peter Zijlstra
2012-09-13 10:23 ` Peter Zijlstra
2012-09-13 11:49   ` Stephane Eranian
2012-09-13 12:11     ` Peter Zijlstra

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=1347475934.15764.90.camel@twins \
    --to=peterz@infradead.org \
    --cc=bigeasy@linutronix.de \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.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.