Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751817AbeAEMBk (ORCPT + 1 other); Fri, 5 Jan 2018 07:01:40 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:46762 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751784AbeAEMBh (ORCPT ); Fri, 5 Jan 2018 07:01:37 -0500 X-Google-Smtp-Source: ACJfBovLujMrEFWo4UyzXATPHTcehX93RTBZg6TGpP/TovV55x2W0+ZKVSUmlQyCCpmornZtCiu5QQ== Date: Fri, 5 Jan 2018 21:01:31 +0900 From: Sergey Senozhatsky To: Sergey Senozhatsky Cc: Petr Mladek , Andrew Morton , Russell King , Catalin Marinas , Mark Salter , Tony Luck , David Howells , Yoshinori Sato , Guan Xuetao , Borislav Petkov , Greg Kroah-Hartman , Thomas Gleixner , Peter Zijlstra , Vineet Gupta , Fengguang Wu , Steven Rostedt , LKML , linux-arm-kernel@lists.infradead.org, linux-c6x-dev@linux-c6x.org, linux-ia64@vger.kernel.org, linux-am33-list@redhat.com, linux-sh@vger.kernel.org, linux-edac@vger.kernel.org, x86@kernel.org, linux-snps-arc@lists.infradead.org, Sergey Senozhatsky Subject: Re: [PATCH 00/13] replace print_symbol() with printk()-s Message-ID: <20180105120131.GA417@jagdpanzerIV> References: <20171211125025.2270-1-sergey.senozhatsky@gmail.com> <20180105100300.j3svmcvvpfe2iows@pathway.suse.cz> <20180105102105.GB471@jagdpanzerIV> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180105102105.GB471@jagdpanzerIV> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On (01/05/18 19:21), Sergey Senozhatsky wrote: > > print_symbol() is an old weird API. It has been > > obsoleted by printk() and %pS format specifier. > > I wouldn't. let's drop the "weird" part. hm... you are right, it is weird. and the weird part here is that print_symbol() is used for things like __show_regs() print_symbol("PC is at %s\n", instruction_pointer(regs)); print_symbol("LR is at %s\n", regs->ARM_lr); printk("pc : [<%08lx>] lr : [<%08lx>] psr: %08lx\n", regs->ARM_pc, regs->ARM_lr, regs->ARM_cpsr); or for EMERG error reporting pr_emerg("unexpected fault for address: 0x%08lx, last fault for address: 0x%08lx\n", addr, my_reason->addr); print_pte(addr); print_symbol(KERN_EMERG "faulting IP is at %s\n", regs->ip); print_symbol(KERN_EMERG "last faulting IP was at %s\n", my_reason->ip); #ifdef __i386__ pr_emerg("eax: %08lx ebx: %08lx ecx: %08lx edx: %08lx\n", regs->ax, regs->bx, regs->cx, regs->dx); or for error reporting in sysfs print_symbol("fill_read_buffer: %s returned bad count\n", (unsigned long)ops->show); and so on. but, print_symbol() is compiled out on !CONFIG_KALLSYMS systems. so, basically, we compile out some of errors print outs; even more, on ia64 ia64_do_show_stack() does nothing when there is no CONFIG_KALLSYMS [all ia64 defconfigs have KALLSYMS_ALL enabled]. printk(%pS), unlike print_symbol(), is not compiled out and prints the function address when symbolic name is not available. but, at a glance, print_symbol() in most of the cases has printk(registers) next to it or before it, so it doesn't look like we are introducing a regression here by switching to printk(%pS). -ss