From: tip-bot for Jan Kiszka <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, jan.kiszka@siemens.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, jailhouse-dev@googlegroups.com,
hpa@zytor.com
Subject: [tip:x86/platform] x86/jailhouse: Set X86_FEATURE_TSC_KNOWN_FREQ
Date: Fri, 19 Jan 2018 23:19:11 -0800 [thread overview]
Message-ID: <tip-11f19ec025dd421c54978c69e42d86758fa310de@git.kernel.org> (raw)
In-Reply-To: <975fbfc9-2a64-cc56-40d5-164992ec3916@siemens.com>
Commit-ID: 11f19ec025dd421c54978c69e42d86758fa310de
Gitweb: https://git.kernel.org/tip/11f19ec025dd421c54978c69e42d86758fa310de
Author: Jan Kiszka <jan.kiszka@siemens.com>
AuthorDate: Fri, 19 Jan 2018 11:06:17 +0100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Sat, 20 Jan 2018 08:15:43 +0100
x86/jailhouse: Set X86_FEATURE_TSC_KNOWN_FREQ
Otherwise, Linux will not recognize precalibrated_tsc_khz and disable
the tsc as clocksource.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Jailhouse <jailhouse-dev@googlegroups.com>
Link: https://lkml.kernel.org/r/975fbfc9-2a64-cc56-40d5-164992ec3916@siemens.com
---
arch/x86/kernel/jailhouse.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c
index 7ade152..2b7ebbe 100644
--- a/arch/x86/kernel/jailhouse.c
+++ b/arch/x86/kernel/jailhouse.c
@@ -176,6 +176,7 @@ static void __init jailhouse_init_platform(void)
pr_debug("Jailhouse: PM-Timer IO Port: %#x\n", pmtmr_ioport);
precalibrated_tsc_khz = setup_data.tsc_khz;
+ setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ);
pci_probe = 0;
prev parent reply other threads:[~2018-01-20 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 10:06 [PATCH] " Jan Kiszka
2018-01-20 7:19 ` tip-bot for Jan Kiszka [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=tip-11f19ec025dd421c54978c69e42d86758fa310de@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--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
Powered by JetHome