From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v1 2/9] PERFv1 6
Date: Tue, 5 Feb 2019 08:37:36 -0800 [thread overview]
Message-ID: <20190205163736.GG31598@tassilo.jf.intel.com> (raw)
In-Reply-To: <20190205144627.GU17528@hirez.programming.kicks-ass.net>
On Tue, Feb 05, 2019 at 03:46:27PM +0100, speck for Peter Zijlstra wrote:
> On Mon, Feb 04, 2019 at 05:14:03PM -0800, speck for Andi Kleen wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> > Subject: x86/pmu/intel: Add flags argument to x86_pmu::disable
> >
> > Add a flags argument to pass the HEF_* flags down to x86_pmu::disable.
> > This will be used in a followon patch to avoid some redundant
> > MSR writes when reprograming counters for updates.
>
> Neither this nor that follow up patch explains what disable needs these
> flags for. Now I could probably reverse engineer it; but you really
> should know better by now.
Just to know that the counter is getting reused, so can skip
the extra MSR disable. I'll mention it.
-Andi
next prev parent reply other threads:[~2019-02-05 16:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 1:14 [MODERATED] [PATCH v1 0/9] PERFv1 0 Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 1/9] PERFv1 7 Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 2/9] PERFv1 6 Andi Kleen
2019-02-05 14:46 ` [MODERATED] " Peter Zijlstra
2019-02-05 16:37 ` Andi Kleen [this message]
2019-02-05 1:14 ` [MODERATED] [PATCH v1 3/9] PERFv1 9 Andi Kleen
2019-02-05 13:58 ` [MODERATED] " Peter Zijlstra
2019-02-05 1:14 ` [MODERATED] [PATCH v1 4/9] PERFv1 2 Andi Kleen
2019-02-05 14:51 ` [MODERATED] " Peter Zijlstra
2019-02-05 16:35 ` Andi Kleen
2019-02-05 16:53 ` Peter Zijlstra
2019-02-05 15:16 ` Peter Zijlstra
2019-02-05 16:52 ` Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 5/9] PERFv1 8 Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 6/9] PERFv1 5 Andi Kleen
2019-02-05 15:26 ` [MODERATED] " Peter Zijlstra
2019-02-05 16:45 ` Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 7/9] PERFv1 1 Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 8/9] PERFv1 4 Andi Kleen
2019-02-05 1:14 ` [MODERATED] [PATCH v1 9/9] PERFv1 3 Andi Kleen
2019-02-05 15:28 ` [MODERATED] " Peter Zijlstra
2019-02-05 16:48 ` Andi Kleen
2019-02-05 17:13 ` Peter Zijlstra
2019-02-05 17:26 ` Andi Kleen
2019-02-05 18:30 ` Peter Zijlstra
2019-02-05 14:03 ` [MODERATED] Re: [PATCH v1 0/9] PERFv1 0 Greg KH
2019-02-05 16:36 ` Andi Kleen
2019-02-05 18:20 ` Greg KH
2019-02-06 1:16 ` Andi Kleen
2019-02-05 15:32 ` 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=20190205163736.GG31598@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=speck@linutronix.de \
/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.