mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Pavel Tatashin <pasha.tatashin@oracle.com>,
	steven.sistare@oracle.com, daniel.m.jordan@oracle.com,
	linux@armlinux.org.uk, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, john.stultz@linaro.org,
	sboyd@codeaurora.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
	douly.fnst@cn.fujitsu.com, prarit@redhat.com,
	feng.tang@intel.com, pmladek@suse.com,
	gnomes@lxorguk.ukuu.org.uk
Subject: Re: [PATCH v10 1/7] x86/tsc: remove tsc_disabled flag
Date: Tue, 19 Jun 2018 22:01:15 +0200	[thread overview]
Message-ID: <20180619200115.GH2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1806192110230.10546@nanos.tec.linutronix.de>

On Tue, Jun 19, 2018 at 09:12:45PM +0200, Thomas Gleixner wrote:
> On Tue, 19 Jun 2018, Peter Zijlstra wrote:
> > It does not; there is TSC usage even if you boot with notsc on. See how
> > it does not clear X86_FEATURE_TSC for instance.
> 
> Well, kinda. There is some stuff in the apic calibration which uses TSC
> independent of tsc_disabled, but that's about it.

Still, that precludes booting on hardware without TSC, so what's the
point of having notsc? I'm all for killing the thing.

  reply	other threads:[~2018-06-19 20:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 17:41 [PATCH v10 0/7] Early boot time stamps for x86 Pavel Tatashin
2018-06-15 17:41 ` [PATCH v10 1/7] x86/tsc: remove tsc_disabled flag Pavel Tatashin
2018-06-19 17:32   ` Thomas Gleixner
2018-06-19 17:50     ` Pavel Tatashin
2018-06-19 18:46     ` Peter Zijlstra
2018-06-19 19:12       ` Thomas Gleixner
2018-06-19 20:01         ` Peter Zijlstra [this message]
2018-06-19 20:57           ` Thomas Gleixner
2018-06-19 21:00             ` Peter Zijlstra
2018-06-15 17:41 ` [PATCH v10 2/7] time: sync read_boot_clock64() with persistent clock Pavel Tatashin
2018-06-19 21:14   ` Thomas Gleixner
2018-06-19 21:25     ` Pavel Tatashin
2018-06-15 17:42 ` [PATCH v10 3/7] x86/time: read_boot_clock64() implementation Pavel Tatashin
2018-06-18  8:42   ` Andy Shevchenko
2018-06-18  8:44     ` Andy Shevchenko
2018-06-19 14:23       ` Pavel Tatashin
2018-06-19 20:39         ` Andy Shevchenko
2018-06-15 17:42 ` [PATCH v10 4/7] sched: early boot clock Pavel Tatashin
2018-06-15 17:42 ` [PATCH v10 5/7] kvm/x86: remove kvm memblock dependency Pavel Tatashin
2018-06-15 17:42 ` [PATCH v10 6/7] x86/paravirt: add active_sched_clock to pv_time_ops Pavel Tatashin
2018-06-19 23:13   ` Thomas Gleixner
2018-06-15 17:42 ` [PATCH v10 7/7] x86/tsc: use tsc early Pavel Tatashin
2018-06-19 22:51   ` Thomas Gleixner
2018-06-19 23:20   ` Thomas Gleixner
2018-06-19 23:52   ` Thomas Gleixner
2018-06-20  0:00     ` Pavel Tatashin
2018-06-20  9:15     ` Peter Zijlstra
2018-06-20 10:42       ` Thomas Gleixner
2018-06-20 12:32         ` Peter Zijlstra
2018-06-20 13:29           ` Thomas Gleixner
2018-06-20 21:30           ` Pavel Tatashin
2018-06-20 10:12     ` Feng Tang
2018-06-20 10:16       ` Thomas Gleixner
2018-06-20 10:29         ` Feng Tang
2018-06-20 10:30           ` Thomas Gleixner
2018-06-20 10:39             ` Feng Tang
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09 21:11 [PATCH v10 0/7] Early boot time stamps for x86 Pavel Tatashin
2018-02-09 21:11 ` [PATCH v10 1/7] x86/tsc: remove tsc_disabled flag 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=20180619200115.GH2494@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=daniel.m.jordan@oracle.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=feng.tang@intel.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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=pmladek@suse.com \
    --cc=prarit@redhat.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®