Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755725AbYLJJH7 (ORCPT ); Wed, 10 Dec 2008 04:07:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754500AbYLJJHn (ORCPT ); Wed, 10 Dec 2008 04:07:43 -0500 Received: from mail.windriver.com ([147.11.1.11]:43763 "EHLO mail.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753731AbYLJJHm (ORCPT ); Wed, 10 Dec 2008 04:07:42 -0500 Message-ID: <493F82DE.8060909@windriver.com> Date: Wed, 10 Dec 2008 16:50:38 +0800 From: Wang Liming User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= CC: Steven Rostedt , Ingo Molnar , Peter Zijlstra , LKML Subject: Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output References: <493EF64D.50804@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 10 Dec 2008 09:06:55.0301 (UTC) FILETIME=[A6024F50:01C95AA6] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2016 Lines: 54 Frédéric Weisbecker wrote: > 2008/12/10 Steven Rostedt : >> On Tue, 9 Dec 2008, Frederic Weisbecker wrote: >> >>> This patchset adds all the features to draw hardirq triggering on output >>> for the function graph tracer. >>> An example is given on the third patch. >>> >>> Just one question, on recordmcount.pl: >>> >>> my %text_sections = ( >>> ".text" => 1, >>> ".sched.text" => 1, >>> ".spinlock.text" => 1, >>> >>> The .sched.text section is included inside .text, it's a subsection, I'm not sure >>> it's necessary to add it in text_sections. In doubt I added the new .irqentry.text >>> >> Matters what objdump -dr shows. >> >> $ objdump -dr kernel/sched.o | grep 'Disassembly' >> Disassembly of section .text: >> Disassembly of section .cpuinit.text: >> Disassembly of section .init.text: >> Disassembly of section .sched.text: >> >> Yep, .sched.text is needed. It is not about what gets linked by the >> linker. It is about what objdump shows, which is what recordmcount.pl uses >> to determine whether or not to record the mcount callers in that section. > > > Ok. I looked at a disassembly objdump on vmlinux to find those > subsections and didn't find it. > But I didn't see that recordmcount did its work on each build folder, You can see "scripts/Makefile.build" file, which uses recordmcount.pl to deal with each .o file when building. Liming Wang > I guess that these sections are > visible on the objects found in the subdirectories.... > > 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/ > -- 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/