Tomas Glozar <[email protected]> writes: > I was talking about preventing other (non-RV) consumers of > bpf_trace_printk from seeing the RV prints. Eg. if I create a tracefs > instance and enable bpf_trace_printk, intending to see my own debug > prints, I will also see debug prints for RV, unless I explicitly > filter them out. I get that on the RV side, these are mostly > equivalent.
I haven't used BPF before, but is that not an RV-specific problem? If user has two BPF programs running that both do bpf_trace_printk, obviously they get mixed prints. They can either filter out other prints, or stop running the other one. Additionally an RV message only appears when something is wrong. So when there is an RV print, there is a bigger problem to worry about. Nam
