Received: by 10.192.165.148 with SMTP id m20csp3584933imm; Mon, 30 Apr 2018 02:53:59 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoDIs7coSeEfVMlvMCM7SnuLLoqecHG72ficV4UKoBVb5Hw9Mmq17UMOUC/GeSjT/FkfOF3 X-Received: by 2002:a65:588c:: with SMTP id d12-v6mr9443261pgu.408.1525082039885; Mon, 30 Apr 2018 02:53:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525082039; cv=none; d=google.com; s=arc-20160816; b=IoIeUkMro5caUiGL0f1fLUOdzMS5GTkntmRnTaPVXSCYkfrhRKqALT3j7zyPYFxVL6 plC9M1XI08IUJwkgX5AVVjPKhls7v/CDM/WJM3GMuefjYpmJSde66ebymnyQzOGYl+fx 008GVCgzUlvtIRE2mPZZD9OJlahGGseIvZyGaLHP84FKLL4fGrYeyGQ/voPIHoUcgdt7 0VTomAnvCZpyyOyfwB/2f1hV0C5Z6Bt7S/PMKkqq+72lYAuT1p5RmZdxVlyyfmrKkvdO 99xUQJlFPy/xldffsG0EaanGdKZLZg7RY485cD1/Kz2ODigZqiz+xa5EDZ/GzB6H/iiZ 3jXg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=wBNGB4QfFTQLyaTH3EcCoADffbv8Vh+hahsUJqLw6es=; b=Xmvvf0gdSuTTff9reU6sOZhA0TmOm6dAhVMQP5fHMZzIeQajFZAEKZvgkr9Ic+69a0 RsgsE6RCBMHW5BYrKPNCmhP7QvJLcasMYi2jj6SRF/sUFcQDU/uP+IruA6AqkA0T/HT9 VCTUPJUhKWuPsBH1AZoaVlXheZw/0dpbwok5klclH8nIKy3T4QEQVnegD2s0MkAzt+e/ X473q9SLDeJ+h/CaqHdWS2VPtxMpElV31IHrfDJb9UrcNG7mdjRyPgk9Cmn7BSVu2gpe BkNJEW2ZUZuMRlz9MF0ZIWyzUivQXw/OOyRpRwyvttWEnjXiS/nlCyN4xB/Vcb48dGGb Ms6w== 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 u193-v6si5980331pgc.186.2018.04.30.02.53.45; Mon, 30 Apr 2018 02:53:59 -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 S1752532AbeD3JxV (ORCPT + 99 others); Mon, 30 Apr 2018 05:53:21 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:57112 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751300AbeD3JxU (ORCPT ); Mon, 30 Apr 2018 05:53:20 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id EC71B15AD; Mon, 30 Apr 2018 02:53:19 -0700 (PDT) Received: from [10.1.70.34] (e112298-lin.cambridge.arm.com [10.1.70.34]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9217F3F587; Mon, 30 Apr 2018 02:53:18 -0700 (PDT) Subject: Re: [PATCH v2 0/6] arm64: provide pseudo NMI with GICv3 To: Joel Fernandes Cc: Linux ARM Kernel List , Linux Kernel Mailing List , mark.rutland@arm.com, marc.zyngier@arm.com, james.morse@arm.com, daniel.thompson@linaro.org, Joel Fernandes References: <1516190084-18978-1-git-send-email-julien.thierry@arm.com> From: Julien Thierry Message-ID: <07a0b8c1-3d87-0cae-61df-dbff782be301@arm.com> Date: Mon, 30 Apr 2018 10:53:17 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29/04/18 07:37, Joel Fernandes wrote: > On Wed, Jan 17, 2018 at 4:10 AM, Julien Thierry wrote: >> Hi, >> >> On 17/01/18 11:54, Julien Thierry wrote: >>> >>> This series is a continuation of the work started by Daniel [1]. The goal >>> is to use GICv3 interrupt priorities to simulate an NMI. >>> >> >> >> I have submitted a separate series making use of this feature for the ARM >> PMUv3 interrupt [1]. > > I guess the hard lockup detector using NMI could be a nice next step > to see how well it works with lock up detection. That's the main > usecase for my interest. However, perf profiling is also a strong one. > From my understanding, Linux's hardlockup detector already uses the ARM PMU interrupt to check whether some task is stuck. I haven't looked at the details of the implementation yet, but in theory having the PMU interrupt as NMI should make the hard lockup detector use the NMI. When I do the v3, I'll have a look at this to check whether the hardlockup detector works fine when using NMI. Cheers, -- Julien Thierry