Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1740753

Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early in boot

From Dou Liyang <douly.fnst@cn.fujitsu.com>
Newsgroups linux.kernel
Subject Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early in boot
Date 2017-09-27 16:00 +0200
Message-ID <uul2x-3HA-9@gated-at.bofh.it> (permalink)
References <ukfB7-3fk-11@gated-at.bofh.it> <ukfB8-3fk-31@gated-at.bofh.it> <uuk6u-2Hs-1@gated-at.bofh.it> <uukpP-3b4-5@gated-at.bofh.it> <uukpP-3b4-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Pasha, Peter

At 09/27/2017 09:16 PM, Pasha Tatashin wrote:
> Hi Peter,
>
> I am totally happy with removing notsc. This certainly simplifies the
> sched_clock code. Are there any issues with removing existing kernel
> parameters that I should be aware of?
>

We do not want to do that. Because, we use "notsc" to support Dynamic
Reconfiguration[1].

AFAIK, this feature enables hot-add system board which contains CPUs
and memories. But the CPUs in different board may have different TSCs
which are not consistent with the TSC from the existing CPUs. If we 
hot-add a board directly, the machine may happen the inconsistency of
TSC.

We make our effort to specify the same TSC value as existing one through
hardware and firmware, but it is hard. So we recommend to specify
"notsc" option in command line for users who want to use Dynamic
Reconfiguration.

[1] 
http://www.fujitsu.com/global/products/computing/servers/mission-critical/primequest/technology/availability/dynamic-reconfiguration.html

Thanks,

	dou

> Thank you,
> Pasha
>
> On 09/27/2017 09:10 AM, Peter Zijlstra wrote:
>> On Wed, Sep 27, 2017 at 02:58:57PM +0200, Peter Zijlstra wrote:
>>> (we're violating "notsc" in any case and really should kill that
>>> option).
>>
>> Something like so; in particular simple_udelay_calibrate() will issue
>> RDTSC _way_ early, so there is absolutely no point in then pretending we
>> can't use RDTSC for sched_clock.
>>
>
>
>

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Peter Zijlstra <peterz@infradead.org> - 2017-09-27 15:00 +0200
  Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-09-27 15:20 +0200
    Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Dou Liyang <douly.fnst@cn.fujitsu.com> - 2017-09-27 16:00 +0200
      Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-09-27 19:20 +0200
      Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Peter Zijlstra <peterz@infradead.org> - 2017-09-27 20:10 +0200
        Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Peter Zijlstra <peterz@infradead.org> - 2017-09-27 20:20 +0200
          Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Dou Liyang <douly.fnst@cn.fujitsu.com> - 2017-09-28 12:10 +0200
            Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Peter Zijlstra <peterz@infradead.org> - 2017-09-28 14:00 +0200
              Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Thomas Gleixner <tglx@linutronix.de> - 2017-09-28 14:20 +0200
                Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Pasha Tatashin <pasha.tatashin@oracle.com> - 2017-09-28 15:20 +0200
                Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Dou Liyang <douly.fnst@cn.fujitsu.com> - 2017-09-29 17:10 +0200
  Re: [PATCH v6 1/4] sched/clock: interface to allow timestamps early  in boot Peter Zijlstra <peterz@infradead.org> - 2017-09-27 15:20 +0200

csiph-web