From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, acme@redhat.com, mingo@elte.hu
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v4)
Date: Fri, 16 Sep 2011 08:52:07 -0600 [thread overview]
Message-ID: <4E736297.2070604@gmail.com> (raw)
In-Reply-To: <CABPqkBRmpnMNH16_HNWWHFn8dDtTE+jRjunkLDpc30SnA8_oYA@mail.gmail.com>
On 09/16/2011 08:44 AM, Stephane Eranian wrote:
>> Sure, but all you need to know is if the file you're reading is a
>> different endian than your box, if it is swap stuff, if its not, you're
>> good.
>
> We agree on that. I am just saying the MAGIC string as it is today
> may not be enough to tell us that.
Right. I think that's why the attribute struct is used to detect
endianness and not the magic.
David
next prev parent reply other threads:[~2011-09-16 14:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 19:10 [PATCH] perf: make perf.data more self-descriptive (v4) Stephane Eranian
2011-09-08 15:27 ` David Ahern
[not found] ` <CABPqkBRKcxeTDMyVYPXU6AQEY-Hp2bnE03ebEtvjYWde2JKqoQ@mail.gmail.com>
2011-09-08 15:37 ` David Ahern
2011-09-08 15:42 ` Stephane Eranian
2011-09-12 13:45 ` David Ahern
2011-09-12 13:54 ` Stephane Eranian
2011-09-12 14:33 ` David Ahern
2011-09-12 14:40 ` Stephane Eranian
2011-09-12 14:43 ` Peter Zijlstra
2011-09-12 14:47 ` Stephane Eranian
2011-09-13 14:40 ` Arnaldo Carvalho de Melo
2011-09-16 14:35 ` Stephane Eranian
2011-09-16 14:37 ` Peter Zijlstra
2011-09-16 14:44 ` Stephane Eranian
2011-09-16 14:52 ` David Ahern [this message]
2011-09-16 14:56 ` Stephane Eranian
2011-09-16 14:50 ` David Ahern
2011-09-16 15:19 ` Peter Zijlstra
2011-09-16 15:33 ` David Ahern
2011-09-16 15:42 ` Peter Zijlstra
2011-09-16 16:34 ` 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=4E736297.2070604@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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