wireguard-linux/include/trace/events/kyber.h, branch jd/unified-crypt-queueWireGuard for the Linux kernelhttps://git.zx2c4.com/wireguard-linux/atom/include/trace/events/kyber.h?h=jd%2Funified-crypt-queue2018-11-12T15:28:37Zkyber: fix wrong strlcpy() size in trace_kyber_latency()2018-11-12T15:28:37ZOmar Sandovalosandov@fb.com2018-11-12T08:08:46Zurn:sha1:18e962ac0781bcb70d433de3b2a325ff792b4288
When copying to the latency type, we should be passing LATENCY_TYPE_LEN,
not DOMAIN_LEN (this isn't a problem in practice because we only pass
"total" or "I/O"). Fix it by changing all of the strlcpy() calls to use
sizeof().
Fixes: 6c3b7af1c975 ("kyber: add tracepoints")
Reported-by: Jordan Glover <Golden_Miller83@protonmail.ch>
Tested-by: Jordan Glover <Golden_Miller83@protonmail.ch>
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
kyber: add tracepoints2018-09-27T23:34:59ZOmar Sandovalosandov@fb.com2018-09-27T22:55:55Zurn:sha1:6c3b7af1c975b87b86dcb2af233d1ae21eb05107
When debugging Kyber, it's really useful to know what latencies we've
been having, how the domain depths have been adjusted, and if we've
actually been throttling. Add three tracepoints, kyber_latency,
kyber_adjust, and kyber_throttled, to record that.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>