Re: [PATCH 7/7] perf data: Fix signess of value

2015-04-21 Thread Arnaldo Carvalho de Melo
Em Tue, Apr 21, 2015 at 10:41:55AM +0800, Wang Nan escreveu: > On 2015/4/21 5:23, Arnaldo Carvalho de Melo wrote: > > Em Sat, Apr 18, 2015 at 05:50:20PM +0200, Jiri Olsa escreveu: > >> From: Wang Nan > > There is no such word "signess", it is "signedness", fixing this up. > > Humm, it seems there

Re: [PATCH 7/7] perf data: Fix signess of value

2015-04-20 Thread Wang Nan
On 2015/4/21 5:23, Arnaldo Carvalho de Melo wrote: > Em Sat, Apr 18, 2015 at 05:50:20PM +0200, Jiri Olsa escreveu: >> From: Wang Nan >> >> When converting int values, perf first extractes it to a ulonglong, then >> feeds it to babeltrace as a signed value. For negative 32 bit values >> (for exampl

Re: [PATCH 7/7] perf data: Fix signess of value

2015-04-20 Thread Jiri Olsa
On Mon, Apr 20, 2015 at 06:23:14PM -0300, Arnaldo Carvalho de Melo wrote: > Em Sat, Apr 18, 2015 at 05:50:20PM +0200, Jiri Olsa escreveu: > > From: Wang Nan > > > > When converting int values, perf first extractes it to a ulonglong, then > > feeds it to babeltrace as a signed value. For negative

Re: [PATCH 7/7] perf data: Fix signess of value

2015-04-20 Thread Arnaldo Carvalho de Melo
Em Sat, Apr 18, 2015 at 05:50:20PM +0200, Jiri Olsa escreveu: > From: Wang Nan > > When converting int values, perf first extractes it to a ulonglong, then > feeds it to babeltrace as a signed value. For negative 32 bit values > (for example, return values of failed syscalls), the extracted data

[PATCH 7/7] perf data: Fix signess of value

2015-04-18 Thread Jiri Olsa
From: Wang Nan When converting int values, perf first extractes it to a ulonglong, then feeds it to babeltrace as a signed value. For negative 32 bit values (for example, return values of failed syscalls), the extracted data should be something like 0xfffe (-2). It becomes a large int64 value