From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>,
Kishon VijayAbraham <Kishon.VijayAbraham@amd.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/barrier: Do not serialize MSR accesses on AMD
Date: Mon, 3 Jul 2023 14:54:19 +0200 [thread overview]
Message-ID: <20230703125419.GJ4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230622095212.20940-1-bp@alien8.de>
On Thu, Jun 22, 2023 at 11:52:12AM +0200, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
>
> AMD does not have the requirement for a synchronization barrier when
> acccessing a certain group of MSRs. Do not incur that unnecessary
> penalty there.
So you're saying that AMD tsc_deadline and x2apic MSRs *do* imply
ordering constraints unlike the Intel ones?
Can we pls haz a document link for that, also a comment?
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
> arch/x86/include/asm/barrier.h | 18 ------------------
> arch/x86/include/asm/processor.h | 19 +++++++++++++++++++
> 2 files changed, 19 insertions(+), 18 deletions(-)
Moving this code while changing it meant I had to look at it _3_ times
before I spotted you changed it :/
> diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
> index b216ac80ebcc..983406342484 100644
> --- a/arch/x86/include/asm/processor.h
> +++ b/arch/x86/include/asm/processor.h
> @@ -735,4 +735,23 @@ bool arch_is_platform_page(u64 paddr);
> #define arch_is_platform_page arch_is_platform_page
> #endif
>
> +/*
> + * Make previous memory operations globally visible before
> + * a WRMSR.
> + *
> + * MFENCE makes writes visible, but only affects load/store
> + * instructions. WRMSR is unfortunately not a load/store
> + * instruction and is unaffected by MFENCE. The LFENCE ensures
> + * that the WRMSR is not reordered.
> + *
> + * Most WRMSRs are full serializing instructions themselves and
> + * do not require this barrier. This is only required for the
> + * IA32_TSC_DEADLINE and X2APIC MSRs.
> + */
> +static inline void weak_wrmsr_fence(void)
> +{
> + if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
> + asm volatile("mfence; lfence" : : : "memory");
Both instructions are 3 bytes, a 6 byte nop would be better, no?
asm volatile (ALTERNATIVE("mfence; lfence;", "", X86_FEATURE_AMD));
or something ?
> +}
> +
> #endif /* _ASM_X86_PROCESSOR_H */
> --
> 2.35.1
>
next prev parent reply other threads:[~2023-07-03 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 9:52 [PATCH] x86/barrier: Do not serialize MSR accesses on AMD Borislav Petkov
2023-07-03 12:54 ` Peter Zijlstra [this message]
2023-07-04 7:46 ` Borislav Petkov
2023-07-04 9:01 ` Peter Zijlstra
2023-07-04 9:22 ` Borislav Petkov
[not found] ` <20231027153327.GKZTvYR3qslaTUjtCT@fat_crate.local>
[not found] ` <20231027153418.GLZTvYejCkXb03rArO@fat_crate.local>
2023-10-27 18:11 ` [PATCH 1/2] x86/alternative: Add per-vendor patching Peter Zijlstra
2023-10-27 18:25 ` Borislav Petkov
[not found] ` <20231027153458.GMZTvYou1tlK6HD8/Y@fat_crate.local>
2023-10-27 18:56 ` [PATCH 2/2] x86/barrier: Do not serialize MSR accesses on AMD Peter Zijlstra
2023-10-27 19:16 ` Borislav Petkov
2023-10-27 19:29 ` Borislav Petkov
2023-10-27 20:09 ` Andrew Cooper
2023-10-27 20:23 ` Borislav Petkov
2023-10-29 10:35 ` [PATCH -v3] " Borislav Petkov
2023-11-02 11:08 ` [PATCH 2/2] " Borislav Petkov
2023-11-13 8:56 ` [tip: x86/cpu] " tip-bot2 for Borislav Petkov (AMD)
2023-11-13 9:21 ` tip-bot2 for Borislav Petkov (AMD)
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=20230703125419.GJ4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kishon.VijayAbraham@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.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