From: Andi Kleen <ak@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH v3 04/19] perf, core: Add a concept of a weightened sample
Date: Wed, 28 Nov 2012 07:27:47 -0800 [thread overview]
Message-ID: <20121128152747.GH2584@tassilo.jf.intel.com> (raw)
In-Reply-To: <20121128152327.GD1038@krava.brq.redhat.com>
> > @@ -198,8 +200,9 @@ enum perf_event_read_format {
> > PERF_FORMAT_TOTAL_TIME_RUNNING = 1U << 1,
> > PERF_FORMAT_ID = 1U << 2,
> > PERF_FORMAT_GROUP = 1U << 3,
> > + PERF_FORMAT_WEIGHT = 1U << 4,
>
> what's PERF_FORMAT_WEIGHT for?
It was used in a earlier iteration, but is now obsolete. I'll remove it.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-11-28 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 12:49 [PATCH v3 00/16] perf: add memory access sampling support Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 01/19] perf, x86: Support CPU specific sysfs events Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 02/19] perf/x86: improve sysfs event mapping with event string Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 03/19] perf/x86: add flags to event constraints Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 04/19] perf, core: Add a concept of a weightened sample Stephane Eranian
2012-11-28 15:23 ` Jiri Olsa
2012-11-28 15:27 ` Andi Kleen [this message]
2012-11-21 12:49 ` [PATCH v3 05/19] perf: add minimal support for PERF_SAMPLE_WEIGHT Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 06/19] perf: add support for PERF_SAMPLE_ADDR in dump_sampple() Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 07/19] perf: add generic memory sampling interface Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 08/19] perf/x86: add memory profiling via PEBS Load Latency Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 09/19] perf/x86: export PEBS load latency threshold register to sysfs Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 10/19] perf/x86: add support for PEBS Precise Store Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 11/19] perf tools: add mem access sampling core support Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 12/19] perf report: add support for mem access profiling Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 13/19] perf record: " Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 14/19] perf tools: add new mem command for memory " Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 15/19] perf: add PERF_RECORD_MISC_MMAP_DATA to RECORD_MMAP Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 16/19] perf tools: detect data vs. text mappings Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 17/19] perf tools: Synthesize data mmap events for threads Stephane Eranian
2012-11-21 12:49 ` [PATCH v3 18/19] perf tools: Ignore ABS symbols when loading data maps Stephane Eranian
2013-01-24 18:44 ` [tip:perf/core] perf symbols: " tip-bot for Namhyung Kim
2012-11-21 12:49 ` [PATCH v3 19/19] perf tools: Fix output of symbol_daddr offset Stephane Eranian
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=20121128152747.GH2584@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.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