Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp627547imm; Fri, 22 Jun 2018 02:30:07 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLWEdoTc0YGyjtaJ7pB+ACVGLvqOCwGJ9NWqOGfGNK23WCuPmEULSqFD81CXazy0RWj+qVh X-Received: by 2002:a17:902:15a8:: with SMTP id m37-v6mr864225pla.219.1529659807393; Fri, 22 Jun 2018 02:30:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529659807; cv=none; d=google.com; s=arc-20160816; b=ffaiX1m97Go1gurgztX84o00Tf4X0ML5gXoQyc0KBaeWwPZ7uluQLhLI1S3BIkJ4V8 CwOrT2CUhc2ZazHyJloiwHUaifwQMbbbiw/Dn9MUsvEY2h6rC0q/cfVqbWaHM/8gnFn8 U5QJrVgjTorGlH+Fy7SUrAoBdUXGjicVhSv+B334S6Hsa52ho3zVRElTXr3zYN7ec9y/ C2QMPlIBDNHOGoL7twMQOne7UktMAeITGpGjUrzRQ6Q06jYp7pvcVctBvEP+cTOkI4Zt iAyt9OjOta4MFWWEoR4hJ8w2930/4XeiLqCRTDqoau9IlVZGdDvgkUWXhtpA4TzFgBFk kjyg== 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=qr5Qraj6bRPw94/uj+IgkFwh3ZrYYjz8jM9sotIWhPs=; b=zsK/DGNDgJjAZyLIXSjnrNjTe7vb2vw8+MWMibW0CSVglTkZJESFWsMmaUkrR6mfbC YyQnPf0b7eTjudXF15xMJDJscv9vGlbX4AkmohHp2LU9Wr20QUIjFavJPvHpltnjZOQe lwFyN3QQRidCz8yHtzBv/oyg6BedHwvaKXOZbAN9ZiFPs3xrmb5BOXaBWO2Sn/W/JqYI MzLeKtCiZoOk7nzF3px6czTIPhIY8ptKMZ19Lbw/4FVlgnFEXWHBcMhxr6k6Zcy9FZqR zy9C6pWMk8URKkgjrzE1xlRq+BiP/KMUs6Lv51SMB1GA2bkoF9bSvveNxKrr9C9XKKFR mc4g== 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 m21-v6si7186694pls.217.2018.06.22.02.29.52; Fri, 22 Jun 2018 02:30:07 -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 S1751393AbeFVJ22 (ORCPT + 99 others); Fri, 22 Jun 2018 05:28:28 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:40974 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751191AbeFVJ21 (ORCPT ); Fri, 22 Jun 2018 05:28:27 -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 1fWIMg-0002bF-5K; Fri, 22 Jun 2018 11:28:22 +0200 Date: Fri, 22 Jun 2018 11:28:21 +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 knob for firmware is to choose continuing firmware execution > by disabling #AC split lock (default) or stopping firmware execution > by enabling #AC for split lock. Stopping firmware execution may be useful > in hard real time system to identify any split lock issue on the platform. There is no maybe on a real-time system. Either the thing is sane or it's not. There is no middle ground. The default has to be fail otherwise firmware wont be fixed ever. > So the control knobs may be useful for different scenarios, right? The control knobs are just helping to proliferate crap, so they are not useful, they are outright counterproductive. Thanks, tglx