Re: [v2] powerpc/vphn: fix endian issue in NUMA device node code

2014-10-14 Thread Michael Ellerman
On Fri, 2014-10-10 at 08:20:33 UTC, Greg Kurz wrote: > On Tue, 7 Oct 2014 20:28:23 +1100 (EST) > Michael Ellerman wrote: > > > On Fri, 2014-03-10 at 09:13:17 UTC, Greg Kurz wrote: > > > The associativity domain numbers are obtained from the hypervisor through > > > registers and written into mem

Re: [v2] powerpc/vphn: fix endian issue in NUMA device node code

2014-10-10 Thread Greg Kurz
On Tue, 7 Oct 2014 20:28:23 +1100 (EST) Michael Ellerman wrote: > On Fri, 2014-03-10 at 09:13:17 UTC, Greg Kurz wrote: > > The associativity domain numbers are obtained from the hypervisor through > > registers and written into memory by the guest: the packed array passed to > > vphn_unpack_asso

Re: [v2] powerpc/vphn: fix endian issue in NUMA device node code

2014-10-07 Thread Michael Ellerman
On Fri, 2014-03-10 at 09:13:17 UTC, Greg Kurz wrote: > The associativity domain numbers are obtained from the hypervisor through > registers and written into memory by the guest: the packed array passed to > vphn_unpack_associativity() is then native-endian, unlike what was assumed > in the followi

Re: [PATCH v2] powerpc/vphn: fix endian issue in NUMA device node code

2014-10-06 Thread Nishanth Aravamudan
On 03.10.2014 [11:13:17 +0200], Greg Kurz wrote: > The associativity domain numbers are obtained from the hypervisor through > registers and written into memory by the guest: the packed array passed to > vphn_unpack_associativity() is then native-endian, unlike what was assumed > in the following c

[PATCH v2] powerpc/vphn: fix endian issue in NUMA device node code

2014-10-03 Thread Greg Kurz
The associativity domain numbers are obtained from the hypervisor through registers and written into memory by the guest: the packed array passed to vphn_unpack_associativity() is then native-endian, unlike what was assumed in the following commit: commit b08a2a12e44eaec5024b2b969f4fcb98169d1ca3 A