[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <651534c5-5095-4b93-dbdf-e4808cc0eaee@cn.fujitsu.com>
Date: Wed, 8 Nov 2017 16:52:34 +0800
From: Dou Liyang <douly.fnst@...fujitsu.com>
To: Pavel Tatashin <pasha.tatashin@...cle.com>
CC: Steve Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
<linux@...linux.org.uk>, <schwidefsky@...ibm.com>,
<heiko.carstens@...ibm.com>, John Stultz <john.stultz@...aro.org>,
<sboyd@...eaurora.org>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>, <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, <hpa@...or.com>
Subject: Re: [PATCH v7 1/6] x86/tsc: remove tsc_disabled flag
Hi Pavel,
At 11/03/2017 10:23 PM, Pavel Tatashin wrote:
> Hi Dou,
>
> Sure, I can remove the warning, but I think we should print something
> that is indicating that notsc is not a good parameter anymore: i.e
> tsc=unstable is better. Perhaps something like:
> "Kernel parameter \'notsc\' is deprecated, please use
> \'tsc=unstable\' instead" ?
>
IMO, we already have a message by
mark_tsc_unstable("boot parameter notsc");
and we will use 'notsc' in case of CONFIG_X86_TSC = no
So, I guess there is no need to print this msg.
Thanks,
dou.
> Pasha
Powered by blists - more mailing lists