[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <573E75CD.6050202@ozlabs.org>
Date: Fri, 20 May 2016 10:26:21 +0800
From: Jeremy Kerr <jk@...abs.org>
To: Ming Lei <ming.lei@...onical.com>,
Scot Doyle <lkml14@...tdoyle.com>
Cc: Tomi Valkeinen <tomi.valkeinen@...com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
David Daney <david.daney@...ium.com>,
Dann Frazier <dann.frazier@...onical.com>,
Peter Hurley <peter@...leysoftware.com>,
Pavel Machek <pavel@....cz>, Jonathan Liu <net147@...il.com>,
Alistair Popple <alistair@...ple.id.au>,
Jean-Philippe Brucker <jean-philippe.brucker@....com>,
"Chintakuntla, Radha" <Radha.Chintakuntla@...iumnetworks.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, David Airlie <airlied@...ux.ie>,
David Daney <ddaney.cavm@...il.com>,
dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH] fbcon: warn on invalid cursor blink intervals
Hi Ming,
> Not sure this one is needed for stable because it justs dumps
> a warning, and not set a valid period to ops->cur_blink_jiffies.
>
> So I guess other fix patch is still required for the soft lockup
> issue, right?
The main thing is that we don't set cur_blink_jiffies to the < 50ms
value. As far as I can tell, it means we'll still get the original
default, set in fbcon_startup():
ops->cur_blink_jiffies = HZ / 5;
And so don't end up spinning on the timer expiry.
Cheers,
Jeremy
Powered by blists - more mailing lists