lkml.org 
[lkml]   [2014]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFD] perf syscall error handling
On Fri, 31 Oct 2014, Stephane Eranian wrote:

> On Fri, Oct 31, 2014 at 1:28 PM, Matt Fleming <matt@console-pimps.org> wrote:
> >
> > I guess we'd run into a problem if userspace doesn't want to just print
> > the kernel string but instead wants to parse it in some fashion.

If the string interface went in it would be a help when debugging
perf_event_open().

Support would probably get added to PAPI, but PAPI has its own error
reporting issues and it's not always easy to pass a string the whole way
back to the user.

Also with PAPI many of the users reporting obscure perf_event_open()
problems are often running 2.6.32-vendor-patched kernels, so sadly it will
be years before any improved error handling filters down to many of the
users.

This proposal also doesn't help with other weird failure modes in the
interface, the most annoying of which is the watchdog stealing a counter
so event groups perf_event_open() and start just fine but fail at read
time.

> > That may or may not be a problem in practice, Vince can probably comment
> > on that. I'm just thinking along the lines of making the perf syscall
> > interface as useful as possible for tools other than tools/perf.
> >
> Maybe I missed something in the earlier thread, but I am trying to understand
> why perf_event_open() would need such extended error retrieval system when
> no other syscall does.

well perf_event_open() is so complex, with it's 40+ different parameters.
Having a wrong value in any one of those (or one of the combinations of
those) can trigger EINVAL and it's not clear where the issue is.
I think other system calls tend to have slighly more straightforward
interfaces.

Vince


\
 
 \ /
  Last update: 2014-11-01 07:01    [W:0.997 / U:0.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site