From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Steve Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
<linux@armlinux.org.uk>, <schwidefsky@de.ibm.com>,
<heiko.carstens@de.ibm.com>, John Stultz <john.stultz@linaro.org>,
<sboyd@codeaurora.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, <hpa@zytor.com>
Subject: Re: [PATCH v7 1/6] x86/tsc: remove tsc_disabled flag
Date: Wed, 8 Nov 2017 16:52:34 +0800 [thread overview]
Message-ID: <651534c5-5095-4b93-dbdf-e4808cc0eaee@cn.fujitsu.com> (raw)
In-Reply-To: <CAOAebxtc6v+fvwYJ_eqTCC=AndStRhR=vwoembyywTy2WNYH2g@mail.gmail.com>
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
next prev parent reply other threads:[~2017-11-08 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 17:26 [PATCH v7 0/6] Early boot time stamps for x86 Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 1/6] x86/tsc: remove tsc_disabled flag Pavel Tatashin
2017-11-03 1:58 ` Dou Liyang
2017-11-03 14:23 ` Pavel Tatashin
2017-11-08 8:52 ` Dou Liyang [this message]
2017-11-08 17:23 ` Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 2/6] time: sync read_boot_clock64() with persistent clock Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 3/6] x86/time: read_boot_clock64() implementation Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 4/6] sched: early boot clock Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 5/6] x86/paravirt: add active_sched_clock to pv_time_ops Pavel Tatashin
2017-11-02 17:26 ` [PATCH v7 6/6] x86/tsc: use tsc early Pavel Tatashin
2017-11-03 2:54 ` Dou Liyang
2017-11-03 14:30 ` Pavel Tatashin
2017-11-08 9:17 ` Dou Liyang
2017-11-08 17:24 ` Pavel Tatashin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=651534c5-5095-4b93-dbdf-e4808cc0eaee@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=daniel.m.jordan@oracle.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=schwidefsky@de.ibm.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®