[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200402144618.GC20730@hirez.programming.kicks-ass.net>
Date: Thu, 2 Apr 2020 16:46:18 +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 07:41:41AM -0700, Kenneth R. Crudup wrote:
>
> On Thu, 2 Apr 2020, Peter Zijlstra wrote:
>
> > 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?
>
> I just looked back at the syslog's copy of the kernel messages at the time
> I'd tried it, and no, I don't see that message.
Dang!
> > Could you slip me a copy of that thing by private mail?
>
> OK, gimme a couple of days though, I've gotta get a little work done.
> (Also, what "thing" exactly did you want?)
All the .ko files that come with vmware. I want to dig through them to
see why the VMLAUNCH detection thing isn't working.
Powered by blists - more mailing lists