From: Saurabh Sengar <ssengar@xxxxxxxxxxxxxxxxxxx> Sent: Friday, September 9, 2022 8:10 AM > > Due to a full ring buffer, the driver may be unable to send updates to > the Hyper-V host. But outputing the error message can make the problem > worse because console output is also typically written to the frame > buffer. > Rate limiting the error message, also output the error code for additional > diagnosability. > > Signed-off-by: Saurabh Sengar <ssengar@xxxxxxxxxxxxxxxxxxx> > --- > drivers/gpu/drm/hyperv/hyperv_drm_proto.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/hyperv/hyperv_drm_proto.c > b/drivers/gpu/drm/hyperv/hyperv_drm_proto.c > index 76a182a..013a782 100644 > --- a/drivers/gpu/drm/hyperv/hyperv_drm_proto.c > +++ b/drivers/gpu/drm/hyperv/hyperv_drm_proto.c > @@ -208,7 +208,7 @@ static inline int hyperv_sendpacket(struct hv_device *hdev, > struct synthvid_msg > VM_PKT_DATA_INBAND, 0); > > if (ret) > - drm_err(&hv->dev, "Unable to send packet via vmbus\n"); > + drm_err_ratelimited(&hv->dev, "Unable to send packet via vmbus; error %d\n", ret); > > return ret; > } > -- > 1.8.3.1 Reviewed-by: Michael Kelley <mikelley@xxxxxxxxxxxxx>
