Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753726AbbDGTIg (ORCPT ); Tue, 7 Apr 2015 15:08:36 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:35647 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753619AbbDGTIa (ORCPT ); Tue, 7 Apr 2015 15:08:30 -0400 MIME-Version: 1.0 In-Reply-To: References: <1428326234-10067-1-git-send-email-kuleshovmail@gmail.com> <20150407095228.GA13093@gmail.com> <20150407102445.GA13658@gmail.com> Date: Tue, 7 Apr 2015 12:08:29 -0700 X-Google-Sender-Auth: q2rsMOzMzMj6gvQ2-fQ2SGZkHzg Message-ID: Subject: Re: [PATCH] x86/earlyprintk: setup earlyprintk as early as possible From: Yinghai Lu To: Alexander Kuleshov Cc: Ingo Molnar , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Greg Kroah-Hartman , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1126 Lines: 29 On Tue, Apr 7, 2015 at 12:07 PM, Yinghai Lu wrote: > On Tue, Apr 7, 2015 at 3:31 AM, Alexander Kuleshov > wrote: > >> >> As i already wrote, i tested it for x86_64 and it works. I will put earlyprintk >> setup in the start of the i386_start_kernel, will test it with 32-bit >> and resend two >> patches if they will be good. > > No, that is not enough. > early_printk would handle not only serial console with io port accessing. > You need to make sure all other path including pciserial/dbgp/efi is safe. > They are using early_ioremap, and you can not call early_ioremap() > before early_ioremap. They are using early_ioremap, and you can not call early_ioremap() before early_ioremap_init. > > otherwise you may need to just search "serial string in boot command line" like > i did in moving earlycon early patch. > > Yinghai -- 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/