printk: Add force_early_printk boot param
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 34 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | printk: Fix kdb_trap_printk placementkernel/ | +6 | 12 replies | |
| 2/3 | early_printk: Add force_early_printk kernel parameterkernel/ | +47 | 9 replies | |
| 3/3 | early_printk: Add simple serialization to early_vprintk()kernel/ | +34 | 11 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Steven Rostedt (VMware) |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] printk: Add force_early_printk boot param
Most all printk() bits are terminally broken because they rely on the scheduler and blocking locks to function, making them unsuitable for debugging the scheduler and NMI context things.
Luckily many early_printk implementations are relatively sane and don't rely on anything much at all; the x86 early_serial_console for example is pure bit-banging without anything.
So provide means to always use these and avoid the whole printk mess.