mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	"acme@kernel.org" <acme@kernel.org>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC V5 2/4] perf,tool: per-event time support
Date: Tue, 21 Jul 2015 16:59:45 +0200	[thread overview]
Message-ID: <20150721145945.GC21171@krava.brq.redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F0770188F94B@SHSMSX103.ccr.corp.intel.com>

On Tue, Jul 21, 2015 at 03:39:17AM +0000, Liang, Kan wrote:

SNIP

> > +		case PERF_EVSEL__CONFIG_TERM_PERIOD:
> > +			attr->sample_period = term->val.period;
> > +		default:
> > +			break;
> > +		}
> > +	}
> > +}
> > +
> >  /*
> >   * The enable_on_exec/disabled value strategy:
> >   *
> > @@ -773,6 +789,8 @@ void perf_evsel__config(struct perf_evsel *evsel,
> > struct record_opts *opts)
> >  		attr->use_clockid = 1;
> >  		attr->clockid = opts->clockid;
> >  	}
> > +
> > +	apply_config_terms(attr, &evsel->config_terms);
> >  }
> > 
> 
> Other options/event modifier may also change the sample_period.
> E.g. sample read.
> So I think we may move it to the beginning of perf_evsel__config.

well, it's at the end to ensure we do the event specific setting
after everything else is done

if you set this together with group leader sampling for non leader
event, I guess you know what you're doing.. right?

jirka

  parent reply	other threads:[~2015-07-21 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 11:30 [PATCH RFC V5 0/4] per event callgrap and " kan.liang
2015-07-17 11:30 ` [PATCH RFC V5 1/4] perf,tools: introduce callgraph_set for callgraph option kan.liang
2015-07-17 11:30 ` [PATCH RFC V5 2/4] perf,tool: per-event time support kan.liang
2015-07-18 12:45   ` Jiri Olsa
2015-07-19  3:21     ` Namhyung Kim
2015-07-19 19:13       ` Jiri Olsa
2015-07-20 15:04         ` Liang, Kan
2015-07-20 17:40           ` Jiri Olsa
2015-07-21  3:39             ` Liang, Kan
2015-07-21 14:45               ` Namhyung Kim
2015-07-21 14:56                 ` Jiri Olsa
2015-07-21 14:59               ` Jiri Olsa [this message]
2015-07-17 11:30 ` [PATCH RFC V5 3/4] perf,tool: per-event callgrap support kan.liang
2015-07-17 11:30 ` [PATCH RFC V5 4/4] perf,tests: Add tests to callgrap and time parse kan.liang

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=20150721145945.GC21171@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.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

Powered by JetHome