Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750739AbWAPNlI (ORCPT ); Mon, 16 Jan 2006 08:41:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750756AbWAPNlI (ORCPT ); Mon, 16 Jan 2006 08:41:08 -0500 Received: from ns.miraclelinux.com ([219.118.163.66]:22584 "EHLO mail01.miraclelinux.com") by vger.kernel.org with ESMTP id S1750739AbWAPNlH (ORCPT ); Mon, 16 Jan 2006 08:41:07 -0500 Date: Mon, 16 Jan 2006 22:41:09 +0900 To: Andi Kleen Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] changes about Call Trace: Message-ID: <20060116134109.GA6707@miraclelinux.com> References: <20060116121611.GA539@miraclelinux.com> <200601161322.12209.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601161322.12209.ak@suse.de> User-Agent: Mutt/1.5.9i From: mita@miraclelinux.com (Akinobu Mita) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 26 On Mon, Jan 16, 2006 at 01:22:11PM +0100, Andi Kleen wrote: > On Monday 16 January 2006 13:16, Akinobu Mita wrote: > > If I'm missing something, please let me know. > > > > a) On x86-64 we get different Call Trace format than other architectures > > when we get oops or press SysRq-t: > > > > {:jbd:kjournald+1030} > > > > There is a architecture independent function print_symbol(). > > How about using it on x86-64? But it changes to: > > > > [] kjournald+0x406/0x578 [jbd] > > The x86-64 format is more compact. How about this update? 1/3: change from "[<...>]" to "<...>". 2/3: change the format of offset from hexadecimal to decimal in. - 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/