Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
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
Thread-Topic: [PATCH] x86/split_lock: Make life miserable for split lockers
Thread-Index: AQHYI52JusZbuGFIckyHL7QBBN4/aay1JM6A//+ddgCAAXbhgP//nlcg
Date:   Tue, 8 Mar 2022 17:12:33 +0000
Message-ID: <fce8ed8b5ea94cdfa265e5dca01e0c11@intel.com>
References: <20220217012721.9694-1-tony.luck@intel.com> <877d95l7jo.ffs@tglx>
 <YialXwpbED5kAUaZ@agluck-desk3.sc.intel.com> <87mti0jxr8.ffs@tglx>
In-Reply-To: <87mti0jxr8.ffs@tglx>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-reaction: no-action
dlp-version: 11.6.401.20
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk

> 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 wo=
rk
though the patch to make sure I'm not missing something.

-Tony