[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170306112228.GZ6515@twins.programming.kicks-ass.net>
Date: Mon, 6 Mar 2017 12:22:28 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Madhavan Srinivasan <maddy@...ux.vnet.ibm.com>
Cc: mpe@...erman.id.au, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org,
Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Wang Nan <wangnan0@...wei.com>,
Alexei Starovoitov <ast@...nel.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH v2 1/6] powerpc/perf: Define big-endian version of
perf_mem_data_src
On Mon, Mar 06, 2017 at 04:13:08PM +0530, Madhavan Srinivasan wrote:
> From: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
>
> perf_mem_data_src is an union that is initialized via the ->val field
> and accessed via the bitmap fields. For this to work on big endian
> platforms, we also need a big-endian represenation of perf_mem_data_src.
Doesn't this break interpreting the data on a different endian machine?
Powered by blists - more mailing lists