[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160921190856.GP2892@codeblueprint.co.uk>
Date: Wed, 21 Sep 2016 20:08:56 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Petr Mladek <pmladek@...e.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Byungchul Park <byungchul.park@....com>,
Frederic Weisbecker <fweisbec@...il.com>,
Luca Abeni <luca.abeni@...tn.it>,
Rik van Riel <riel@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Wanpeng Li <wanpeng.li@...mail.com>,
Yuyang Du <yuyang.du@...el.com>, Jan Kara <jack@...e.cz>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel@...r.kernel.org,
Mel Gorman <mgorman@...hsingularity.net>,
Mike Galbraith <umgwanakikbuti@...il.com>
Subject: Re: [PATCH v2 7/7] sched/core: Add debug code to catch missing
update_rq_clock()
On Wed, 21 Sep, at 05:58:27PM, Petr Mladek wrote:
>
> I am not sure how the above call chain is realistic. But adding
> WARN_ON() into the scheduler paths is risky in general.
It's not clear to me why this should be the case. WARN_ON() calls have
existed in the scheduler paths since forever.
If the new async printk patches make that impossible then surely they
need fixing, not the scheduler?
Powered by blists - more mailing lists