Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp42678imm; Thu, 21 Jun 2018 13:34:25 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLwknb4xsqR88CecmO88R7nwsDoK9BdNNaGnBgEY6ep1uvObLlaN9zePB9Z7avuvLxcw7DG X-Received: by 2002:a17:902:be0b:: with SMTP id r11-v6mr30839566pls.182.1529613265487; Thu, 21 Jun 2018 13:34:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529613265; cv=none; d=google.com; s=arc-20160816; b=iUlTcTcFPCv4dGPvKDgT2HkvawvkWkRK1C5g6QzsNR3MCAI9kEjIuhtoZCsxqkBGQF czXN4ZAWCgNTLMGIXVk9QyOL5oFuhH0Aq7bXJpK9v2oUkUE+T9gwbV3E759suTPyUGct DrEIRty0NK5g6ADpbMOZgXCUZU0puWvjjiIfopMTJ+ne1dGfeKgeiXiP72qibLSkudsl voVvqrWG9HdRx7vIDVFyyU4WxH1t+RwK/BzCyrteWXW6h+euzo2uQOX76D3UGvHzEM1p bFaRdTOiiB7YJG5I74p0/DfpHaKel6XDBLqjDX8hGrfkTjhRFELK6dJlydY7uutd3t2F 25Ug== 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=I5na7chP4pdZOwYvOwnTrRrqcOHEXVSY3r/lr7eWWbY=; b=fu+g803jKx+MJybQ96R6Ta2rqRUmvi04qV4KJQeRnsINS93orNMtd4OxvDgPLJuuiS xohy0VmuWYtZ3POh9eP1ubqG6M9OJkWOTzVdl+N2C0iRlTy6oYDV/Stb/vDhhEaAyB2X yRpEma3+S6jjU0bB6NJZCrhadgcgKCwO+ZDREcFKdlIAfOAkVYeu/KHTRu4+lkRNclln lEC0i0BTnT28JT9e/WlwRJpSFh4HZ+8tpSz3FeuCyGqqJgWFaFh6Es+iaQ2Avmp6PRWI ulZkDoK+cN8CnmZP6GYmu/k9FXrIsbiOOeLiLLctdVyLSWCq1pytrDnzUlfofeAjkF8n oczQ== 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 d11-v6si5577363pla.184.2018.06.21.13.34.11; Thu, 21 Jun 2018 13:34:25 -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 S933640AbeFUUdF (ORCPT + 99 others); Thu, 21 Jun 2018 16:33:05 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:39777 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932899AbeFUUdE (ORCPT ); Thu, 21 Jun 2018 16:33:04 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fW6GI-0004A3-Ba; Thu, 21 Jun 2018 22:32:58 +0200 Date: Thu, 21 Jun 2018 22:32:57 +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: <20180621201851.GC114883@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> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: 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: > On Thu, Jun 21, 2018 at 09:37:38PM +0200, Peter Zijlstra wrote: > > On Sun, May 27, 2018 at 08:45:49AM -0700, Fenghua Yu wrote: > > > Currently we can trace split lock event counter for debug purpose. But > > > > How? A while ago I actually tried that, but I could not find a suitable > > perf event. > > The event name is called sq_misc.split_lock. It's been supported in perf > already. So the obvious question is why not simply use that counter and capture the IP which triggers the event? I can see that this wont cover the early boot process, but there it's enough to catch #AC once, yell loudly and then disable the thing. I'm not seing the value of adding 1000 lines of code with lots of control knobs. I might be missing something though and am happy to be educated. Thanks, tglx