Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails

[Jiri Kosina]

On Mon, 23 Mar 2015, Paul E. McKenney wrote:

> > > Even if it was documented (it isn't), it's pretty weird terminology - 
> > > please use clearer formulations, like 'patched function' or 'unpatched 
> > > function' or 'function with pending patch'. No need to redefine 
> > > existing words in a weird fashion just to create the appearance of 
> > > being special ...
> > > 
> > 
> > I think it has to do with their RCU like patching functionality, where
> > some tasks are still executing the old function and others are
> > executing the new function. In RCU, there's two "universes" too. One
> > with the old value, and one with the new. After the grace period has
> > finished, everything is back to a single "universe".
> > 
> > I'm not sure RCU uses the term "universe" though. Paul?
> 
> I have used "version" for what you call "universe", but mostly in
> "intro to RCU" guest lectures.

Yup, exactly. Even kGraft (which is where the 'universe' term referring to 
the function versioning in lazy migration is very likely coming from) 
doesn't really use the term 'universe' itself anywhere in the sources as 
any kind of identifier. It's always used solely as a term that's intended 
to simplify the basic understanding of how the whole process works, and 
that's pretty much it. I don't even think it deserves so lively discussion 
:)

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/