From: Borislav Petkov <bp@alien8.de>
To: Alexey Kardashevskiy <aik@amd.com>
Cc: kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Venu Busireddy <venu.busireddy@oracle.com>,
Tony Luck <tony.luck@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sean Christopherson <seanjc@google.com>,
Sandipan Das <sandipan.das@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael Roth <michael.roth@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Jan Kara <jack@suse.cz>, Ingo Molnar <mingo@redhat.com>,
Huang Rui <ray.huang@amd.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH kernel v2 1/3] x86/amd: Cache values in percpu variables
Date: Tue, 10 Jan 2023 17:05:21 +0100 [thread overview]
Message-ID: <Y72MwWB+Nsphjqs8@zn.tnic> (raw)
In-Reply-To: <20221209043804.942352-2-aik@amd.com>
On Fri, Dec 09, 2022 at 03:38:02PM +1100, Alexey Kardashevskiy wrote:
Make that Subject:
"x86/amd: Cache debug register values in percpu variables"
to make it less generic and more specific as to what you're doing.
> Reading DR[0-3]_ADDR_MASK MSRs takes about 250 cycles which is going to
> be noticeable with the AMD KVM SEV-ES DebugSwap feature enabled.
> KVM is going to store host's DR[0-3] and DR[0-3]_ADDR_MASK before
> switching to a guest; the hardware is going to swap these on VMRUN
> and VMEXIT.
>
> Store MSR values passsed to set_dr_addr_mask() in percpu values
s/values/variables/
Unknown word [passsed] in commit message.
Use a spellchecker pls.
> (when changed) and return them via new amd_get_dr_addr_mask().
> The gain here is about 10x.
10x when reading percpu vars vs MSR reads?
Oh well.
> As amd_set_dr_addr_mask() uses the array too, change the @dr type to
> unsigned to avoid checking for <0.
I feel ya but that function will warn once, return 0 when the @dr number is
outta bounds and that 0 will still get used as an address mask.
I think you really wanna return negative on error and the caller should not
continue in that case.
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index c75d75b9f11a..9ac5a19f89b9 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -1158,24 +1158,41 @@ static bool cpu_has_amd_erratum(struct cpuinfo_x86 *cpu, const int *erratum)
> return false;
> }
>
> -void set_dr_addr_mask(unsigned long mask, int dr)
> +DEFINE_PER_CPU_READ_MOSTLY(unsigned long[4], amd_dr_addr_mask);
static
> +
> +static unsigned int amd_msr_dr_addr_masks[] = {
> + MSR_F16H_DR0_ADDR_MASK,
> + MSR_F16H_DR1_ADDR_MASK - 1 + 1,
- 1 + 1 ?
Why?
Because of the DR0 and then DR1 being in a different MSR range?
Who cares, make it simple:
MSR_F16H_DR0_ADDR_MASK,
MSR_F16H_DR1_ADDR_MASK,
MSR_F16H_DR1_ADDR_MASK + 1,
MSR_F16H_DR1_ADDR_MASK + 2
and add a comment if you want to denote the non-contiguous range but meh.
> + MSR_F16H_DR1_ADDR_MASK - 1 + 2,
> + MSR_F16H_DR1_ADDR_MASK - 1 + 3
> +};
> +
> +void set_dr_addr_mask(unsigned long mask, unsigned int dr)
> {
> - if (!boot_cpu_has(X86_FEATURE_BPEXT))
> + if (!cpu_feature_enabled(X86_FEATURE_BPEXT))
> return;
>
> - switch (dr) {
> - case 0:
> - wrmsr(MSR_F16H_DR0_ADDR_MASK, mask, 0);
> - break;
> - case 1:
> - case 2:
> - case 3:
> - wrmsr(MSR_F16H_DR1_ADDR_MASK - 1 + dr, mask, 0);
> - break;
> - default:
> - break;
> - }
> + if (WARN_ON_ONCE(dr >= ARRAY_SIZE(amd_msr_dr_addr_masks)))
> + return;
> +
> + if (per_cpu(amd_dr_addr_mask, smp_processor_id())[dr] == mask)
Do that at function entry:
int cpu = smp_processor_id();
and use cpu here.
> + return;
> +
> + wrmsr(amd_msr_dr_addr_masks[dr], mask, 0);
> + per_cpu(amd_dr_addr_mask, smp_processor_id())[dr] = mask;
> +}
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-10 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 4:38 [PATCH kernel v2 0/3] KVM: SEV: Enable AMD SEV-ES DebugSwap Alexey Kardashevskiy
2022-12-09 4:38 ` [PATCH kernel v2 1/3] x86/amd: Cache values in percpu variables Alexey Kardashevskiy
2023-01-10 16:05 ` Borislav Petkov [this message]
2023-01-12 5:21 ` Alexey Kardashevskiy
2023-01-12 11:12 ` Borislav Petkov
2022-12-09 4:38 ` [PATCH kernel v2 2/3] KVM: SEV: Enable data breakpoints in SEV-ES Alexey Kardashevskiy
2023-01-10 18:00 ` Borislav Petkov
2023-01-10 19:06 ` Tom Lendacky
2023-01-12 5:45 ` Alexey Kardashevskiy
2023-01-12 11:28 ` Borislav Petkov
2023-01-12 14:32 ` Tom Lendacky
2022-12-09 4:38 ` [PATCH kernel v2 3/3] x86/sev: Do not handle #VC for DR7 read/write Alexey Kardashevskiy
2023-01-10 20:04 ` Borislav Petkov
2023-01-09 5:20 ` [PATCH kernel v2 0/3] KVM: SEV: Enable AMD SEV-ES DebugSwap Alexey Kardashevskiy
2023-01-10 17:41 ` 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=Y72MwWB+Nsphjqs8@zn.tnic \
--to=bp@alien8.de \
--cc=Jason@zx2c4.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=aik@amd.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=brijesh.singh@amd.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=ray.huang@amd.com \
--cc=sandipan.das@amd.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--cc=venu.busireddy@oracle.com \
--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