From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752260AbbE0MBz (ORCPT ); Wed, 27 May 2015 08:01:55 -0400 Received: from cantor2.suse.de ([195.135.220.15]:36538 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751641AbbE0MBw (ORCPT ); Wed, 27 May 2015 08:01:52 -0400 Date: Wed, 27 May 2015 14:01:40 +0200 From: Borislav Petkov To: Alexander Kuleshov Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andy Shevchenko , LKML , Greg Kroah-Hartman , Mark Rustad , Yinghai Lu Subject: Re: [PATCH v8 0/3] x86/earlyprintk: setup serial earlyprintk as early as possible Message-ID: <20150527120140.GC19582@pd.tnic> References: <1432645607-29343-1-git-send-email-kuleshovmail@gmail.com> <20150526131717.GB18076@nazgul.tnic> <20150526135700.GC18076@nazgul.tnic> <20150526213400.GA17409@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 27, 2015 at 01:33:23PM +0600, Alexander Kuleshov wrote: > We can't use earlyprintk from the arch/x86/kernel/head{32,64}.c before > parse_early_param from the arch/x86/kernel/setup.c. Yes, and I'm simply asking why do we even want to use it there at all. What do you think would need to be dumped with early_printk() calls there and would be useful? IOW, do you have a sensible use case for why we need it there or not? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --