Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp347230imu; Fri, 16 Nov 2018 03:34:18 -0800 (PST) X-Google-Smtp-Source: AJdET5dqVxh7nZDEJDD5y59cpmk6/7ZvwzWQFG5u8S2wQwXFeDrpKrc0gHdv1mSwGTrne5SIamj6 X-Received: by 2002:a17:902:6a8b:: with SMTP id n11-v6mr10581813plk.311.1542368058783; Fri, 16 Nov 2018 03:34:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542368058; cv=none; d=google.com; s=arc-20160816; b=F3PUtYuwkyqebK6gIwmEQX8an1a1CozeUMLLQkx/hwb4WQHJ9GcP/UyWNTgRluhG3N 7RLwqmMIHzXaYGsB/tqWk7sahAsLDqdj96VfEmgdfAkw8S503U/kk5cw12J+rayd4CPy iExco0XMSlpQntq9aglKJtICEAuILt4sruzwGlELRRaUpEDvv+CVgIOD0sErRN0KEJEa gFEcLQNJYW4U8VfheU2MlgXXmmd3NBpYibgX1FdxHVTdgzv07InkizER8pORUqNgmnco A2yncJFSm8SBbXvty3FfxNS+6jW4TEy1MMcAyEHzeYaSt4Ylb1kxpd28bW/OIrf/qhwG DwVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:mime-version:references :in-reply-to:subject:cc:to:from; bh=KdCU9cR/6rrVpfR2iOMAxz+zNi1nTDl2D3H0I5Jmhqg=; b=jYAn6VjndJMMFtMpTv3LcqWEprxXXfiZxTlHW0/ZS09rU9fjYA59456KhzxYdWtWfa 7oznWBOgbvgy8u1IM3AvmpXpOQdmp7vkocYkXS4ecdAyCSxqgVwXmJVrKMOmCnovomKq DTifvCYKxXqdwARQ+9oLDKV1iyEtgzmYP6O+QqpY4p1o/wlGJLAYUCH0q+L/5mXN8Wqq HMuuP7d0q9DOIAUIxsN2ZLxJbb/uwb2vOZdMJ9EzSBBm5g4awT4X7jN1NBI9i/VdaUa7 nz6JIiN5PSSYlULgDJe1LertEWA8hUr0YtyyxMINl/dG7MF4LZrDeqFHSrHZWcWKx77W QQJQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vt.edu Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t3-v6si32877839pfb.247.2018.11.16.03.34.02; Fri, 16 Nov 2018 03:34:18 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=vt.edu Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389507AbeKPVpP (ORCPT + 99 others); Fri, 16 Nov 2018 16:45:15 -0500 Received: from outbound.smtp.vt.edu ([198.82.183.121]:55810 "EHLO omr2.cc.vt.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727638AbeKPVpP (ORCPT ); Fri, 16 Nov 2018 16:45:15 -0500 Received: from mr2.cc.vt.edu (inbound.smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id wAGBXG7X011281 for ; Fri, 16 Nov 2018 06:33:16 -0500 Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) by mr2.cc.vt.edu (8.14.7/8.14.7) with ESMTP id wAGBXBiM015610 for ; Fri, 16 Nov 2018 06:33:16 -0500 Received: by mail-qk1-f197.google.com with SMTP id n68so50156269qkn.8 for ; Fri, 16 Nov 2018 03:33:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:date:message-id; bh=KdCU9cR/6rrVpfR2iOMAxz+zNi1nTDl2D3H0I5Jmhqg=; b=hDtw5Ldl8ILcQQfYYkL349A/E8Iyi8gReuD5iU1aR3R5fy1kJ0Q+IQbEcuS34TeXOy GN0VyDQXpnhxATKTFf1yKUJkQ7KKBpMJcjiK9DqGO9z5XNXcPLqgevdbFKbwwuHoBP6F fI4tCVRDGQ1KVUukBu+mFdGGOniUxhZSPdR5pFGkeUpimlBwZ/if3g+O779CuIft30T3 cel9XQYy7hQeKFQvdM/z034AHfaVwoaZF5JKc1p/RxRcqrVWxDAy8GrhUt2TpYvFWxt9 qNZPMGhJfzLxHDjHUcVeifSrg+VKvJhmaUru5zg7gMgFuycgjsLpoF99A1f8k1LXLPDB +naQ== X-Gm-Message-State: AGRZ1gJFvwfm3VOw0LyOswl52dLyhC+x2PklWoz+HbbaWOdBhNc547q5 VB9uUdIHIE4dZMGeJ0W3XOAuOZKycjga0FeEttVkWWiRxITMEoBAxN0CQG0sdWE+mAYU/bsew5/ pkqw7D46I2wwysnEcmOSJFVwkf6CwBI8e07c= X-Received: by 2002:ac8:3038:: with SMTP id f53mr9542882qte.45.1542367991088; Fri, 16 Nov 2018 03:33:11 -0800 (PST) X-Received: by 2002:ac8:3038:: with SMTP id f53mr9542862qte.45.1542367990750; Fri, 16 Nov 2018 03:33:10 -0800 (PST) Received: from turing-police.cc.vt.edu ([2601:5c0:c001:4340::be3]) by smtp.gmail.com with ESMTPSA id 24sm29304864qkp.65.2018.11.16.03.33.08 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 16 Nov 2018 03:33:09 -0800 (PST) From: valdis.kletnieks@vt.edu X-Google-Original-From: Valdis.Kletnieks@vt.edu X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev To: Pintu Agarwal cc: open list , linux-arm-kernel@lists.infradead.org, Russell King - ARM Linux , kernelnewbies@kernelnewbies.org, Jungseok Lee , catalin.marinas@arm.com, will.deacon@arm.com, Takahiro Akashi , mark.rutland@arm.com, Sungjinn Chung Subject: Re: [ARM64] Printing IRQ stack usage information In-reply-to: References: <28496.1542300549@turing-police.cc.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Nov 2018 06:33:08 -0500 Message-ID: <49219.1542367988@turing-police.cc.vt.edu> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Nov 2018 11:44:36 +0530, Pintu Agarwal said: > > If your question is "Did one > > of the CPUs blow out its IRQ stack (or come close to doing so)?" there's better > > approaches. > > > Yes, exactly, this is what the main intention. > If you have any better idea about this approach, please refer me. > It will be of great help. Look at the code controlled by '#ifdef CONFIG_DEBUG_STACK_USAGE' which does the same thing for process stacks, or CONFIG_SCHED_STACK_END_CHECK or the use of guard pages for detecting stack overrun....