Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp4346668ybh; Tue, 6 Aug 2019 10:05:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqxsSPrW6M+X2mZ1KJzAMmvSf79hEegBvKhsPTC8U38cB3udum+7xOU2zzG42XRDqhs7gaHA X-Received: by 2002:a17:902:724a:: with SMTP id c10mr3877815pll.298.1565111148153; Tue, 06 Aug 2019 10:05:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565111148; cv=none; d=google.com; s=arc-20160816; b=EQiQjROP4R69NYK8AnkZVpJYJurIdFwNhewK/3SW51WHjEM087p+W/RlgN2ZhBM83D 7ECNjgB3it1FHYJEiJanvS1rmVo/KVyRXKc6sXTAObcD0YNphIPizQuW7YvpYjD0xu+2 9E2NmL0GGM7tID415lfU7H+MYajI8nPyA20FfilL6Y9hNlOv383tyKr5QgBKg/OupuEh siHVr+BV5ykh36ozOqoBcS0TrOKK/tRWzZwvbN+YhvDOEHV0x19z1QwbPZbOIFOemjww MT2q7ReAjZlBG6ajl372blyvjElfgOhZ14ridWTaofXolwI2fQmj1QxxFN0J8cjWFOIX bgJA== 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:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=elPExN8gPl3RnSKK9PmR1TewJ+qojp9awzmUjMz9Ip0=; b=I1qamMSn5VFAp+AKaG+IOHXnrLkxgszQMT/TRkMlhWvIr9rLkxQXpWr4Q9Yot4v7GT /xkRDwbtEFaLFTkiMqCk5AXz8WVOO5RzqqBNuPkPG8W493M9IRlPXJAsbJzYH5IHkDTT vIa+k6rVMMRefHwlZWZZA7fXbi+bkd3G0P+4+9RH5dS3x4wT/uF5Y+I7AWs6JfY16QT7 SE0VXfbTvkvJ9n1BmBhD/CEqsmuqtDHsFly9mJ3kHx0YqE7N6Ef0lul9JsZjaZQJDN3c LAFpQ7kidHuYywtEgj1m7o3ASgUhfgD5BA358h0g57s+j76NWbZanp0FNfPJUAyiJPUq 1pZw== 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 n187si46901786pgn.362.2019.08.06.10.05.32; Tue, 06 Aug 2019 10:05:48 -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 S2388059AbfHFRD1 (ORCPT + 99 others); Tue, 6 Aug 2019 13:03:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:38452 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733011AbfHFRD0 (ORCPT ); Tue, 6 Aug 2019 13:03:26 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 56B2420717; Tue, 6 Aug 2019 17:03:25 +0000 (UTC) Date: Tue, 6 Aug 2019 13:03:23 -0400 From: Steven Rostedt To: Joel Fernandes Cc: Jiping Ma , mingo@redhat.com, catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3] tracing: Function stack size and its name mismatch in arm64 Message-ID: <20190806130323.7075c3da@gandalf.local.home> In-Reply-To: <20190806123455.487ac02b@gandalf.local.home> References: <20190802094103.163576-1-jiping.ma2@windriver.com> <20190802112259.0530a648@gandalf.local.home> <20190802120920.3b1f4351@gandalf.local.home> <20190802121124.6b41f26a@gandalf.local.home> <20190806154811.GB39951@google.com> <20190806123455.487ac02b@gandalf.local.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 6 Aug 2019 12:34:55 -0400 Steven Rostedt wrote: > Here's the best way to explain this. The code is using the stack trace > to figure out which function is the stack hog. Or perhaps a serious of Why so serious? .... s/serious/series/ -- Steve > stack hogs. On x86, a call stores the return address as it calls the > next function. Then that function allocates its stack frame for its > local variables and saving of registers.