linux-kernel - Re: [PATCH] x86/earlyprintk: setup earlyprintk as early as possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Apr 2015 16:31:54 +0600
From:	Alexander Kuleshov <kuleshovmail@...il.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/earlyprintk: setup earlyprintk as early as possible

> Ingo Molnar <mingo@...nel.org>: wrote:
>
> Just add a debug printk() for your own testing, right after the param
> initialization call, to be confident that the early console indeed
> works.
>

I already tested it as you said when was writing this patch and it works.

>
> I'd use i386_start_kernel() on 32-bit and x86_64_start_kernel() on
> 64-bit - but I haven't tested whether it actually works.
>

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/