Matthieu, are you aware of the work done on generalized RAS hooks for
linux? It was used in dprpbes, LTT and LKST at one time. That in its own
way dealt with some of the issues you're trying to solve. I'm not saying
it's the correct solution, but it shares a lot of common ground. Check out
"kernel hooks" aka ghki. We used it to dynamically remove dprobes from the
pagefault code path when no user probes were active. It was also used to
instrument tracepoints for different facilities that needed to share
instrumentation point. There was also a /proc interface that showed which
hooks were installed and their status. We have generic mechanisms that
would work across most architectures and optimized ones for specific
architectures. One thing we tried to do was to make sure that affect on
data cache was minimized or eliminated. We achieved that on IA32 by making
the hook mechanism a test following a load of a literal into a register.
The hook was activated and deactivated by moving 1 or 0 into a register -
i.e. by editing the literal in the instruction. (changing mov eax,0 to mov
eax,1)
You might as well see whether there are any bone on that carcass worth
picking.
Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
