Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 20 Jun 2018 01:13:13 +0200 (CEST)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Pavel Tatashin <pasha.tatashin@oracle.com>
cc:     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,
        peterz@infradead.org, prarit@redhat.com, feng.tang@intel.com,
        pmladek@suse.com, gnomes@lxorguk.ukuu.org.uk
Subject: Re: [PATCH v10 6/7] x86/paravirt: add active_sched_clock to
 pv_time_ops
In-Reply-To: <20180615174204.30581-7-pasha.tatashin@oracle.com>
Message-ID: <alpine.DEB.2.21.1806200110370.10546@nanos.tec.linutronix.de>
References: <20180615174204.30581-1-pasha.tatashin@oracle.com> <20180615174204.30581-7-pasha.tatashin@oracle.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> Early boot clock might differ from the clock that is used later on,
> therefore add a new field to pv_time_ops, that shows currently active
> clock. If platform supports early boot clock, this field will be changed
> to use that clock early in boot, and later will be replaced with the
> permanent clock.

I'm not seeing why this is required. If a hypervisor provides a
sched_clock() override then it's not the kernels problem to make sure that
it is usable.

Thanks,

	tglx