mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	ak@linux.intel.com, peterz@infradead.org, eranian@google.com,
	Paul Mackerras <paulus@samba.org>,
	dev@codyps.com, Michael Ellerman <michaele@au1.ibm.com>,
	Anshuman Khandual <khandual@linux.vnet.ibm.com>,
	hbabu@us.ibm.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 00/10] Add support for parameterized events from sysfs
Date: Mon, 22 Sep 2014 16:43:19 +0200	[thread overview]
Message-ID: <20140922144318.GG18187@krava.brq.redhat.com> (raw)
In-Reply-To: <1410979923-7722-1-git-send-email-sukadev@linux.vnet.ibm.com>

On Wed, Sep 17, 2014 at 11:51:53AM -0700, Sukadev Bhattiprolu wrote:

SNIP

> 
> 	This means that when provided as an event, a value for
> 	phys_processor_idx must also be supplied. For example:
> 
> 	  perf stat -e 'hv_gpci/dtbp_ptitc,phys_processor_idx=0x2/' ...
> 
> Changelog[v3]
> 	- [Jiri Olsa] Changed the event parameters are specified. If
> 	  event file specifes 'param=val' make the usage 'param=123'
> 	  rather than 'val=123'. (patch 1,2/10)
> 	- Shortened event names using "PHYS" and "VCPU" (patch 4/10)
> 	- Print help message if invalid parameter is specified or required
> 	  parameter is missing.
> 	- Moved 3 patches that are unrelated to parametrized events into
> 	  a separate patchset.
> 	- Reordered patches so code changes come first.

hi,
Could you please rebase to latest acme/perf/core?
There were some changes in util/pmu.c conflicting with yours..

thanks,
jirka

      parent reply	other threads:[~2014-09-22 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 18:51 Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 01/10] tools/perf: support parsing parameterized events Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 02/10] tools/perf: extend format_alias() to include event parameters Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 03/10] perf: provide sysfs_show for struct perf_pmu_events_attr Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 04/10] powerpc/perf/hv-24x7: parse catalog and populate sysfs with events Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 05/10] perf: add PMU_EVENT_ATTR_STRING() helper Sukadev Bhattiprolu
2014-09-17 18:51 ` [PATCH v3 06/10] powerpc/perf/{hv-gpci,hv-common}: generate requests with counters annotated Sukadev Bhattiprolu
2014-09-17 18:52 ` [PATCH v3 07/10] powerpc/perf/hv-gpci: add the remaining gpci requests Sukadev Bhattiprolu
2014-09-17 18:52 ` [PATCH v3 08/10] perf Documentation: add event parameters Sukadev Bhattiprolu
2014-09-17 18:52 ` [PATCH v3 09/10] tools/perf: Document parameterized and symbolic events Sukadev Bhattiprolu
2014-09-17 18:52 ` [PATCH v3 10/10] powerpc/perf/hv-24x7: Document sysfs event description entries Sukadev Bhattiprolu
2014-09-22 14:43 ` Jiri Olsa [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=20140922144318.GG18187@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=dev@codyps.com \
    --cc=eranian@google.com \
    --cc=hbabu@us.ibm.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michaele@au1.ibm.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=sukadev@linux.vnet.ibm.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
all inboxes | Powered by JetHome®