Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp619962imm; Fri, 22 Jun 2018 02:19:50 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI99BygwYZQDU/xbo4orxzE6TFKDlH8wD7BCodJfNDM+RDvj8P3iJS9ryKLmpsWZ6P0mFbY X-Received: by 2002:a17:902:6f0f:: with SMTP id w15-v6mr837563plk.216.1529659190430; Fri, 22 Jun 2018 02:19:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529659190; cv=none; d=google.com; s=arc-20160816; b=Vse+eb20BEwQT3FvXVyZAT2FRlyQabS+ysEJFWGbfe35jm1xhStJrlnUps1LDUAUru CEJiVwzBULZ8y6ptK7zh68KDfxWrw+TUGQykdqez+JVjYEkHBfbNukgOMG5uVdBMNqjR hI3eSXc4DiXPqrjpbA6nBXTZyE9fKS+x2ixc+uY/d1RkGK+KBu5VyVidjSIC+5buzPkw i1+EPdgnhIABvnAbyWmhj29cmuU6gWI8ScWqa4pkJxuKhT/Wk9HYw5SeosU82oHoCaON Xi0KUI1VPYV4fdqQ9vzN5M8Ezz2C7Wx3eIOy8C+jEEex4QiK/K+4jdc2ZTsrRMOAV0Wt e//w== 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:from:date :arc-authentication-results; bh=6w6N3HThHNTTZBvFnkMAo54el6SxcsEuNTkM4XUU60Q=; b=lnLOqVWdRVxfULLIw/00uvJQO+DlrTHvwR58lNWs8mXw1a18a0lWCGRMtZqIfFWM/O l9jFC46q0T/KXZm4xbnEn3cUeQ1WHGEzR6LibG5wVYgRfCJe58gJGKYF0K0239NfYqkn 7WEHBU/zeMi1G+Uz9yTwXbDt0XpXDkrnPkJpj/28wYrUaytZphxmD7UkbWp3EWjt9Nsa SfDjeHBmuEXBMd3ri1RMHGIT5URFCbqTdQs83bbaqBnDaP4bIX/0MtV6drZuc/i5Kmlb Q1/WPMOr78oj7kpYAwuFYgiJo+lLKmk9dDUAVeysKdVMaref4DEMGtPBA1amqBH7PWPc 7WTA== 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 85-v6si6947364pfm.264.2018.06.22.02.19.35; Fri, 22 Jun 2018 02:19:50 -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 S1751305AbeFVJSu (ORCPT + 99 others); Fri, 22 Jun 2018 05:18:50 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:40949 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbeFVJSs (ORCPT ); Fri, 22 Jun 2018 05:18:48 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] 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 1fWID0-0002UO-Fw; Fri, 22 Jun 2018 11:18:22 +0200 Date: Fri, 22 Jun 2018 11:18:18 +0200 (CEST) From: Thomas Gleixner To: Fenghua Yu cc: Peter Zijlstra , Ingo Molnar , "H. Peter Anvin" , Ashok Raj , Dave Hansen , Rafael Wysocki , Tony Luck , Alan Cox , Ravi V Shankar , Arjan van de Ven , linux-kernel , x86 Subject: Re: [RFC PATCH 00/16] x86/split_lock: Enable #AC exception for split locked accesses In-Reply-To: <20180621220003.GD114883@romley-ivt3.sc.intel.com> Message-ID: References: <1527435965-202085-1-git-send-email-fenghua.yu@intel.com> <20180621193738.GA13636@worktop.programming.kicks-ass.net> <20180621201851.GC114883@romley-ivt3.sc.intel.com> <20180621220003.GD114883@romley-ivt3.sc.intel.com> 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, 21 Jun 2018, Fenghua Yu wrote: > Right. Code won't cover the early boot process. It only covers boot process > after the feature is enabled. That's broken. #AC wants to be enabled early as any other exception. The reason why you cannot enable it is because your exception handler is a total trainwreck, but it's even a trainwreck later on. > After disabling #AC split lock after catching #AC once, any future split > lock will not generate #AC any more. That's perfectly fine for the kernel. Issue a prominent warning and stuff gets fixed. Thanks, tglx