All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/4] perf header: Save and reuse feature information in header (v3)
Date: Thu, 20 Sep 2012 22:55:14 +0900	[thread overview]
Message-ID: <1348149314.1510.4.camel@leonhard> (raw)
In-Reply-To: <505B1DB5.1030304@gmail.com>

Hi David,

2012-09-20 (목), 07:44 -0600, David Ahern:
> On 9/19/12 11:36 PM, Namhyung Kim wrote:
> > Currently the perf header information is used only at initial setup
> > time and discarded.  If it's saved we could reuse the information for
> > various purpose in the future.
> 
> When this gets settled can you update builtin-kvm too? The kvm-events 
> patch too adds a perf_file_section__read_feature() function for 
> extracting cpuid from the header.

Will look at it too.

Thanks,
Namhyung



      reply	other threads:[~2012-09-20 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  5:36 [PATCH 0/4] perf header: Save and reuse feature information in header (v3) Namhyung Kim
2012-09-20  5:36 ` [PATCH 1/4] perf header: Add struct perf_header_info Namhyung Kim
2012-09-20 11:43   ` Arnaldo Carvalho de Melo
2012-09-20 13:53     ` Namhyung Kim
2012-09-20  5:36 ` [PATCH 2/4] perf header: Add ->process callbacks to most of features Namhyung Kim
2012-09-20  5:36 ` [PATCH 3/4] perf header: Use pre-processed header info when printing Namhyung Kim
2012-09-20  5:36 ` [PATCH 4/4] perf header: Remove unused @feat arg from ->process callback Namhyung Kim
2012-09-20 13:44 ` [PATCH 0/4] perf header: Save and reuse feature information in header (v3) David Ahern
2012-09-20 13:55   ` Namhyung Kim [this message]

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=1348149314.1510.4.camel@leonhard \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.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.