[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200402143203.GJ20713@hirez.programming.kicks-ass.net>
Date: Thu, 2 Apr 2020 16:32:03 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Kenneth R. Crudup" <kenny@...ix.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>, x86@...nel.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
On Thu, Apr 02, 2020 at 06:43:19AM -0700, Kenneth R. Crudup wrote:
>
> 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, you're not seeing this:
+ pr_warn("disabled due to VMLAUNCH in module: %s\n", me->name);
fire when you load the vmware kernel module? Could you slip me a copy of
that thing by private mail?
Powered by blists - more mailing lists