From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754769AbcHCDac (ORCPT ); Tue, 2 Aug 2016 23:30:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60050 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752905AbcHCDaU (ORCPT ); Tue, 2 Aug 2016 23:30:20 -0400 Date: Tue, 2 Aug 2016 22:30:00 -0500 From: Josh Poimboeuf To: Steven Rostedt Cc: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, Andy Lutomirski , Linus Torvalds , Brian Gerst , Kees Cook , Peter Zijlstra , Frederic Weisbecker , Byungchul Park Subject: Re: [PATCH 05/19] x86/dumpstack: fix function graph tracing stack dump reliability issues Message-ID: <20160803033000.3es37b532nyhqjxp@treble> References: <20160802210011.k6li4mnyvky5jtev@treble> <20160802171610.09156c90@gandalf.local.home> <20160802221359.tkb3mkjzkq3petrq@treble> <20160802191622.466f53d2@gandalf.local.home> <20160803015656.j6fxrgucmghh5gfn@treble> <20160802223011.6209e28c@grimm.local.home> <20160803025012.bmte6hjhcd6lotod@treble> <20160802225936.5b6dad93@grimm.local.home> <20160803031233.b73xz5jftxj7crqh@treble> <20160802231857.4c082831@grimm.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160802231857.4c082831@grimm.local.home> User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Wed, 03 Aug 2016 03:30:02 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 02, 2016 at 11:18:57PM -0400, Steven Rostedt wrote: > On Tue, 2 Aug 2016 22:12:33 -0500 > Josh Poimboeuf wrote: > > > > Sounds good. I was thinking I could also add a similar define to > > indicate whether an arch passes the return address stack pointer to > > ftrace_push_return_trace(). HAVE_FUNCTION_GRAPH_RET_ADDR_PTR? > > > > If you are making this function global, might as well make all pass > that pointer when you do the conversion. I don't think we need a define > to differentiate it. In theory, I like the idea. But from what I can tell, it looks like a few arches would require some assembly changes: s390, powerpc, and sparc. I can probably handle s390 and power, but sparc is a whole different story... -- Josh