On 9/26/19 1:02 AM, Tejun Heo wrote: > vrate_adj tracepoint traces vrate changes; however, it does so only > when busy_level is non-zero. busy_level turning to zero can sometimes > be as interesting an event. This patch also enables vrate_adj > tracepoint on other vrate related events - busy_level changes and > non-zero nr_lagging. > > Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> > --- > Hello, Jens. > > I've encountered vrate regulation issues while testing on a hard disk > machine. These are three patches to improve vrate adj visibility and > fix the issue. Applied 1-3 for 5.4, thanks Tejun. -- Jens Axboe
