Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Madhavan Srinivasan writes: > On Wednesday 19 April 2017 10:20 AM, Michael Ellerman wrote: >> It also occurred to me that we don't actually have to redefine the whole >> union, it's only the bitfields that matter, so we could reduce the diff >> to: >> >> diff --git

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Madhavan Srinivasan writes: > On Wednesday 19 April 2017 10:20 AM, Michael Ellerman wrote: >> It also occurred to me that we don't actually have to redefine the whole >> union, it's only the bitfields that matter, so we could reduce the diff >> to: >> >> diff --git

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Wednesday 19 April 2017 10:20 AM, Michael Ellerman wrote: Peter Zijlstra writes: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Wednesday 19 April 2017 10:20 AM, Michael Ellerman wrote: Peter Zijlstra writes: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the ->val field and accessed via the bitmap fields. For

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Peter Zijlstra writes: > On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: >> From: Sukadev Bhattiprolu >> >> perf_mem_data_src is an union that is initialized via the ->val field >> and accessed via the bitmap fields. For

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Peter Zijlstra writes: > On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: >> From: Sukadev Bhattiprolu >> >> 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 (Which is

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Thursday 13 April 2017 06:08 PM, Peter Zijlstra wrote: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the ->val field and accessed via the bitmap fields. For

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Thursday 13 April 2017 06:08 PM, Peter Zijlstra wrote: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu 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

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Thursday 13 April 2017 06:53 PM, Michael Ellerman wrote: Peter Zijlstra writes: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Thursday 13 April 2017 06:53 PM, Michael Ellerman wrote: Peter Zijlstra writes: On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the ->val field and accessed via the bitmap fields. For

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Peter Zijlstra writes: > On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: >> From: Sukadev Bhattiprolu >> >> perf_mem_data_src is an union that is initialized via the ->val field >> and accessed via the bitmap fields. For

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

Peter Zijlstra writes: > On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: >> From: Sukadev Bhattiprolu >> >> 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 (Which is

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: > From: Sukadev Bhattiprolu > > 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 (Which is broken

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: > From: Sukadev Bhattiprolu > > 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 (Which is broken now), we also need a

[PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

From: Sukadev Bhattiprolu 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 (Which is broken now), we also need a big-endian represenation of perf_mem_data_src. i.e, in a

[PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

From: Sukadev Bhattiprolu 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 (Which is broken now), we also need a big-endian represenation of perf_mem_data_src. i.e, in a big endian system, if user

[PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

From: Sukadev Bhattiprolu 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 (Which is broken now), we also need a big-endian represenation of perf_mem_data_src. i.e, in a

[PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

From: Sukadev Bhattiprolu 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 (Which is broken now), we also need a big-endian represenation of perf_mem_data_src. i.e, in a big endian system, if user