From: Yinghai Lu <yinghai@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v4] x86: Setup early console as early as possible in x86_start_kernel()
Date: Mon, 11 Oct 2010 12:26:25 -0700 [thread overview]
Message-ID: <4CB364E1.5060303@kernel.org> (raw)
In-Reply-To: <4CB35973.3070100@zytor.com>
On 10/11/2010 11:37 AM, H. Peter Anvin wrote:
> On 10/11/2010 10:58 AM, Yinghai Lu wrote:
>>
>> #ifdef CONFIG_X86_TRAMPOLINE
>> Index: linux-2.6/arch/x86/kernel/head64.c
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/kernel/head64.c
>> +++ linux-2.6/arch/x86/kernel/head64.c
>> @@ -74,6 +74,10 @@ void __init x86_64_start_kernel(char * r
>> /* clear bss before set_intr_gate with early_idt_handler */
>> clear_bss();
>>
>> + /* boot_params is in bss */
>> + copy_bootdata(__va(real_mode_data));
>> + setup_early_console();
>> +
>> /* Make NULL pointers segfault */
>> zap_identity_mappings();
>>
>> @@ -97,7 +101,14 @@ void __init x86_64_start_kernel(char * r
>>
>> void __init x86_64_start_reservations(char *real_mode_data)
>> {
>> - copy_bootdata(__va(real_mode_data));
>> + /*
>> + * hdr.version is always not 0, so check it to see
>> + * if boot_params is copied or not.
>> + */
>> + if (!boot_params.hdr.version) {
>> + copy_bootdata(__va(real_mode_data));
>> + setup_early_console();
>> + }
>>
>> memblock_init();
>>
>
> Under what conditions would we *not* have gotten through
> x86_64_start_kernel()?
xen will go with x86_64_start_reservations() directly.
Yinghai
prev parent reply other threads:[~2010-10-11 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 17:58 [PATCH -v4] x86: Setup early console as early as possible in x86_start_kernel() Yinghai Lu
2010-10-11 18:37 ` H. Peter Anvin
2010-10-11 19:26 ` Yinghai Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB364E1.5060303@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.