[lkml]   [2008]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bug #11954] sysprof tracer ABI regression in 2.6.28rc1
Ingo Molnar <> writes:

> * Soeren Sandmann <> wrote:
> > There are no ABI guarantees for the sysprof tracer at this point,
> > given that it is in debugfs [...]
> to avoid situations like this, it would be nice to print out the
> format string itself in the trace header, in printf format string
> style. That way if there's a trivial expansion in trace format, it can
> be detected (and even followed) by user-space - without some ugly
> version based API.

It's not clear to me that sysprof userspace could realistically do
runtime detection. It would require (a) using sscanf() to parse the
output and (b) that only the types changed, not the actual content or
ordering. (a) is likely a non-starter performance-wise (the first
version actually did this and it was too slow), and (b) means there
are strict limits to what could be changed anyway.


 \ /
  Last update: 2008-11-18 13:21    [W:0.082 / U:0.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site