| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20120504175940.GC29365@infradead.org> Date: Fri, 4 May 2012 14:59:40 -0300 From: Arnaldo Carvalho de Melo <acme@...hat.com> To: David Ahern <dsahern@...il.com> Cc: Jiri Olsa <jolsa@...hat.com>, a.p.zijlstra@...llo.nl, mingo@...e.hu, paulus@...ba.org, cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com, linux-kernel@...r.kernel.org Subject: Re: [PATCHv2 0/4] perf, tool: Fix endian issues Em Fri, May 04, 2012 at 11:40:17AM -0600, David Ahern escreveu: > On 5/4/12 11:11 AM, Jiri Olsa wrote: > >hi, > >sending fixies to properly handle perf.data endians. > > > >v2 changes: > > - added patches 3 and 4 to handle sample_id_all header endianity > > > >Attached patches: > > 1/4 perf, tool: Handle different endians properly during symbol load > > 2/4 perf, tool: Carry perf_event_attr bitfield throught different endians > > 3/4 perf, tool: Handle endianity swap on sample_id_all header data > > 4/4 perf, tool: Fix 32 bit values endianity swap for sample_id_all header > > Have you tested these patches by collecting data on PPC (or other > big endian) and analyzing on Intel x86 and vice versa? I think so, but indeed it is good practice to show the sequence made to test the changes, with sample, short command output before and after. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists