[ltt-dev] Porting "jump labels" to userspace

Thomas Gleixner tglx at linutronix.de
Wed Feb 16 15:45:30 EST 2011

On Wed, 16 Feb 2011, Mathieu Desnoyers wrote:

> * David Daney (ddaney at caviumnetworks.com) wrote:
> > On 02/16/2011 12:04 PM, Roland McGrath wrote:
> >> IMHO there is not really so much to the in-kernel implementation that it's
> >> worth attempting to reuse the code in userland.  Pretty much all the work
> >> is in the details of the implementation that would naturally differ a lot
> >> in a different context.  If you understand the mechanism and the machine
> >> details, then implementing it well for a userland context is not a big deal
> >> and is cleaner to do from scratch than shoe-horning kernel-centric code
> >> into a wildly different context.
> >>
> >
> > Good point.
> >
> > Certainly the details of maintaining instruction cache coherency may be  
> > different in userspace.
> Indeed, the arch-specific parts will need some extra care (which might, in the
> worse case scenario, require to suspend a whole process during the update), but
> the generic code in jump_label.c and jump_label.h could certainly be reused.

We talk about 500 lines of code, where half of it is modules specific
and the whole thing is full of kernelims. IMNSHO, that's faster
reimplemented from scratch than writing all the mails and get the
authors to sign off on the license change.



More information about the lttng-dev mailing list