Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2241491ybb; Thu, 2 Apr 2020 16:18:30 -0700 (PDT) X-Google-Smtp-Source: APiQypKW4eVhXmOxAl3ngr1Olwr8J+pGdcWDWgFO/oyAZmlrlCkBmXsy67xNqeOiSJi5eGffK4Ik X-Received: by 2002:a05:6830:1d67:: with SMTP id l7mr4132458oti.72.1585869510017; Thu, 02 Apr 2020 16:18:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585869510; cv=none; d=google.com; s=arc-20160816; b=DIWoRzr8KLFE8tVCN8rFl5RBE3kW/vAu7+sD9MIJc7iZpo5CencKR/+9nqp0oJW4Kp NWz/OsiVDAF9orjYiBsV2CSI3kvV9ym0uQJS+bpnPABYhcJrjLkVdaLnZcH/X3mHCwE+ 3jx5Jam2+Nj/L8c5/jZ3WPV4VBebtnjZofdvwWhOyhtmW4uwynMQb6E/f6xPAEIQIZ0Q CbatQ8hXt/9lRaBd963jSzBHUDiLBsYiqD7P2er127nx1W56aAy6jGAYinoYht+6ovzY VNWxbpx7GCQS2Sqv4epM4e6MOsKEd5tgWrY9NFaJ6pKiWmDSifuudOTrTmtveW744yq6 WFrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:reply-to:from:date; bh=fS1j5EklG0FcahgShB0to9gR+J15rJS9VCI5Nv5yM+8=; b=c2CDAm8q86JHTBs2auhYpsYlvNiMG0TJrY3k2gDd+VUcKIyXGUBcxgER0E74kzgDRQ NZhjKUtSBCVA4ugVrNTTC1aIwTQHWR6xyIqYxGMgBDBZXQaL0+q1wOuPgk44xVbvclas 8UstfAjX0xa23rwuIJFge/IG4/JhQ/w16YLd3D/adwye2DyjUSSeTAmeYVcUS+fwAewL 9xJA+pWGn5uy5s7qRc5x4eX2V+2OaqlUrRaB9jGJYdEepHzcZfcnTXkLCjvPCCsIuU8L tK9qffmH58/N0sn68dkDyTA3/LW//IkB8zFEf1FM36r7ZtWmijR8/BjVIuMGLAwWXEAt 2qjg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y110si2895954otb.71.2020.04.02.16.18.16; Thu, 02 Apr 2020 16:18:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389228AbgDBXQc (ORCPT + 99 others); Thu, 2 Apr 2020 19:16:32 -0400 Received: from mailbackend.panix.com ([166.84.1.89]:40484 "EHLO mailbackend.panix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730837AbgDBXQb (ORCPT ); Thu, 2 Apr 2020 19:16:31 -0400 Received: from xps-7390 (c-73-241-154-233.hsd1.ca.comcast.net [73.241.154.233]) by mailbackend.panix.com (Postfix) with ESMTPSA id 48tf8C3bT6z1B4f; Thu, 2 Apr 2020 19:16:26 -0400 (EDT) Date: Thu, 2 Apr 2020 16:16:25 -0700 (PDT) From: "Kenneth R. Crudup" Reply-To: "Kenneth R. Crudup" To: Steven Rostedt cc: Nadav Amit , Thomas Gleixner , Sean Christopherson , x86 , Paolo Bonzini , Fenghua Yu , Xiaoyao Li , Thomas Hellstrom , Tony Luck , Peter Zijlstra , Jessica Yu , 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: <20200402190839.00315012@gandalf.local.home> Message-ID: 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> <20200402190839.00315012@gandalf.local.home> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2 Apr 2020, Steven Rostedt wrote: > If we go the approach of not letting VM modules load if it doesn't have the > sld_safe flag set, how is this different than a VM module not loading due > to kabi breakage? Why not a compromise: if such a module is attempted to be loaded, print up a message saying something akin to "turn the parameter 'split_lock_detect' off" as we reject loading it- and if we see that we've booted with it off just splat a WARN_ON() if someone tries to load such modules? -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley