public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@elte.hu, ak@linux.intel.com, acme@redhat.com,
	jolsa@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH 2/2] perf: add new perf uncore command
Date: Fri, 01 Feb 2013 17:45:15 +0900	[thread overview]
Message-ID: <874nhwtobo.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1359640479-5289-3-git-send-email-eranian@google.com> (Stephane Eranian's message of "Thu, 31 Jan 2013 14:54:39 +0100")

Just a nitpick.  But maybe I shows it can be done with perf stat. :)


On Thu, 31 Jan 2013 14:54:39 +0100, Stephane Eranian wrote:
> diff --git a/tools/perf/builtin-uncore.c b/tools/perf/builtin-uncore.c
> new file mode 100644
> index 0000000..b050712
> --- /dev/null
> +++ b/tools/perf/builtin-uncore.c
> @@ -0,0 +1,739 @@
> +/*
> + * builtin-stat.c

s/stat/uncore/ :)

> + *
> + * Builtin stat command: Give a precise performance counters summary

Ditto.

Thanks,
Namhyung


  reply	other threads:[~2013-02-01  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 13:54 [PATCH 0/2] perf: add new uncore command Stephane Eranian
2013-01-31 13:54 ` [PATCH 1/2] perf tools: add cpu_map__get_socket() Stephane Eranian
2013-01-31 13:54 ` [PATCH 2/2] perf: add new perf uncore command Stephane Eranian
2013-02-01  8:45   ` Namhyung Kim [this message]
2013-01-31 14:21 ` [PATCH 0/2] perf: add new " Ingo Molnar
2013-01-31 14:32   ` Stephane Eranian
2013-02-01  8:42 ` Namhyung Kim
2013-02-02  1:35   ` Andi Kleen
2013-02-04 13:33     ` Jiri Olsa

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=874nhwtobo.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.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