From: Fenghua Yu <fenghua.yu@intel.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>, "H Peter Anvin" <hpa@zytor.com>,
"Dave Hansen" <dave.hansen@intel.com>,
"Ashok Raj" <ashok.raj@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Michael Chan" <michael.chan@broadcom.com>,
"Ravi V Shankar" <ravi.v.shankar@intel.com>,
"Ricardo Neri" <ricardo.neri@intel.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
"x86" <x86@kernel.org>, Fenghua Yu <fenghua.yu@intel.com>
Subject: [PATCH v3 04/10] x86/split_lock: Align x86_capability to unsigned long to avoid split locked access
Date: Fri, 1 Feb 2019 21:14:45 -0800 [thread overview]
Message-ID: <1549084491-57808-5-git-send-email-fenghua.yu@intel.com> (raw)
In-Reply-To: <1549084491-57808-1-git-send-email-fenghua.yu@intel.com>
set_cpu_cap() calls locked BTS and clear_cpu_cap() calls locked BTR to
operate on bitmap defined in x86_capability.
Locked BTS/BTR accesses a single unsigned long location. In 64-bit mode,
the location is at:
base address of x86_capability + (bit offset in x86_capability % 64) * 8
Since base address of x86_capability may not aligned to unsigned long,
the single unsigned long location may cross two cache lines and
accessing the location by locked BTS/BTR introductions will trigger #AC.
To fix the split lock issue, align x86_capability to unsigned long so that
the location will be always within one cache line.
Changing x86_capability[]'s type to unsigned long may also fix the issue
because x86_capability[] will be naturally aligned to unsigned long. But
this needs additional code changes. So we choose the simpler solution
by enforcing alignment using __aligned(unsigned long).
Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
---
arch/x86/include/asm/processor.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index 33051436c864..eb8ae701ef65 100644
--- a/arch/x86/include/asm/processor.h
+++ b/arch/x86/include/asm/processor.h
@@ -93,7 +93,9 @@ struct cpuinfo_x86 {
__u32 extended_cpuid_level;
/* Maximum supported CPUID level, -1=no CPUID: */
int cpuid_level;
- __u32 x86_capability[NCAPINTS + NBUGINTS];
+ /* Unsigned long alignment to avoid split lock in atomic bitmap ops */
+ __u32 x86_capability[NCAPINTS + NBUGINTS]
+ __aligned(sizeof(unsigned long));
char x86_vendor_id[16];
char x86_model_id[64];
/* in KB - valid for CPUS which support this call: */
--
2.7.4
next prev parent reply other threads:[~2019-02-02 5:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 5:14 [PATCH v3 00/10] x86/split_lock: Enable #AC exception for split locked accesses Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 01/10] x86/common: Align cpu_caps_cleared and cpu_caps_set to unsigned long Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 02/10] drivers/net/b44: Align pwol_mask to unsigned long for better performance Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 03/10] wlcore: Align reg_ch_conf_pending and tmp_ch_bitmap " Fenghua Yu
2019-02-02 5:14 ` Fenghua Yu [this message]
2019-02-02 5:14 ` [PATCH v3 05/10] x86/clearcpuid: Support multiple clearcpuid options Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 06/10] x86/clearcpuid: Support feature flag string in kernel option clearcpuid Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 07/10] Change document for " Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 08/10] x86/setcpuid: Add kernel option setcpuid Fenghua Yu
2019-02-04 17:49 ` Thomas Gleixner
2019-02-04 19:05 ` Dave Hansen
2019-02-04 19:57 ` Borislav Petkov
2019-02-04 20:46 ` Dave Hansen
2019-02-04 21:40 ` Borislav Petkov
2019-02-04 22:14 ` Fenghua Yu
2019-02-05 6:10 ` Borislav Petkov
2019-02-04 23:24 ` Dave Hansen
2019-02-05 6:18 ` Borislav Petkov
2019-02-05 16:46 ` Dave Hansen
2019-02-05 17:09 ` Peter Zijlstra
2019-02-05 8:57 ` Peter Zijlstra
2019-02-05 13:15 ` Peter Zijlstra
2019-02-05 8:48 ` Peter Zijlstra
2019-02-05 15:19 ` Dave Hansen
2019-02-05 15:43 ` Borislav Petkov
2019-02-05 18:26 ` Fenghua Yu
2019-02-05 17:04 ` Peter Zijlstra
2019-02-10 19:20 ` Thomas Gleixner
2019-02-11 19:16 ` Fenghua Yu
2019-02-12 13:37 ` Peter Zijlstra
2019-02-12 13:51 ` Thomas Gleixner
2019-02-12 16:48 ` Peter Zijlstra
2019-02-12 16:50 ` Dave Hansen
2019-02-12 17:52 ` Yu, Fenghua
2019-02-04 21:09 ` Fenghua Yu
2019-02-05 8:51 ` Peter Zijlstra
2019-02-05 15:21 ` Dave Hansen
2019-02-05 15:34 ` Peter Zijlstra
2019-02-02 5:14 ` [PATCH v3 09/10] x86/split_lock: Define #AC for split lock feature Fenghua Yu
2019-02-04 18:41 ` Dave Hansen
2019-02-04 18:45 ` Fenghua Yu
2019-02-04 19:00 ` Dave Hansen
2019-02-04 19:03 ` Fenghua Yu
2019-02-02 5:14 ` [PATCH v3 10/10] x86/split_lock: Handle #AC exception for split lock Fenghua Yu
2019-02-04 11:00 ` kbuild test robot
2019-02-04 14:43 ` kbuild test robot
2019-02-11 10:53 ` Ingo Molnar
2019-02-11 18:10 ` Fenghua Yu
2019-02-13 8:14 ` Ingo Molnar
2019-02-13 14:37 ` Yu, Fenghua
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=1549084491-57808-5-git-send-email-fenghua.yu@intel.com \
--to=fenghua.yu@intel.com \
--cc=ashok.raj@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome