From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] tools lib traceevent: Add page_size field to pevent
Date: Fri, 12 Apr 2013 22:27:21 -0300 [thread overview]
Message-ID: <20130413012721.GA12924@ghostprotocols.net> (raw)
In-Reply-To: <1365815846.1769.11.camel@leonhard>
Em Sat, Apr 13, 2013 at 10:17:26AM +0900, Namhyung Kim escreveu:
> > I just want to know more about this patch before I ack it.
>
> The page size of traced system can be different than current system's
> because the recorded data file might be analyzed in a different machine.
> In this case we should use original page size of traced system when
> accessing the data file, so this information needs to be saved.
Excellent explanation! So good it deserves being in the changelog
commit!
8-)
- Arnaldo
next prev parent reply other threads:[~2013-04-13 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 12:04 [PATCH 1/6] tools lib traceevent: Remove unused install targets Namhyung Kim
2013-04-11 12:04 ` [PATCH 2/6] tools lib traceevent: Get rid of unused gui target Namhyung Kim
2013-04-11 12:04 ` [PATCH 3/6] tools lib traceevent: Add const qualifier to string arguments Namhyung Kim
2013-04-11 12:04 ` [PATCH 4/6] tools lib traceevent: Add trace_seq_reset() Namhyung Kim
2013-04-11 12:04 ` [PATCH 5/6] tools lib traceevent: Add page_size field to pevent Namhyung Kim
2013-04-11 14:39 ` Steven Rostedt
2013-04-11 14:40 ` Steven Rostedt
2013-04-13 1:17 ` Namhyung Kim
2013-04-13 1:26 ` Steven Rostedt
2013-04-13 2:08 ` Namhyung Kim
2013-04-13 2:14 ` Steven Rostedt
2013-04-13 2:40 ` Namhyung Kim
2013-04-13 1:27 ` Arnaldo Carvalho de Melo [this message]
2013-04-11 12:04 ` [PATCH 6/6] tools lib traceevent: Port kbuffer parser routines Namhyung Kim
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=20130413012721.GA12924@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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.