From: Jiri Olsa <jolsa@redhat.com>
To: Kan Liang <kan.liang@intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, a.p.zijlstra@chello.nl,
luto@kernel.org, mingo@redhat.com, eranian@google.com,
ak@linux.intel.com, mark.rutland@arm.com,
adrian.hunter@intel.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 1/7] perf,tools: introduce generic FEAT for CPU attributes
Date: Thu, 27 Aug 2015 20:10:32 +0200 [thread overview]
Message-ID: <20150827181032.GA15010@krava.redhat.com> (raw)
In-Reply-To: <1440494288-20448-2-git-send-email-kan.liang@intel.com>
On Tue, Aug 25, 2015 at 05:18:02AM -0400, Kan Liang wrote:
SNIP
> @@ -66,6 +67,11 @@ struct perf_header;
> int perf_file_header__read(struct perf_file_header *header,
> struct perf_header *ph, int fd);
>
> +enum perf_header_cpu_attr {
> + PERF_HEADER_CPU_MAX_FREQ = 0,
> + PERF_HEADER_CPU_ATTR_MAX,
> +};
> +
> struct perf_session_env {
> char *hostname;
> char *os_release;
> @@ -89,6 +95,12 @@ struct perf_session_env {
> char *sibling_threads;
> char *numa_nodes;
> char *pmu_mappings;
> + union {
> + u64 cpu_attr[PERF_HEADER_CPU_ATTR_MAX];
> + struct {
> + u64 freq;
should it b maxfreq ?
jirka
next prev parent reply other threads:[~2015-08-27 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:18 [PATCH V5 0/7] Freq/CPU%/CORE_BUSY% support Kan Liang
2015-08-25 9:18 ` [PATCH V5 1/7] perf,tools: introduce generic FEAT for CPU attributes Kan Liang
2015-08-27 17:54 ` Jiri Olsa
2015-08-27 18:10 ` Jiri Olsa [this message]
2015-08-25 9:18 ` [PATCH V5 2/7] perf,tools: read msr pmu type from header Kan Liang
2015-08-25 9:18 ` [PATCH V5 3/7] perf,tools: rename perf_session_env and add backpointer to evlist Kan Liang
2015-08-25 9:18 ` [PATCH V5 4/7] perf evsel: Add a backpointer to the evlist a evsel is in Kan Liang
2015-08-25 9:18 ` [PATCH V5 5/7] perf,tools: Dump per-sample freq/CPU%/CORE_BUSY% in report -D Kan Liang
2015-08-25 9:18 ` [PATCH V5 6/7] perf,tools: caculate and save freq/CPU%/CORE_BUSY% in he_stat Kan Liang
2015-08-27 18:10 ` Jiri Olsa
2015-08-25 9:18 ` [PATCH V5 7/7] perf,tools: Show freq/CPU%/CORE_BUSY% in perf report --stdio 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=20150827181032.GA15010@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.