Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2479893ybk; Sun, 17 May 2020 23:30:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxuKOsFo31z77x6WxHHVaZ9OmcbB2nmVSgYOruum83jgHs66Z0NvYxcC7oGj1Qc3zXN8ND0 X-Received: by 2002:a17:906:4e13:: with SMTP id z19mr12822126eju.339.1589783436517; Sun, 17 May 2020 23:30:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589783436; cv=none; d=google.com; s=arc-20160816; b=hY2VKApcqh0iApHmRhoD1Y1hRiYrws9ItBPGvRlUnV3STNTCGvVEoaE16/bFU78Ehm Ggv26FHgLRwilBjr5QidvkCYatFMXWLGgFVnCLaqLfawh/8NIOPyanwA9KOZ4GYh3gC2 D+lhSAZZ+ofX4CCXeOsSwxpSMWhG7yHxOmfDggKK+v18JDyF+1JlJi18N9Z75PagTV4F MT06p0bF/20x93Ept+INjiAb3gAMr6vcKNwL8S/8GnS1zFSp67d7E4+GLpTM5UQgfFCp pLUPVcLTGl7i3+4Czw6h7EcJKQqRn2m6Xb5wY4voNLjyHo+VX4zx+1Q7XznTJqNHOBEU kNGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=sqEbuUUC6vd4Sa66d08NNo4B0txnWr9aDhBTPjvmYJ8=; b=rCz0x0PdcLU3EqaSm+JCusnF4AwhzIS46z8N8cuBAIXyktoOlXYOMcBT83aq6rauz7 icG3eo6PTCDqiA11wnSCtXCKpx8Q7/j1PITYSyognrqfuogJNUvoWvw8ODk9jbns5oSe WAcWhzbhQIuO72BrxMlyl8hHHkGLfWvGePSNVFuSWKh5BDQlRkXa0u6kDu7+NakQryL4 pnqCHMsz9IGSlu0736RnwV8etmBk0XJ1rxm17ZrIyh/1EAMyo5507PFBUQ1Am0bBlPoW Tv19+zWTNv91kzdkFY7EmSG7wREUrHkK2itV89aOs9BlhenrOHTkg5uyckjcnoaPXmlF i5qw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=X3xPJZtp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m16si3040084edq.126.2020.05.17.23.30.13; Sun, 17 May 2020 23:30:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=X3xPJZtp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726573AbgERG0P (ORCPT + 99 others); Mon, 18 May 2020 02:26:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726378AbgERG0O (ORCPT ); Mon, 18 May 2020 02:26:14 -0400 Received: from mail-pj1-x1044.google.com (mail-pj1-x1044.google.com [IPv6:2607:f8b0:4864:20::1044]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A5681C061A0C for ; Sun, 17 May 2020 23:26:13 -0700 (PDT) Received: by mail-pj1-x1044.google.com with SMTP id nu7so2110601pjb.0 for ; Sun, 17 May 2020 23:26:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=sqEbuUUC6vd4Sa66d08NNo4B0txnWr9aDhBTPjvmYJ8=; b=X3xPJZtpZ+1rw0mFFaFkJlO44v9hlmZCh+zJeg9JgWkvvtlZOPOXfPTsK01TqHRmgr oLDaaMSe5J/NidcHTI+itTPoh7TsAZJ8xd1iMI/5nltzxBJzppACR5SdjJtxw56JwHOw o03MowbtjoB6XR0HlELcpQFaI4lE3F51CCdp7GsHRTzIkA9AbO83juZNwf7dyJUCZ6XE 8tLUzs9bkvSuBs1PbvkDXilxaEDWIU8TN4tCfSKuYG/RzOUCBWw64ffJSU+Ev3OuqusW OBGzjpi33ZJCL4CBKM1hQ6CQApI7CgYKkJqn35zU2xE0cW0x574QIJ+lmAVo4IiUKn8A QSvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sqEbuUUC6vd4Sa66d08NNo4B0txnWr9aDhBTPjvmYJ8=; b=Kasm97qA8JUh/mLIUyNio1iDfTzTlM6DS5TMGcuXtfYZPpT1flQwu2S2Y3Vn+QJD/4 bDO6cwxuuYqgiby1+x5aQsS+uEKlT4PBo9G7uvQmGp2718sKGVrHJKDPVyhT1DneSrlu 1LaS19zNquPsdOxk3mMuLWUhlKhR63q8/w4/J29i7A/ImeAEXTHb49BhXxb8CG32qxfG o2A6b1vGuetMwk4l2RJNGEf6HirkALRYBLczChQSi/RBT497oj5dYX+MU4bzGdE5tdYb Bvh8cKgxZV04sKQXPHFXwXM+nJNRMLFIAX6gRs/A0/QOjwLBsjr5sGjGfa6/4iprXC/5 Q2vQ== X-Gm-Message-State: AOAM532ZFHn0/sOX7dWxn6wihe1zJSf/sjTm9V8I+RBwmkxIZePVWuZI KfEofspOfx6lzZYCb5RAHDlBXfdVGNujyHEIrB8= X-Received: by 2002:a17:902:b088:: with SMTP id p8mr15507720plr.123.1589783173163; Sun, 17 May 2020 23:26:13 -0700 (PDT) MIME-Version: 1.0 References: <20200516124857.75004-1-lecopzer@gmail.com> In-Reply-To: From: Lecopzer Chen Date: Mon, 18 May 2020 14:26:00 +0800 Message-ID: Subject: Re: [PATCH 0/3] arm64: perf: Add support for Perf NMI interrupts To: Sumit Garg Cc: julien.thierry.kdev@gmail.com, Linux Kernel Mailing List , Mark Rutland , Jian-Lin Chen , alexander.shishkin@linux.intel.com, Catalin Marinas , jolsa@redhat.com, acme@kernel.org, Peter Zijlstra , mingo@redhat.com, linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com, namhyung@kernel.org, Will Deacon , yj.chiang@mediatek.com, linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org HI Sumit, Thanks for your information. I've already implemented IPI (same as you did [1], little difference in detail), hardlockup detector and perf in last year(2019) for debuggability. And now we tend to upstream to reduce kernel maintaining effort. I'm glad if someone in ARM can do this work :) Hi Julien, Does any Arm maintainers can proceed this action? This is really useful in debugging. Thank you!! [1] https://lkml.org/lkml/2020/4/24/328 Lecopzer Sumit Garg =E6=96=BC 2020=E5=B9=B45=E6=9C=8818=E6= =97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=881:46=E5=AF=AB=E9=81=93=EF=BC=9A > > + Julien > > Hi Lecopzer, > > On Sat, 16 May 2020 at 18:20, Lecopzer Chen wrote: > > > > These series implement Perf NMI funxtionality and depends on > > Pseudo NMI [1] which has been upstreamed. > > > > In arm64 with GICv3, Pseudo NMI was implemented for NMI-like interruts. > > That can be extended to Perf NMI which is the prerequisite for hard-loc= kup > > detector which had already a standard interface inside Linux. > > > > Thus the first step we need to implement perf NMI interface and make su= re > > it works fine. > > > > This is something that is already implemented via Julien's patch-set > [1]. Its v4 has been floating since July, 2019 and I couldn't find any > major blocking comments but not sure why things haven't progressed > further. > > Maybe Julien or Arm maintainers can provide updates on existing > patch-set [1] and how we should proceed further with this interesting > feature. > > And regarding hard-lockup detection, I have been able to enable it > based on perf NMI events using Julien's perf patch-set [1]. Have a > look at the patch here [2]. > > [1] https://patchwork.kernel.org/cover/11047407/ > [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2020-May/732227= .html > > -Sumit > > > Perf NMI has been test by dd if=3D/dev/urandom of=3D/dev/null like the = link [2] > > did. > > > > [1] https://lkml.org/lkml/2019/1/31/535 > > [2] https://www.linaro.org/blog/debugging-arm-kernels-using-nmifiq > > > > > > Lecopzer Chen (3): > > arm_pmu: Add support for perf NMI interrupts registration > > arm64: perf: Support NMI context for perf event ISR > > arm64: Kconfig: Add support for the Perf NMI > > > > arch/arm64/Kconfig | 10 +++++++ > > arch/arm64/kernel/perf_event.c | 36 ++++++++++++++++++------ > > drivers/perf/arm_pmu.c | 51 ++++++++++++++++++++++++++++++---- > > include/linux/perf/arm_pmu.h | 6 ++++ > > 4 files changed, 88 insertions(+), 15 deletions(-) > > > > -- > > 2.25.1 > > > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel