From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jia He <hejianet@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Ingo Molnar <mingo@kernel.org>,
fweisbec@gmail.com, Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Ivan Mikhaylov <ivan@de.ibm.com>,
cyrilbur@gmail.com
Subject: Re: [PATCH] powerpc/time: use get_tb instead of get_vtb in running_clock
Date: Thu, 13 Jul 2017 08:45:04 +1000 [thread overview]
Message-ID: <1499899504.2865.44.camel@kernel.crashing.org> (raw)
In-Reply-To: <1499871670-24671-1-git-send-email-hejianet@gmail.com>
On Wed, 2017-07-12 at 23:01 +0800, Jia He wrote:
> Virtual time base(vtb) is a register which increases only in guest.
> Any exit from guest to host will stop the vtb(saved and restored by kvm).
> But if there is an IO causes guest exits to host, the guest's watchdog
> (watchdog_timer_fn -> is_softlockup -> get_timestamp -> running_clock)
> needs to also include the time elapsed in host. get_vtb is not correct in
> this case.
>
> Also, the TB_OFFSET is well saved and restored by qemu after commit [1].
> So we can use get_tb here.
That completely defeats the purpose here... This was done specifically
to exploit the VTB which doesn't count in hypervisor mode.
>
> [1] http://git.qemu.org/?p=qemu.git;a=commit;h=42043e4f1
>
> Signed-off-by: Jia He <hejianet@gmail.com>
> ---
> arch/powerpc/kernel/time.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
> index fe6f3a2..c542dd3 100644
> --- a/arch/powerpc/kernel/time.c
> +++ b/arch/powerpc/kernel/time.c
> @@ -695,16 +695,15 @@ notrace unsigned long long sched_clock(void)
> unsigned long long running_clock(void)
> {
> /*
> - * Don't read the VTB as a host since KVM does not switch in host
> - * timebase into the VTB when it takes a guest off the CPU, reading the
> - * VTB would result in reading 'last switched out' guest VTB.
> + * Use get_tb instead of get_vtb for guest since the TB_OFFSET has been
> + * well saved/restored when qemu does suspend/resume.
> *
> * Host kernels are often compiled with CONFIG_PPC_PSERIES checked, it
> * would be unsafe to rely only on the #ifdef above.
> */
> if (firmware_has_feature(FW_FEATURE_LPAR) &&
> cpu_has_feature(CPU_FTR_ARCH_207S))
> - return mulhdu(get_vtb() - boot_tb, tb_to_ns_scale) << tb_to_ns_shift;
> + return mulhdu(get_tb() - boot_tb, tb_to_ns_scale) << tb_to_ns_shift;
>
> /*
> * This is a next best approximation without a VTB.
next prev parent reply other threads:[~2017-07-12 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 15:01 [PATCH] powerpc/time: use get_tb instead of get_vtb in running_clock Jia He
2017-07-12 22:45 ` Benjamin Herrenschmidt [this message]
2017-07-13 6:55 ` hejianet
2017-07-13 20:50 ` Benjamin Herrenschmidt
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=1499899504.2865.44.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=cyrilbur@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hejianet@gmail.com \
--cc=ivan@de.ibm.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sgruszka@redhat.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).