Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753726AbZFEWYm (ORCPT ); Fri, 5 Jun 2009 18:24:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751468AbZFEWYf (ORCPT ); Fri, 5 Jun 2009 18:24:35 -0400 Received: from pfepa.post.tele.dk ([195.41.46.235]:37604 "EHLO pfepa.post.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247AbZFEWYe (ORCPT ); Fri, 5 Jun 2009 18:24:34 -0400 Date: Sat, 6 Jun 2009 00:26:50 +0200 From: Sam Ravnborg To: "H. Peter Anvin" Cc: LKML , linux-arch@vger.kernel.org Subject: Re: "N" symbols and System.map Message-ID: <20090605222650.GM29008@uranus.ravnborg.org> References: <49FB7692.2000508@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49FB7692.2000508@linux.intel.com> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 859 Lines: 24 On Fri, May 01, 2009 at 03:24:18PM -0700, H. Peter Anvin wrote: > Hi all, > > right now, we filter out symbols that nm tag N, meaning "debugging > symbols", from System.map. However, at least on x86, the > linker-generated symbol _end is tagged N, and in fact is the only N in > the entire image. > > Are there other architectures which would suffer if N were included in > System.map, or would that be a reasonable thing to do? Peter - what is status here? Do you see _end tagged N with -tip? We landed a lot of changes to vmlinux.lds there. Needless to say I have not included N symbols for now. Sam -- 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/