On 02/03/2017 09:38 PM, David Ahern wrote:
Similar to classic bpf, support saving original ebpf instructions
Signed-off-by: David Ahern <d...@cumulusnetworks.com>
Not convinced that this is in the right direction, this not only *significantly*
increases mem footprint for each and every program, but also when you dump this,
then map references from relocs inside the insns are meaningless (f.e. what
about
prog arrays used in tail calls?), so things like criu also won't be able to use
this kind of interface for dump and restore. If it's just for debugging, then
why not extend the existing tracing infrastructure around bpf that was started
with intention to gain more visibility.
Thanks,
Daniel
