Re: tracepoint maintainance models

[Frank Ch. Eigler]

Hi -

alan worte:
> > > [...] So its L1 misses more register reloads and the like. Sounds
> > > more and more like wasted clock cycles for debug. [...]
> > 
> > But it's not just "for debug"!  It is for system administrators,
> > end-users, developers.
> 
> It is for debug. System administrators and developers also do debug,
> they may just use different tools. 

Then you're using the term so broadly as to lose specific meaning.

> The percentage of schedule() calls executed across every Linux box
> on the planet where debug is enabled is so close to nil it's
> noise. [...]

Unless one's worried about planetary-scale energy use, I see no point
in multiplying overheads by "every box on the planet".

> > Indeed, there will be some non-zero execution-time cost.  We must be
> > willing to pay *something* in order to enable this functionality.
> 
> There is an implementation which requires no penalty is paid. Create a
> new elf section which contains something like [...]

Unfortunately, cases in which this sort of out-of-band markup would be
sufficient are pretty much those exact same cases where it is not
necessary.  Remember, the complex cases occur when the compiler munges
up control flow and data accessability, so debuginfo cannot or does
not correctly place the probes and their data gathering compatriots.

- FChE

Attachment: pgp00000.pgp
Description: PGP signature