Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753868AbbDHJbb (ORCPT ); Wed, 8 Apr 2015 05:31:31 -0400 Received: from mail-lb0-f175.google.com ([209.85.217.175]:34007 "EHLO mail-lb0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753829AbbDHJb1 (ORCPT ); Wed, 8 Apr 2015 05:31:27 -0400 From: Alexander Kuleshov To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Greg Kroah-Hartman , Yinghai Lu Cc: linux-kernel@vger.kernel.org Subject: [PATCH 0/2] x86/earlyprintk: setup earlyprintk as early as possible Date: Wed, 8 Apr 2015 15:31:06 +0600 Message-Id: <1428485466-24326-1-git-send-email-kuleshovmail@gmail.com> X-Mailer: git-send-email 2.3.3.611.g09038fc.dirty Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1324 Lines: 32 As setup_early_printk passed to the early_param, it will be usable only after 'parse_early_param' function will be called from the 'setup_arch'. So we have earlyprintk during early boot and decompression. Next point after decompression of the kernel where we can use early_printk is after call of the 'parse_early_param'. This patch provides initialization of earlyprintk serial console as early as possible in the arch/x86/kerne/head{32,64}.c Alexander Kuleshov (2): x86/setup: update boot_command_line with builtin_cmdline in separate function x86/earlyprintk: setup earlyprintk as early as possible arch/x86/kernel/early_printk.c | 2 +- arch/x86/kernel/head.c | 14 ++++++++++++++ arch/x86/kernel/head32.c | 3 +++ arch/x86/kernel/head64.c | 8 +++++++- arch/x86/kernel/setup.c | 31 ++++++++++++++++++------------- include/linux/init.h | 6 +++++- include/linux/printk.h | 4 ++++ kernel/printk/printk.c | 11 +++++++---- 8 files changed, 59 insertions(+), 20 deletions(-) -- 2.3.3.611.g09038fc.dirty -- 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/