Kernel module memory access

I supose you intend to implement another kernel module as you think it is easier to share data between kernel modules. But perhaps it is not a good choice. If it is possible to 'profile the noise' in user space, I think a better solution is to implement the 'profiler' in user space.

In this solution, the user space profiler reads data, performe some calculations, and than submit the result.

If this solution is ok, the implementation is as follows.

In the kernel module, it is just to register a char device in '/proc' and implement 'read' and 'write' primitives. In user space, is just to implement the profiler, reading and writing to the char device. Details and information for this implementation is all here.