All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [Question] perf header: Why the HEADER_EVENT_DESC is needed?
Date: Sat, 21 Jul 2012 20:11:24 +0900	[thread overview]
Message-ID: <87txx1qsgz.fsf@kernel.org> (raw)

Hi Stephane,

I wonder why we need to save the event descriptions in the feature area
of file header. Since the perf_event_attr, its ids and the event name
are already saved in the header, it seems a duplicate work to do that.
For printing the information, we might reuse those info or evlist
directly IMHO.

Am I missing something?

Thanks,
Namhyung

             reply	other threads:[~2012-07-21 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21 11:11 Namhyung Kim [this message]
2012-07-21 17:16 ` [Question] perf header: Why the HEADER_EVENT_DESC is needed? 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=87txx1qsgz.fsf@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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 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.