mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"acme@kernel.org" <acme@kernel.org>,
	"eranian@google.com" <eranian@google.com>,
	"ak@linux.intel.com" <ak@linux.intel.com>
Subject: RE: [PATCH V3 1/5] perf/x86/intel/uncore: customized pmu event read for client IMC uncore
Date: Thu, 2 Nov 2017 14:54:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1711021453550.2090@nanos> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077537DCA04@SHSMSX103.ccr.corp.intel.com>

On Thu, 2 Nov 2017, Liang, Kan wrote:
> > On Tue, 24 Oct 2017, kan.liang@intel.com wrote:
> > > -	if (event->hw.idx >= UNCORE_PMC_IDX_FIXED)
> > > +	if (event->hw.idx == UNCORE_PMC_IDX_FIXED)
> > >  		shift = 64 - uncore_fixed_ctr_bits(box);
> > >  	else
> > >  		shift = 64 - uncore_perf_ctr_bits(box); diff --git
> > > a/arch/x86/events/intel/uncore_snb.c
> > > b/arch/x86/events/intel/uncore_snb.c
> > > index db1127c..9d5cd3f 100644
> > > --- a/arch/x86/events/intel/uncore_snb.c
> > > +++ b/arch/x86/events/intel/uncore_snb.c
> > > @@ -498,6 +498,30 @@ static void snb_uncore_imc_event_del(struct
> > perf_event *event, int flags)
> > >  	snb_uncore_imc_event_stop(event, PERF_EF_UPDATE);  }
> > >
> > > +static void snb_uncore_imc_event_read(struct perf_event *event) {
> > > +	struct intel_uncore_box *box = uncore_event_to_box(event);
> > > +	u64 prev_count, new_count, delta;
> > > +	int shift;
> > > +
> > > +	if (event->hw.idx >= UNCORE_PMC_IDX_FIXED)
> > 
> > And this needs to be >= because?
> 
> Patch 5/5 will clean up the client IMC uncore.
> Before that, we still need it to make client IMC uncore work.
> 
> This patch isolates the >= case for client IMC uncore.

Fair enough. A comment to that effect (even when removed later) would have
avoided that question.

Thanks,

	tglx

  reply	other threads:[~2017-11-02 13:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 11:05 kan.liang
2017-10-24 11:05 ` [PATCH V3 2/5] perf/x86/intel/uncore: add infrastructure for free running counter kan.liang
2017-10-24 11:05 ` [PATCH V3 3/5] perf/x86/intel/uncore: SKX support for IIO " kan.liang
2017-10-24 11:05 ` [PATCH V3 4/5] perf/x86/intel/uncore: expose pmu counter operation functions kan.liang
2017-10-24 11:05 ` [PATCH V3 5/5] perf/x86/intel/uncore: clean up client IMC uncore kan.liang
2017-11-02 13:46 ` [PATCH V3 1/5] perf/x86/intel/uncore: customized pmu event read for " Thomas Gleixner
2017-11-02 13:51   ` Liang, Kan
2017-11-02 13:54     ` Thomas Gleixner [this message]
2017-11-02 13:59       ` Thomas Gleixner
2017-11-02 14:06         ` Liang, Kan
2017-11-02 14:11           ` Thomas Gleixner
2017-11-02 14:16             ` Thomas Gleixner
2017-11-02 14:27               ` Liang, Kan
2017-11-02 14:56                 ` Thomas Gleixner
2017-11-02 15:10                   ` Liang, Kan
2017-11-02 15:39                     ` Thomas Gleixner
2017-11-02 15:57                       ` Liang, Kan

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=alpine.DEB.2.20.1711021453550.2090@nanos \
    --to=tglx@linutronix.de \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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®