From: Thomas Gleixner <tglx@linutronix.de>
To: hpa@zytor.com
Cc: Guenter Roeck <linux@roeck-us.net>,
Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Thomas Lendacky <Thomas.Lendacky@amd.com>
Subject: Re: [PATCH] x86/TSC: Use RDTSCP
Date: Fri, 23 Nov 2018 21:44:12 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1811232143000.1684@nanos.tec.linutronix.de> (raw)
In-Reply-To: <62E011F5-639B-4CF9-8A8B-091C84749F43@zytor.com>
On Fri, 23 Nov 2018, hpa@zytor.com wrote:
> On November 23, 2018 12:03:07 PM PST, Guenter Roeck <linux@roeck-us.net> wrote:
> ># first bad commit: [2e94061096c5c3aa6c3fe3ec2bec176c1f9c1b07] x86/TSC:
> >Use RDTSCP
>
> Right, because that cpu predates RDTSCP, so it needs to use a fallback.
Well, that's not the problem.
The default here is MFENCE; RDTSC; But P3 does not have MFENCE either :)
We need alternative_3 with default RDTSC
Thanks,
tglx
next prev parent reply other threads:[~2018-11-23 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 18:45 [PATCH] x86/TSC: Use RDTSCP Borislav Petkov
2018-11-19 19:02 ` Lendacky, Thomas
2018-11-19 19:52 ` Andy Lutomirski
2018-11-19 20:17 ` H. Peter Anvin
2018-11-19 20:40 ` Borislav Petkov
2018-11-19 20:48 ` hpa
2018-11-20 9:11 ` [tip:x86/timers] " tip-bot for Borislav Petkov
2018-11-23 20:03 ` [PATCH] " Guenter Roeck
2018-11-23 20:22 ` hpa
2018-11-23 20:44 ` Thomas Gleixner [this message]
2018-11-23 20:44 ` Borislav Petkov
2018-11-23 21:03 ` Guenter Roeck
2018-11-23 21:07 ` Borislav Petkov
2018-12-07 18:39 ` Borislav Petkov
2019-01-16 11:59 ` [tip:x86/alternatives] " tip-bot for Borislav Petkov
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=alpine.DEB.2.21.1811232143000.1684@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).