trace-cmd start -B devlib -b 42 will set the buffer size for the "devlib" ftrace instance but will not set the buffer size of the top-level buffer.
Unfortunately, some events still end up in the top-level buffer regardless of any configuration such as the "print" event. This can lead to lost events because the buffer size was too small.
Avoid that by using the buffer size for both top-level and devlib's instance.
trace-cmd start -B devlib -b 42 will set the buffer size for the "devlib" ftrace instance but will not set the buffer size of the top-level buffer.
Unfortunately, some events still end up in the top-level buffer regardless of any configuration such as the "print" event. This can lead to lost events because the buffer size was too small.
Avoid that by using the buffer size for both top-level and devlib's instance.