Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755387Ab2K2VEn (ORCPT ); Thu, 29 Nov 2012 16:04:43 -0500 Received: from mail-qa0-f46.google.com ([209.85.216.46]:63963 "EHLO mail-qa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755143Ab2K2VEm (ORCPT ); Thu, 29 Nov 2012 16:04:42 -0500 MIME-Version: 1.0 Date: Thu, 29 Nov 2012 16:04:40 -0500 Message-ID: Subject: MIPS Function Tracer question From: Alan Cooper To: ralf@linux-mips.org, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1315 Lines: 25 I've been doing some testing of the MIPS Function Tracer functionality on the 3.3 kernel. I was surprised to find that the option to generate frame pointers was required for tracing. When I don't enable FRAME_POINTER along with FUNCTION_TRACER, the kernel hangs on boot. I also noticed that a checkin to the 3.4 kernel (b732d439cb43336cd6d7e804ecb2c81193ef63b0) no longer forces on FRAME_POINTER when FUNCTION_TRACER is selected. I was wondering how it works in 3.4 and beyond, so I built a Malta kernel from the latest MIPS tree with FUNCTION_TRACING enabled and tested it with QEMU. The kernel hung the same way. I can think of 2 reasons for this: 1. Function tracing is broken for MIPS in 3.4 and beyond. 2. The 4.5.3 GNU C compiler I'm using is generating different code for function tracing. I was wondering if anyone has MIPS function tracing working in 3.4 or later? I did figure out why it's hanging and I have some changes that will allow the function tracer to run without frame pointers, but before I proceed I want to rule out compiler differences. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/