mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiri Olsa <jolsa@redhat.com>
Subject: Re: [RFC PATCH v2 1/2] x86/perf/amd: Resolve race condition when disabling PMC
Date: Mon, 18 Mar 2019 16:20:20 +0000	[thread overview]
Message-ID: <3d176556-2424-39d1-1923-f0964ebf4e2d@amd.com> (raw)
In-Reply-To: <20190318093725.GJ6058@hirez.programming.kicks-ass.net>

On 3/18/19 4:37 AM, Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 08:40:53PM +0000, Lendacky, Thomas wrote:
>> +void amd_pmu_disable_all(void)
>> +{
>> +	unsigned long overflow_check[BITS_TO_LONGS(X86_PMC_IDX_MAX)];
>> +	struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
>> +	int idx;
>> +
>> +	bitmap_zero(overflow_check, X86_PMC_IDX_MAX);
>> +
>> +	for (idx = 0; idx < x86_pmu.num_counters; idx++) {
>> +		u64 val;
>> +
>> +		if (!test_bit(idx, cpuc->active_mask))
>> +			continue;
>> +
>> +		rdmsrl(x86_pmu_config_addr(idx), val);
>> +		if (!(val & ARCH_PERFMON_EVENTSEL_ENABLE))
>> +			continue;
>> +
>> +		val &= ~ARCH_PERFMON_EVENTSEL_ENABLE;
>> +		wrmsrl(x86_pmu_config_addr(idx), val);
>> +
>> +		/*
>> +		 * If the interrupt is enabled, this counter must be checked
>> +		 * for an overflow condition to avoid possibly changing the
>> +		 * counter value before the NMI handler runs.
>> +		 */
>> +		if (val & ARCH_PERFMON_EVENTSEL_INT)
>> +			__set_bit(idx, overflow_check);
>> +	}
> 
> I think you can ditch overflow_check and directly call
> x86_pmu_disable_all() here.
> 
>> +
>> +	/*
>> +	 * This shouldn't be called from NMI context, but add a safeguard here
>> +	 * to return, since if we're in NMI context we can't wait for an NMI
>> +	 * to reset an overflowed counter value.
>> +	 */
>> +	if (in_nmi())
>> +		return;
>> +
>> +	/*
>> +	 * Check each counter for overflow and wait for it to be reset by the
>> +	 * NMI if it has overflowed.
>> +	 */
>> +	for (idx = 0; idx < x86_pmu.num_counters; idx++) {
>> +		if (!test_bit(idx, overflow_check))
> 
> And simply iterate cpuc->active_mask again here.
> 
>> +			continue;
>> +
>> +		amd_pmu_wait_on_overflow(idx);
>> +	}
>> +}
> 
> Because, per x86_pmu_hw_config() we _always_ have EVENTSEL_INT set, even
> for !sampling events -- such that we can deal with overflow, and we
> should 'always' have EVENTSEL_ENABLE set when 'active', see
> x86_pmu_enable_all().

That would make it much simpler. I will have to rely on those assumptions,
though, which I'm fine with.

I'm traveling this week so it might be a few days before I can get the
next version out.

Thanks,
Tom

> 
> 

  reply	other threads:[~2019-03-18 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 20:40 [RFC PATCH v2 0/2] x86/perf/amd: AMD PMC counters and NMI latency Lendacky, Thomas
2019-03-15 20:40 ` [RFC PATCH v2 1/2] x86/perf/amd: Resolve race condition when disabling PMC Lendacky, Thomas
2019-03-18  9:37   ` Peter Zijlstra
2019-03-18 16:20     ` Lendacky, Thomas [this message]
2019-03-15 20:41 ` [RFC PATCH v2 2/2] x86/perf/amd: Resolve NMI latency issues when multiple PMCs are active Lendacky, Thomas
2019-03-18 10:40   ` Peter Zijlstra
2019-03-18 16:40     ` Lendacky, Thomas

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=3d176556-2424-39d1-1923-f0964ebf4e2d@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®