On Fri, 13 Oct 2017 15:06:09 +0200
Petr Mladek wrote:
> >
> > Can we even have !PRINTK && EARLY_PRINTK? If so it seems to me continued
> > usage of early_printk() is what makes most sense.
>
> Yes, !PRINTK && EARLY_PRINTK is possible at the moment. It makes some
> sense
On Fri, 13 Oct 2017 15:06:09 +0200
Petr Mladek wrote:
> >
> > Can we even have !PRINTK && EARLY_PRINTK? If so it seems to me continued
> > usage of early_printk() is what makes most sense.
>
> Yes, !PRINTK && EARLY_PRINTK is possible at the moment. It makes some
> sense because EARLY_PRINTK
On Fri, Oct 13, 2017 at 03:06:09PM +0200, Petr Mladek wrote:
> Or we should call early_printk() from printk() also when
> PRINTK is disabled.
This.
> > Do you mean if someone were to toggle force_early_printk at runtime?
>
> Or that someone unregisters the early console.
That's broken anyway,
On Fri, Oct 13, 2017 at 03:06:09PM +0200, Petr Mladek wrote:
> Or we should call early_printk() from printk() also when
> PRINTK is disabled.
This.
> > Do you mean if someone were to toggle force_early_printk at runtime?
>
> Or that someone unregisters the early console.
That's broken anyway,
On Thu 2017-10-12 13:39:49, Peter Zijlstra wrote:
> On Thu, Oct 12, 2017 at 12:24:19PM +0200, Petr Mladek wrote:
> > On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
>
> > > +#ifdef CONFIG_EARLY_PRINTK
> > > +struct console *early_console;
> > > +
> > > +static bool __read_mostly
On Thu 2017-10-12 13:39:49, Peter Zijlstra wrote:
> On Thu, Oct 12, 2017 at 12:24:19PM +0200, Petr Mladek wrote:
> > On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
>
> > > +#ifdef CONFIG_EARLY_PRINTK
> > > +struct console *early_console;
> > > +
> > > +static bool __read_mostly
On Thu, Oct 12, 2017 at 12:24:19PM +0200, Petr Mladek wrote:
> On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
> > +#ifdef CONFIG_EARLY_PRINTK
> > +struct console *early_console;
> > +
> > +static bool __read_mostly force_early_printk;
> > +
> > +static int __init force_early_printk_setup(char
On Thu, Oct 12, 2017 at 12:24:19PM +0200, Petr Mladek wrote:
> On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
> > +#ifdef CONFIG_EARLY_PRINTK
> > +struct console *early_console;
> > +
> > +static bool __read_mostly force_early_printk;
> > +
> > +static int __init force_early_printk_setup(char
On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
> Add add the 'force_early_printk' kernel parameter to override printk()
> and force it into early_printk(). This bypasses all the cruft and fail
> from printk() and makes things work again.
>
> Signed-off-by: Peter Zijlstra (Intel)
On Thu 2017-09-28 14:18:25, Peter Zijlstra wrote:
> Add add the 'force_early_printk' kernel parameter to override printk()
> and force it into early_printk(). This bypasses all the cruft and fail
> from printk() and makes things work again.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
>
On Thu, 28 Sep 2017 14:18:25 +0200
Peter Zijlstra wrote:
> Add add the 'force_early_printk' kernel parameter to override printk()
> and force it into early_printk(). This bypasses all the cruft and fail
> from printk() and makes things work again.
Probably break this up
On Thu, 28 Sep 2017 14:18:25 +0200
Peter Zijlstra wrote:
> Add add the 'force_early_printk' kernel parameter to override printk()
> and force it into early_printk(). This bypasses all the cruft and fail
> from printk() and makes things work again.
Probably break this up into two patches. One
On 09/28/17 09:07, Peter Zijlstra wrote:
> On Thu, Sep 28, 2017 at 08:41:37AM -0700, Randy Dunlap wrote:
>
>> Please add that kernel parameter to
>> Documentation/admin-guide/kernel-parameters.txt.
>
> Something like so?
Yes, thanks. Ack.
> ---
On 09/28/17 09:07, Peter Zijlstra wrote:
> On Thu, Sep 28, 2017 at 08:41:37AM -0700, Randy Dunlap wrote:
>
>> Please add that kernel parameter to
>> Documentation/admin-guide/kernel-parameters.txt.
>
> Something like so?
Yes, thanks. Ack.
> ---
On Thu, Sep 28, 2017 at 08:41:37AM -0700, Randy Dunlap wrote:
> Please add that kernel parameter to
> Documentation/admin-guide/kernel-parameters.txt.
Something like so?
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -1165,6
On Thu, Sep 28, 2017 at 08:41:37AM -0700, Randy Dunlap wrote:
> Please add that kernel parameter to
> Documentation/admin-guide/kernel-parameters.txt.
Something like so?
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -1165,6
On 09/28/17 05:18, Peter Zijlstra wrote:
Hi Peter,
Please add that kernel parameter to
Documentation/admin-guide/kernel-parameters.txt.
thanks,
--
~Randy
On 09/28/17 05:18, Peter Zijlstra wrote:
Hi Peter,
Please add that kernel parameter to
Documentation/admin-guide/kernel-parameters.txt.
thanks,
--
~Randy
Add add the 'force_early_printk' kernel parameter to override printk()
and force it into early_printk(). This bypasses all the cruft and fail
from printk() and makes things work again.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 68
Add add the 'force_early_printk' kernel parameter to override printk()
and force it into early_printk(). This bypasses all the cruft and fail
from printk() and makes things work again.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 68
d-by.
In particular, the above change was moved to the first patch
to fix bisectability. The result after applying both patches
is still exactly the same.
>From e1c00ae67d07767ec8e5bddb1113c2badf31f4bd Mon Sep 17 00:00:00 2001
From: Petr Mladek <pmla...@suse.com>
Date: Tue, 29 Nov 2
d-by.
In particular, the above change was moved to the first patch
to fix bisectability. The result after applying both patches
is still exactly the same.
>From e1c00ae67d07767ec8e5bddb1113c2badf31f4bd Mon Sep 17 00:00:00 2001
From: Petr Mladek
Date: Tue, 29 Nov 2016 13:32:56 +0100
Subject: [PAT
Add add the 'force_early_printk' kernel parameter to override printk()
and force it into early_printk(). This bypasses all the cruft and fail
from printk() and makes things work again.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 74
Add add the 'force_early_printk' kernel parameter to override printk()
and force it into early_printk(). This bypasses all the cruft and fail
from printk() and makes things work again.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 74
24 matches
Mail list logo