From: Imre Palik <imrep.amz@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org, "Palik,
Imre" <imrep@amazon.de>, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [PATCH v3] perf: honoring the architectural performance monitoring version
Date: Thu, 18 Jun 2015 16:25:17 +0200 [thread overview]
Message-ID: <5582D4CD.8000005@gmail.com> (raw)
In-Reply-To: <20150616092136.GL3644@twins.programming.kicks-ass.net>
On 06/16/15 11:21, Peter Zijlstra wrote:
> On Mon, Jun 15, 2015 at 04:22:32PM +0200, Imre Palik wrote:
>> From: "Palik, Imre" <imrep@amazon.de>
>>
>> Architectural performance monitoring version 1 doesn't support fixed
>> counters. Currently, even if a hypervisor advertises support for
>> architectural performance monitoring version 1, perf may still tries to use
>> the fixed counters, as the constraints are set up based on the CPU model.
>>
>> This patch ensures that perf honors the architectural performance
>> monitoring version returned by CPUID, and it only uses the fixed counters
>> for version two and above.
>>
>> Some of the ideas in this patch are coming from Peter Zijlstra.
>
> What's the difference from -v2? I'm not really seeing it.
>
I made the mistake of sending two different versions as v2. v3 is the same
as the second v2.
I sent this to clear up possible confusion. Sorry if it caused more of it.
prev parent reply other threads:[~2015-06-18 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 14:22 [PATCH v3] perf: honoring the architectural performance monitoring version Imre Palik
2015-06-16 9:21 ` Peter Zijlstra
2015-06-18 14:25 ` Imre Palik [this message]
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=5582D4CD.8000005@gmail.com \
--to=imrep.amz@gmail.com \
--cc=acme@kernel.org \
--cc=aliguori@amazon.com \
--cc=hpa@zytor.com \
--cc=imrep@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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 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.