If I understand this code correctly, then changing immediate values
needs some exclusion to avoid patching live code. You leave this to the
user with some very unclear rules.
The result is a real mess that has nothing to do with the module mutex
and list. These patches need a lot more work 8(
1) The immediate types are just kind of silly. See per-cpu for how it
handles this already. DECLARE_IMMEDIATE(type, var) is probably enough.
2) immediate_if() needs an implementation before you introduce it. Your
assumption that it's always unlikely seems non-orthogonal.
3) immediate_set(), _immediate_set() and immediate_set_early()? No
thanks! AFAICT you really want an "init_immediate(var, val)". This
means "you can patch all the references now, they're not executing".
Later on we could possibly have a super-stop-machine version which
ensures noone's preempted and handles the concurrent case. Maybe.
4) With an "init" interface not a "set" interface, you don't need
Hope that helps,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/