magic_write: Missing complicated definitions values in BPF programs

[AlonZivony]

In CO-RE there is no access to definitions in the kernel, so we need to calculate them ourselves.
Currently we created the missing_definitions.h file to define mandatory definitions.
However, this won't work for definitions which depends on kconfig values, or which are translated to globals which we don't have access to either in CO-RE.
There should be a way to calculate these complicated values for the BPF programs to use.

[AlonZivony]

I am wondering how to implement this one.
Most of the consts could be defined in the missing_definitions.h file.
However, some values depend on BPF helpers and globals, so they cannot be defined in compilation time.

My solution was to create a map between const key to its value.
However, this solution is much lest efficient than using defined value. So, if we make this the normal way to use consts we will harm the performance.
The other option is to create 2 APIs to get consts depending on its value complication (normal consts will be defined, and complicated accessed using map). This makes the code less accessible to new users.

WDYT @rafaeldtinoco?

[yanivagman]

This is more of implementation discussion than an issue in tracee.
Converting to discussion.