From: "Luck, Tony" <tony.luck@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: RE: [PATCH] x86/split_lock: Make life miserable for split lockers
Date: Tue, 8 Mar 2022 17:12:33 +0000 [thread overview]
Message-ID: <fce8ed8b5ea94cdfa265e5dca01e0c11@intel.com> (raw)
In-Reply-To: <87mti0jxr8.ffs@tglx>
> I still do not like the inconsistent state between the TIF flag and the
> SLD MSR.
If I'm updating the "warn" option to work this way, I think I can make the TIF flag
and the code that updates the MSR in context switch go away. But need to work
though the patch to make sure I'm not missing something.
-Tony
next prev parent reply other threads:[~2022-03-08 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 1:27 [PATCH] x86/split_lock: Make life miserable for split lockers Tony Luck
2022-03-07 22:30 ` Thomas Gleixner
2022-03-08 0:37 ` Luck, Tony
2022-03-08 14:59 ` Thomas Gleixner
2022-03-08 17:12 ` Luck, Tony [this message]
2022-03-10 20:48 ` [PATCH v2 0/2] " Tony Luck
2022-03-10 20:48 ` [PATCH v2 1/2] x86/split_lock: " Tony Luck
2022-03-17 11:13 ` Pavel Machek
2022-03-17 16:27 ` Luck, Tony
2022-03-17 18:06 ` Thomas Gleixner
2022-03-17 22:21 ` David Laight
2022-03-17 22:40 ` Luck, Tony
2022-03-18 12:21 ` Fenghua Yu
2022-04-27 13:49 ` [tip: x86/splitlock] " tip-bot2 for Tony Luck
2022-03-10 20:48 ` [PATCH v2 2/2] x86/split-lock: Remove unused TIF_SLD bit Tony Luck
2022-04-27 13:49 ` [tip: x86/splitlock] " tip-bot2 for Tony Luck
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=fce8ed8b5ea94cdfa265e5dca01e0c11@intel.com \
--to=tony.luck@intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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