[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875zeinecr.fsf@nanos.tec.linutronix.de>
Date: Thu, 02 Apr 2020 16:37:08 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "Kenneth R. Crudup" <kenny@...ix.com>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
"Peter Zijlstra \(Intel\)" <peterz@...radead.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Jessica Yu <jeyu@...nel.org>,
Fenghua Yu <fenghua.yu@...el.com>,
Xiaoyao Li <xiaoyao.li@...el.com>,
Nadav Amit <namit@...are.com>,
Thomas Hellstrom <thellstrom@...are.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Tony Luck <tony.luck@...el.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [patch 0/2] x86: Prevent Split-Lock-Detection wreckage on VMX hypervisors
"Kenneth R. Crudup" <kenny@...ix.com> writes:
> On Thu, 2 Apr 2020, Thomas Gleixner wrote:
>
>> As Peter and myself don't have access to a SLD enabled machine, the
>> KVM/VMX part is untested. The module scan part works.
>
> I just applied both of these patches to my (Linus' tip) tree, and unfortunately
> VMWare still hangs if split_lock_detect= is set to anything but "off".
>
> Was there anything else I'd needed to do?
Hmm. Not really. Does dmesg show the warning when the VMWare module loads?
Something like:
x86/split lock detection: disabled due to VMLAUNCH in module: ....
Thanks,
tglx
Powered by blists - more mailing lists