From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752580AbcERCmr (ORCPT <rfc822;w@1wt.eu>);
	Tue, 17 May 2016 22:42:47 -0400
Received: from mga09.intel.com ([134.134.136.24]:14589 "EHLO mga09.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752366AbcERCmq (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 17 May 2016 22:42:46 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.26,326,1459839600"; 
   d="scan'208";a="704811296"
Date: Wed, 18 May 2016 03:01:27 +0800
From: Yuyang Du <yuyang.du@intel.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>,
        linux-kernel@vger.kernel.org, Byungchul Park <byungchul.park@lge.com>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Luca Abeni <luca.abeni@unitn.it>,
        "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
        Rik van Riel <riel@redhat.com>, Thomas Gleixner <tglx@linutronix.de>,
        Wanpeng Li <wanpeng.li@hotmail.com>,
        Mel Gorman <mgorman@techsingularity.net>,
        Mike Galbraith <umgwanakikbuti@gmail.com>
Subject: Re: [RFC][PATCH 5/5] sched/core: Add debug code to catch missing
 update_rq_clock()
Message-ID: <20160517190127.GE8790@intel.com>
References: <1463082593-27777-1-git-send-email-matt@codeblueprint.co.uk>
 <1463082593-27777-6-git-send-email-matt@codeblueprint.co.uk>
 <20160515021439.GC8790@intel.com>
 <20160516094638.GB6574@codeblueprint.co.uk>
 <20160516201109.GD8790@intel.com>
 <20160517122415.GD21993@codeblueprint.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160517122415.GD21993@codeblueprint.co.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, May 17, 2016 at 01:24:15PM +0100, Matt Fleming wrote:
> So, if the code looks like the following, either now or in the future,
> 
> static void __schedule(bool preempt)
> {
> 	...
> 	/* Clear RQCF_ACT_SKIP */
> 	rq->clock_update_flags = 0;
> 	...
> 	delta = rq_clock();
> }
 
Sigh, you even said "Clear RQCF_ACT_SKIP", but you not only clear it,
you clear everything. And if you clear the RQCF_UPDATE also (maybe you
shouldn't, but actually it does not matter), of course you will get
a warning...

In addition, it looks like multiple skips are possible, so:

update_rq_clock() {
        rq->clock_update_flags |= RQCF_UPDATE;

        ...
}

instead of clearing the skip flag there.