use pr_warn_ratelimited() for vq_err()
Subsystems (3)
PATCH 1/1 use pr_warn_ratelimited() for vq_err()
vq_err() is used to report various failure states in vhost code, but by default uses pr_debug(), and as a result doesn't record anything unless enabled via dynamic debug. We'll change this so we get something recorded in the log in these failure cases. Guest VMs (and userspace) can trigger some of these messages, so we want to use the pr_warn_ratelimited() variant.
--- drivers/vhost/vhost.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/vhost/vhost.h +4 -4
@@ -228,10 +228,10 @@ int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled);void vhost_iotlb_map_free (struct vhost_iotlb *iotlb,struct vhost_iotlb_map *map); -#define vq_err (vq, fmt, ...) do { \ - pr_debug(pr_fmt(fmt), ##__VA_ARGS__); \ - if ((vq)->error_ctx) \ - eventfd_signal((vq)->error_ctx, 1);\ +#define vq_err (vq, fmt, ...) do { \ + pr_warn_ratelimited(pr_fmt(fmt), ##__VA_ARGS__); \ + if ((vq)->error_ctx) \ + eventfd_signal((vq)->error_ctx, 1); \ } while (0)enum {
Signature · 1 line
2.25.1
Quoted 6 lines · John Levon
vq_err()is used to report various failure states in vhost code, but by default usespr_debug(), and as a result doesn't record anything unless enabled via dynamic debug. We'll change this so we get something recorded in the log in these failure cases. Guest VMs (and userspace) can trigger some of these messages, so we want to use thepr_warn_ratelimited()variant.
It looks to me KVM also use pr_warn_ratelimited().
So
Quoted 15 lines
Signed-off-by John Levon <[email protected]>--- drivers/vhost/vhost.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)drivers/vhost/vhost.h +0
-1@@ -228,10 +228,10 @@ int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled);void vhost_iotlb_map_free (struct vhost_iotlb *iotlb,struct vhost_iotlb_map *map); -#define vq_err (vq, fmt, ...) do { \
drivers/vhost/vhost.h int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled); · line 237
Quoted 10 lines
drivers/vhost/vhost.h +4
-3- pr_debug(pr_fmt(fmt), ##__VA_ARGS__); \ -if ((vq)->error_ctx) \ -eventfd_signal ((vq)->error_ctx,1 );\ +#define vq_err (vq, fmt, ...) do { \ + pr_warn_ratelimited(pr_fmt(fmt), ##__VA_ARGS__); \ + if ((vq)->error_ctx) \ + eventfd_signal((vq)->error_ctx, 1); \ } while (0)enum {
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 1/1 use pr_warn_ratelimited() for vq_err()
In reply to John Levonvq_err() is used to report various failure states in vhost code, but by default uses pr_debug(), and as a result doesn't record anything unless enabled via dynamic debug. We'll change this so we get something recorded in the log in these failure cases. Guest VMs (and userspace) can trigger some of these messages, so we want to use the pr_warn_ratelimited() variant. However, on DEBUG kernels, we'd like to get everything, so we use pr_warn() then.
---
v2: use pr_warn() for DEBUG kernels
--- drivers/vhost/vhost.h | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
drivers/vhost/vhost.h +10 -4
@@ -228,10 +228,16 @@ int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled);void vhost_iotlb_map_free (struct vhost_iotlb *iotlb,struct vhost_iotlb_map *map); -#define vq_err (vq, fmt, ...) do { \ - pr_debug(pr_fmt(fmt), ##__VA_ARGS__); \ - if ((vq)->error_ctx) \ - eventfd_signal((vq)->error_ctx, 1);\ +#ifdef DEBUG +#define vq_pr_warn pr_warn +#else +#define vq_pr_warn pr_warn_ratelimited +#endif + +#define vq_err (vq, fmt, ...) do { \ + vq_pr_warn(pr_fmt(fmt), ##__VA_ARGS__); \ + if ((vq)->error_ctx) \ + eventfd_signal((vq)->error_ctx, 1); \ } while (0)enum {
Signature · 1 line
2.25.1
Quoted 9 lines · John Levon
vq_err()is used to report various failure states in vhost code, but by default usespr_debug(), and as a result doesn't record anything unless enabled via dynamic debug. We'll change this so we get something recorded in the log in these failure cases. Guest VMs (and userspace) can trigger some of these messages, so we want to use thepr_warn_ratelimited()variant. However, on DEBUG kernels, we'd like to get everything, so we usepr_warn()then.Signed-off-by John Levon <[email protected]>
Quoted 33 lines
---
v2: usepr_warn()for DEBUG kernels--- drivers/vhost/vhost.h | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)drivers/vhost/vhost.h +10
-4@@ -228,10 +228,16 @@ int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled);void vhost_iotlb_map_free (struct vhost_iotlb *iotlb,struct vhost_iotlb_map *map); -#define vq_err (vq, fmt, ...) do { \ - pr_debug(pr_fmt(fmt), ##__VA_ARGS__); \ - if ((vq)->error_ctx) \ - eventfd_signal((vq)->error_ctx, 1);\ +#ifdef DEBUG +#define vq_pr_warn pr_warn +#else +#define vq_pr_warn pr_warn_ratelimited +#endif + +#define vq_err (vq, fmt, ...) do { \ + vq_pr_warn(pr_fmt(fmt), ##__VA_ARGS__); \ + if ((vq)->error_ctx) \ + eventfd_signal((vq)->error_ctx, 1); \ } while (0)enum {Signature · 1 line
2.25.1
dme.
Signature · 1 line
Slow me down, it's getting away from me.