[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1910161651290.2046@nanos.tec.linutronix.de>
Date: Wed, 16 Oct 2019 17:03:17 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: David Laight <David.Laight@...LAB.COM>
cc: 'Paolo Bonzini' <pbonzini@...hat.com>,
Xiaoyao Li <xiaoyao.li@...el.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
H Peter Anvin <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Dave Hansen <dave.hansen@...el.com>,
Radim Krcmar <rkrcmar@...hat.com>,
Ashok Raj <ashok.raj@...el.com>,
Tony Luck <tony.luck@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
Ravi V Shankar <ravi.v.shankar@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
x86 <x86@...nel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: RE: [PATCH v9 09/17] x86/split_lock: Handle #AC exception for split
lock
On Wed, 16 Oct 2019, David Laight wrote:
> For the smt case, can you make #AC enable a property of the process?
> Then disable it on the core if either smt process requires it be disabled?
That would be feasible if the logic of the TEST_CTRL_MSR would be AND, but
it's OR.
Thread0 #AC-EN Thread1 #AC-EN #AC enabled on core
0 0 0
1 0 1
0 1 1
1 1 1
So in order to do flips on VMENTER you'd need to IPI the other thread and
handle all the interesting corner cases.
The 'Rescue SMT' mitigation stuff on top of core scheduling is ugly enough
already, but there the state can be transitionally 'unmitigated' while with
#AC you run into trouble immediately if the transitional state is ON at the
wrong point.
Thanks,
tglx
Powered by blists - more mailing lists