From: "tip-bot2 for Hayato Ohhashi" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Hayato Ohhashi <o8@vmm.dev>, Ingo Molnar <mingo@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/timers] x86/xen/time: Set the X86_FEATURE_TSC_KNOWN_FREQ flag in xen_tsc_khz()
Date: Sat, 25 Jul 2020 13:53:36 -0000 [thread overview]
Message-ID: <159568521657.4006.636725222719551278.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200721161231.6019-1-o8@vmm.dev>
The following commit has been merged into the x86/timers branch of tip:
Commit-ID: 898ec52d2ba05915aaedcdb21bff2e944c883cb8
Gitweb: https://git.kernel.org/tip/898ec52d2ba05915aaedcdb21bff2e944c883cb8
Author: Hayato Ohhashi <o8@vmm.dev>
AuthorDate: Tue, 21 Jul 2020 16:12:31
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Sat, 25 Jul 2020 15:49:41 +02:00
x86/xen/time: Set the X86_FEATURE_TSC_KNOWN_FREQ flag in xen_tsc_khz()
If the TSC frequency is known from the pvclock page,
the TSC frequency does not need to be recalibrated.
We can avoid recalibration by setting X86_FEATURE_TSC_KNOWN_FREQ.
Signed-off-by: Hayato Ohhashi <o8@vmm.dev>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Link: https://lore.kernel.org/r/20200721161231.6019-1-o8@vmm.dev
---
arch/x86/xen/time.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index c8897aa..91f5b33 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -39,6 +39,7 @@ static unsigned long xen_tsc_khz(void)
struct pvclock_vcpu_time_info *info =
&HYPERVISOR_shared_info->vcpu_info[0].time;
+ setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ);
return pvclock_tsc_khz(info);
}
prev parent reply other threads:[~2020-07-25 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 16:12 [PATCH] x86/xen/time: set " Hayato Ohhashi
2020-07-21 23:33 ` Boris Ostrovsky
2020-07-25 13:53 ` tip-bot2 for Hayato Ohhashi [this message]
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=159568521657.4006.636725222719551278.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=o8@vmm.dev \
--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®