Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4184696pxf; Tue, 30 Mar 2021 01:07:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzliqCGdxKVnjoERtCOx868XCdrYkZtcZR1pMuSNc0LGcbWoriMgiCYqQ7yEZmP0bsfBlKg X-Received: by 2002:a05:6402:32a:: with SMTP id q10mr32090831edw.15.1617091677689; Tue, 30 Mar 2021 01:07:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617091677; cv=none; d=google.com; s=arc-20160816; b=ZZ2ygeI3BYpZGtZF4HiPfzDQocJRlCBv2RAJv4ukgG5wUQ0UoDEGWgRERPczbGQdZX LPjauEVsPx6fYjzflKRxEI0JgYf9n0Opy2A7xMhPNUr8EOlJIoUNeQK9ApFy4hXRMB8L 2u1EZkumhhqsr1Y+kZibIOaFAKG26Jd8TClYp0501Moe9nbAEfI8f22RFJKI3XgHPfzv +b3Xs6UH5jDlAuEpaA4Hflc2hwxLW955DTBbWYMsHj1CHnrzHt7CADLROIzJrVnostZ2 jiB8t/h4faPXsyilXfmRht0W4bJ3YAcAgbb5xbl1xSl6hakroGsvEOwELZV0iy6XGwIK r2bQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=R9Uv3zFMSlkvL5Lb1uxQtkvDLMjJwKF4TXBD9pyBsHI=; b=L+qxl7eIGcgJfpLqDOYBf76LXIP+qykPe0VVN9KGAD+1r725b8d0Pwm6JBP5Dc4ha0 7aulSetSKr0AYbotM6ClobQhrg4wCJnoVH9FRy23wBuxzID4oIyjCK95WlwbAjFCJttS DhbifvdgNOE9p+a0kJrwDgKzo28RJHTyhZ7MtjeS6Ea/oQ7o01h3WLmHrrX15cn854hb 5RyKLcGXbI4oeDui/tDEzdHAFC6VD3VmvoT+1bjyVKgTVAFBp1/xRZnK/HW9gMTafqBb Px82MDMxMT8Qb7VePRAAiQ+AH1CLmu69nN0GjjK3Y2W/FJPH5VpViTEvL61LGr/FSL+d iqHA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f16si14493639eds.608.2021.03.30.01.07.29; Tue, 30 Mar 2021 01:07:57 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=mediatek.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231394AbhC3IGe (ORCPT + 99 others); Tue, 30 Mar 2021 04:06:34 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:37512 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S231301AbhC3IG2 (ORCPT ); Tue, 30 Mar 2021 04:06:28 -0400 X-UUID: 919b34e3c4c6490ca2e2fc9341e452c8-20210330 X-UUID: 919b34e3c4c6490ca2e2fc9341e452c8-20210330 Received: from mtkmbs10n2.mediatek.inc [(172.21.101.183)] by mailgw02.mediatek.com (envelope-from ) (Cellopoint E-mail Firewall v4.1.14 Build 0819 with TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256/256) with ESMTP id 334879961; Tue, 30 Mar 2021 16:06:17 +0800 Received: from MTKCAS06.mediatek.inc (172.21.101.30) by mtkmbs08n1.mediatek.inc (172.21.101.55) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 30 Mar 2021 16:06:15 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by MTKCAS06.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Tue, 30 Mar 2021 16:06:15 +0800 From: Lecopzer Chen To: CC: , , , , , , , , , , , Subject: Re: [PATCH v5] arm64: Enable perf events based hard lockup detector Date: Tue, 30 Mar 2021 16:06:15 +0800 Message-ID: <20210330080615.21938-1-lecopzer.chen@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Hi Will, Mark, > > On Fri, 15 Jan 2021 at 17:32, Sumit Garg wrote: > > > > With the recent feature added to enable perf events to use pseudo NMIs > > as interrupts on platforms which support GICv3 or later, its now been > > possible to enable hard lockup detector (or NMI watchdog) on arm64 > > platforms. So enable corresponding support. > > > > One thing to note here is that normally lockup detector is initialized > > just after the early initcalls but PMU on arm64 comes up much later as > > device_initcall(). So we need to re-initialize lockup detection once > > PMU has been initialized. > > > > Signed-off-by: Sumit Garg > > --- > > > > Changes in v5: > > - Fix lockup_detector_init() invocation to be rather invoked from CPU > > binded context as it makes heavy use of per-cpu variables and shouldn't > > be invoked from preemptible context. > > > > Do you have any further comments on this? > > Lecopzer, > > Does this feature work fine for you now? This really fixes the warning, I have a real hardware for testing this now. but do we need to call lockup_detector_init() for each cpu? In init/main.c, it's only called by cpu 0 for once. BRs, Lecopzer