Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757923AbcJXXdJ (ORCPT ); Mon, 24 Oct 2016 19:33:09 -0400 Received: from ms01.sssup.it ([193.205.80.99]:55195 "EHLO sssup.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbcJXXdG (ORCPT ); Mon, 24 Oct 2016 19:33:06 -0400 X-Greylist: delayed 3602 seconds by postgrey-1.27 at vger.kernel.org; Mon, 24 Oct 2016 19:33:05 EDT From: Tommaso Cucinotta To: Luca Abeni , Juri Lelli , Peter Zijlstra Cc: linux-kernel@vger.kernel.org, linux-dl@retis.sssup.it, Tommaso Cucinotta , Daniel Bistrot de Oliveira Subject: [RFC PATCH] sched/deadline: show leftover runtime and abs deadline in /proc/-/sched Date: Tue, 25 Oct 2016 00:32:53 +0200 Message-Id: <1477348374-8248-1-git-send-email-tommaso.cucinotta@sssup.it> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 845 Lines: 19 Hi all, this is a tiny patch providing readings of the current (leftover) runtime and absolute deadline in /proc/*/sched. Mostly useful for debugging, I heard others playing with SCHED_DEADLINE had some need for similar patches as well. In addition to debugging, reading the leftover runtime is generally useful for adaptive/incremental RT logics that need to check whether there's enough runtime left for refining the computed result, or just use what we've computed so far and block till the next instance. Also, knowing what the absolute scheduling deadline is (along with what clock it refers to) might be useful for synchronization purposes. (albeit, for real production code, I wouldn't like to parse /proc anyway, rather I'd prefer to retrieve those params via eg sched_getscheduler()?) Please, share your thoughts, thanks. Tommaso