Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757566AbeAHQsO (ORCPT + 1 other); Mon, 8 Jan 2018 11:48:14 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47814 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933724AbeAHQsJ (ORCPT ); Mon, 8 Jan 2018 11:48:09 -0500 Date: Mon, 8 Jan 2018 16:48:04 +0000 From: "Dr. David Alan Gilbert" To: Andrew Cooper Cc: Tom Lendacky , Thomas Gleixner , bp@alien8.de, dwmw@amazon.co.uk, gregkh@linux-foundation.org, pjt@google.com, mingo@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com, tim.c.chen@linux.intel.com, torvalds@linux-foundation.org, peterz@infradead.org, dave.hansen@intel.com, linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/pti] x86/cpu/AMD: Use LFENCE_RDTSC instead of MFENCE_RDTSC Message-ID: <20180108164803.GF2462@work-vm> References: <20180105160756.23786.4220.stgit@tlendack-t1.amdoffice.net> <1b179b8b-6cc8-d736-81dc-2445be4baf02@citrix.com> <4d9a1f0d-a401-3f0f-9ee2-dd42f4b4716a@amd.com> <929a34a1-e3bc-b1c8-4c71-196610c0d02a@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <929a34a1-e3bc-b1c8-4c71-196610c0d02a@citrix.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 08 Jan 2018 16:48:09 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: * Andrew Cooper (andrew.cooper3@citrix.com) wrote: > On 08/01/18 14:47, Tom Lendacky wrote: > > On 1/8/2018 5:10 AM, Thomas Gleixner wrote: > >> On Mon, 8 Jan 2018, Andrew Cooper wrote: > >> > >>> On 08/01/18 10:08, Thomas Gleixner wrote: > >>>> On Sat, 6 Jan 2018, tip-bot for Tom Lendacky wrote: > >>>> > >>>>> Commit-ID: 0bf17c102177d5da9363bf8b1e4704b9996d5079 > >>>>> Gitweb: https://git.kernel.org/tip/0bf17c102177d5da9363bf8b1e4704b9996d5079 > >>>>> Author: Tom Lendacky > >>>>> AuthorDate: Fri, 5 Jan 2018 10:07:56 -0600 > >>>>> Committer: Thomas Gleixner > >>>>> CommitDate: Sat, 6 Jan 2018 21:57:40 +0100 > >>>>> > >>>>> x86/cpu/AMD: Use LFENCE_RDTSC instead of MFENCE_RDTSC > >>>>> > >>>>> With LFENCE now a serializing instruction, set the LFENCE_RDTSC > >>>>> feature since the LFENCE instruction has less overhead than the > >>>>> MFENCE instruction. > >>>> Second thoughts on that. As pointed out by someone in one of the insane > >>>> long threads: > >>>> > >>>> What happens if the kernel runs as a guest and > >>>> > >>>> - the hypervisor did not set the LFENCE to serializing on the host > >>>> > >>>> - the hypervisor does not allow writing MSR_AMD64_DE_CFG > >>>> > >>>> That would bring the guest into a pretty bad state or am I missing > >>>> something essential here? > >>> What I did in Xen was to attempt to set it, then read it back and see.? > >>> If LFENCE still isn't serialising, using repoline is the only available > >>> mitigation. > >>> > >>> My understanding from the folk at AMD is that retpoline is safe to use, > >>> but has higher overhead than the LFENCE approach. > > Correct, the retpoline will work, it just takes more cycles. > > > >> That still does not help vs. rdtsc_ordered() and LFENCE_RDTSC ... > > Ok, I can add the read-back check before setting the feature flag(s). > > > > But... what about the case where the guest is a different family than > > hypervisor? If we're on, say, a Fam15h hypervisor but the guest is started > > as a Fam0fh guest where the MSR doesn't exist and LFENCE is supposed to be > > serialized? I'll have to do a rdmsr_safe() and only set the flag(s) if I > > can successfully read the MSR back and validate the bit. > > If your hypervisor is lying to you about the primary family, then all > bets are off.? I don't expect there will be any production systems doing > this. It's not that an unusual thing to do on qemu/kvm - to specify the lowest common denominator of the set of CPUs in your data centre (for any one vendor); it does tend to get some weird combinations. Dave > The user can get to keep both pieces if they've decided that this was a > good thing to try. > > ~Andrew -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK