public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@redhat.com>,
	Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Michael Petlan <mpetlan@redhat.com>
Subject: Re: [RFC] perf/x86/intel/uncore: pmu->type->single_fixed question
Date: Thu, 1 Dec 2016 17:37:55 +0100	[thread overview]
Message-ID: <20161201163755.GM3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07750CA4D86@SHSMSX103.ccr.corp.intel.com>

On Thu, Dec 01, 2016 at 04:34:43PM +0000, Liang, Kan wrote:
> 
> > 
> > "Liang, Kan" <kan.liang@intel.com> writes:
> > >
> > > Maybe we should create a clocktick box for client uncore to fix it.
> > 
> > That would break all the user space code that uses the existing format.
> > 
> OK.
> If so, I think we should remove the non-exist events for non-first boxes.
> 
> What do you think about the patch as below?
> 
> Andi? Jirka?

Urgh, more lines for ugly :-(

I really would prefer to move the thing to its own PMU.

  reply	other threads:[~2016-12-01 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 10:51 [RFC] perf/x86/intel/uncore: pmu->type->single_fixed question Jiri Olsa
2016-11-30 14:45 ` Liang, Kan
2016-11-30 17:52   ` Andi Kleen
2016-12-01 16:34     ` Liang, Kan
2016-12-01 16:37       ` Peter Zijlstra [this message]
2016-12-12 14:49         ` Liang, Kan
2016-12-14 11:33           ` Jiri Olsa
2016-12-20 18:05             ` Liang, Kan
2017-01-16 13:15               ` Liang, Kan
2016-11-30 15:27 ` Liang, Kan
2016-11-30 15:38   ` Jiri Olsa

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=20161201163755.GM3092@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox