Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp622357imm; Fri, 22 Jun 2018 02:23:11 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI1S+a/ZP8bSURAJQ5eSrYiAECY7HOKMRehnCs9288cz3f4Z8FpUlGaJ0OX1dTVj3+kOKrW X-Received: by 2002:a63:920c:: with SMTP id o12-v6mr697868pgd.233.1529659390982; Fri, 22 Jun 2018 02:23:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529659390; cv=none; d=google.com; s=arc-20160816; b=EwC6zEoLKoilXbEj4vjGSbvkCZCsBGxBo3USf8FanJZTMNXB7fWUj4l5/rNeH9zkC2 9RrYM3/op0LtghjXH4xCJ9pGhtbsst7YDZbdRU27jvke5ZuQvJoxK+g7kPUnhn29ul+9 hBH8H6FgcBou8y1nD2Ql+EQ69TRxo/qdvCvKHFZviI8zaVC+NhorHIIc+cB2aFIeVCvC PJh0rh+Ukp1Gz1i7lHHgG65a4KKFYUIPOBp3HlzDr7kWtvyCCsH29z4DYxs7CJVnDX1Q KR64Fl3c0aeq5N1jBUJO6M2dFCrUzfAu0Mq8y5ZZX4F3d1BklRZMhw2f8HMiSUhBa/Ee q60A== 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=CjugrXABOZwp6IFBtQcYIyeT6hU4a5DIGDtj31l6n4o=; b=YbV58t9W88IOnxgTa30HnM2mO/aC8ze2zZzdF2pem1wh09vI8+HnhVnVhm+XKeX0FC WZ4/JI4ZJ51WACSDzQ31PWrMYuZ8rd0Lw6UIXhoX396HjrdCOWGmaXKA7QFr/Ho+38Gb hABcTvWogQPmW7q/pcMLZQScmwxfvOsyNx8F1NZZcdfyyWPdwlPY0c7dUZ88jAZAwrT5 FACeQSuGr0THfdnYBp/OtR0YPn5pH53dnEH0/y4N/7sL7vMhLtEY0qLV5ILT5RVyN4uT LfhN31lHvcB6Dbol7D6NNjl9OwbalHnuG59b2MPaOHhE41rYfuh6XJxZ4Z1ixLBUYeqP KNlQ== 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 i3-v6si6963158pld.189.2018.06.22.02.22.55; Fri, 22 Jun 2018 02:23:10 -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 S1751305AbeFVJWR (ORCPT + 99 others); Fri, 22 Jun 2018 05:22:17 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:40957 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbeFVJWQ (ORCPT ); Fri, 22 Jun 2018 05:22:16 -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 1fWIGh-0002Vr-0z; Fri, 22 Jun 2018 11:22:11 +0200 Date: Fri, 22 Jun 2018 11:22:09 +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: > The control knobs allow sysadmin to handle #AC for split lock in different > scenarios and usages. > > The control knob for kernel is to choose re-executing the faulting > instruction (default) or kernel panic. Kernel panic may be useful in hard > real time which has less tolerant to bad performance. That's nonsense, really. 1) The re-executing mechanism is broken and totally useless 2) Panicing a real-time system just due to a single #AC is total overkill. Real-Time systems care very much about proper safe state transitioning. Panic is surely a safe state, but so is power off. But neither of them qualifies as proper state transitioning. Thanks, tglx