linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Cc: Thomas Richter <tmricht@linux.vnet.ibm.com>,
	linux-s390@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf: correct precise_ip level for s390
Date: Thu, 8 Jun 2017 11:40:02 -0300	[thread overview]
Message-ID: <20170608144002.GJ6949@kernel.org> (raw)
In-Reply-To: <20170608142915.GC4444@linux.vnet.ibm.com>

Em Thu, Jun 08, 2017 at 04:29:15PM +0200, Hendrik Brueckner escreveu:
> On Thu, Jun 08, 2017 at 11:05:32AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Jun 08, 2017 at 10:40:44AM +0200, Thomas Richter escreveu:
> > > Fix this by changing function perf_evsel__new_cycles(). It is called
> > > very early in the event setup. Delay the determination of
> > > the value of precise_ip until the context is known. This is the case
> > > when perf_evsel__config() is called.
> > > Function perf_evsel__new_cycles() just marks precise_ip to be
> > > determined later.

> > > Also change the modifier to 'P' for maximum detected precise level.

> > This "Also" usually indicates that you are folding two changes into one
> > patch, please break it into two, and also send it to the perf
 
> That's usually right.  Except for the change below.  The
> perf_evsel__new_cycles() function constructs a perf event selection.
> The construction includes setting evsel->precise_max and specifying
> the event name string.  To keep setting precise_max and the event name
> in sync, the :P modifier must be set.  This should be part of the same
> commit and not split into two.

Ack, you're right, I'm testing this now, thanks for the patch!

- Arnaldo

      reply	other threads:[~2017-06-08 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08  8:40 [PATCH] perf: correct precise_ip level for s390 Thomas Richter
2017-06-08 14:05 ` Arnaldo Carvalho de Melo
2017-06-08 14:29   ` Hendrik Brueckner
2017-06-08 14:40     ` Arnaldo Carvalho de Melo [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=20170608144002.GJ6949@kernel.org \
    --to=acme@kernel.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=tmricht@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;
as well as URLs for NNTP newsgroup(s).