Re: [PATCH v2 0/5] perf trace: Introduce arch-specific errno code/name mappings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Em Thu, Jan 25, 2018 at 01:30:13PM +0530, Ravi Bangoria escreveu:
> Hi Hendrik,
> 
> On 01/19/2018 02:26 PM, Hendrik Brueckner wrote:
> > Introduce an interface to perf to resolve errno codes to their names.
> > This is used by perf trace to display the errno name, for example, ENOENT,
> > for an system call.  The previous implementation used the errno_to_name()
> > function from the audit library.
> >
> > With this change, a table of errno codes and their names are created for
> > each architecture on which perf is supported (others can be easily added
> > if necessary).  The errno_to_name() function from the audit library is
> > replaced with an arch-specific one, arch_errno_to_name().
> >
> > The benefit is that perf trace does not longer have a direct dependency
> > for the audit library and the perf trace output can be displayed across
> > architectures.  For example, collect trace output on s390 and display it
> > on x86.
> 
> I haven't tested this but are you sure that we can do cross-arch perf-trace
> after this patch set?

This patch is a step in that direction
 
> Why I'm curious is because, we embed arch specific syscall table in the perf
> binary at compile time:
> 
>     $ cat tools/perf/util/syscalltbl.c
> 
>     #if defined(__x86_64__)
>     #include <asm/syscalls_64.c>
>     const int syscalltbl_native_max_id = SYSCALLTBL_x86_64_MAX_ID;
>     static const char **syscalltbl_native = syscalltbl_x86_64;
>     #elif defined(__s390x__)
>     #include <asm/syscalls_64.c>
>     const int syscalltbl_native_max_id = SYSCALLTBL_S390_64_MAX_ID;
>     static const char **syscalltbl_native = syscalltbl_s390_64;
>     #endif
> 
> If we don't have, let's say, s390 syscall table in perf compiled on x86 machine,
> we won't be able to do perf-trace across architecture. Right ?

Right.
 
> Please let me know if I'm missing anything.

You are not, we need to start testing running 'perf trace record' for
some workloads on a, say, PowerPC machine, run perf trace -i on that
file to do the beautification, copy this formatted output file + its
perf.data file, copy that to x86_64 or s/390 and try to get the same
output.

We will not, and the differences will tell us what to work on :-)

- Arnaldo
 
> Thanks,
> Ravi
> 
> P.S.: Seems I can remove libaudit dependency for syscalls on PowerPC as well.
> Will prepare patches for that very soon.

Great!
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux