Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 23 Aug 2021 23:18:58 -0400
From:   Dave Jones <davej@codemonkey.org.uk>
To:     Linux Kernel <linux-kernel@vger.kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 5.14-rc breaks iotop swap io monitoring.
Message-ID: <20210824031858.GA3263@codemonkey.org.uk>
Mail-Followup-To: Dave Jones <davej@codemonkey.org.uk>,
        Linux Kernel <linux-kernel@vger.kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
References: <20210824031648.GA2725@codemonkey.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210824031648.GA2725@codemonkey.org.uk>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Mon, Aug 23, 2021 at 11:16:48PM -0400, Dave Jones wrote:
 > I just noticed that in 5.14-rc running iotop, it complains on startup
 > that "CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine
 > SWAPIN and IO %" and sure enough a bunch of columns show up as
 > 'unavailable'.
 > 
 > My suspicion is this commit, which I've not confirmed yet as it doesn't
 > cleanly revert.  I'll poke at it some more in the morning, but figured
 > I'd bring it up sans-evidence in the hope that I'll wake up to someone
 > having an Ah-ha moment.

Forgot to mention, my config has both SCHEDSTATS, SCHED_INFO and TASK_DELAY_ACCT set
to =y

 	Dave