From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3000FC2BA18 for ; Thu, 2 Apr 2020 23:04:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0ADAC2073B for ; Thu, 2 Apr 2020 23:04:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389171AbgDBXD4 (ORCPT ); Thu, 2 Apr 2020 19:03:56 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:39172 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729549AbgDBXD4 (ORCPT ); Thu, 2 Apr 2020 19:03:56 -0400 Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jK8rq-0004wg-2z; Fri, 03 Apr 2020 01:03:22 +0200 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id B84C0103A01; Fri, 3 Apr 2020 01:03:20 +0200 (CEST) From: Thomas Gleixner To: Nadav Amit Cc: Sean Christopherson , x86 , "Kenneth R . Crudup" , Paolo Bonzini , Fenghua Yu , Xiaoyao Li , Thomas Hellstrom , Tony Luck , Peter Zijlstra , Jessica Yu , Steven Rostedt , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , kvm , LKML , Doug Covelli Subject: Re: [PATCH 3/3] KVM: VMX: Extend VMX's #AC interceptor to handle split lock #AC in guest In-Reply-To: <08D90BEB-89F6-4D94-8C2E-A21E43646938@vmware.com> References: <20200402124205.334622628@linutronix.de> <20200402155554.27705-1-sean.j.christopherson@intel.com> <20200402155554.27705-4-sean.j.christopherson@intel.com> <87sghln6tr.fsf@nanos.tec.linutronix.de> <20200402174023.GI13879@linux.intel.com> <87h7y1mz2s.fsf@nanos.tec.linutronix.de> <20200402205109.GM13879@linux.intel.com> <87zhbtle15.fsf@nanos.tec.linutronix.de> <08D90BEB-89F6-4D94-8C2E-A21E43646938@vmware.com> Date: Fri, 03 Apr 2020 01:03:20 +0200 Message-ID: <87wo6xlccn.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org Nadav Amit writes: > Just to communicate the information that was given to me: we do intend to > fix the SLD issue in VMware and if needed to release a minor version that > addresses it. Having said that, there are other hypervisors, such as > virtualbox or jailhouse, which would have a similar issue. I'm well aware of that and even if VMWare fixes this, this still will trip up users which fail to install updates for one reason or the other and leave them puzzled. Maybe we just should not care at all. Despite that I might have mentioned it before: What a mess ... Thanks, tglx