kdump: crashkernel parameter improvement
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | kdump: extend crashkernel=range:size to dynamically increase reservation sizeDocumentation/ Documentation/ kernel/ | +41 | 2 replies | |
| 2/3 | X86/kdump: crashkernel=X try to reserve below 896M first then below 4G and MAXMEMarch/ | +16 | 3 replies | |
| 3/3 | kdump: round up the total memory size to 128M for crashkernel reservationkernel/ | +13 | 3 replies | |
| 3/3 | kdump: round up the total memory size to 128M for crashkernel reservationkernel/ | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] kdump: crashkernel parameter improvement
Hi,
Here is a try to improve current crashkernel kernel parameter
Patch 1/3 adds an extra functionality so that one can use like crashkernel=2G-:128M^12 to reserve 128M for 2G+ machine but also scale the size based on system memory, that means 128M + (total_mem - 128M) >> 12
Patch 2/3 is a resending of previous post to let crashkernel=xM to reserve first from below 896M, then <4G, then <MAXMEM
Patch 3/3 round up total system memory size because according to test the mem size from memblock api is usually smaller than actual size, this passed my tests on x86/arm/powerpc, it should work for most cases, but there might be exceptions, appreciated for any better idea.
Thanks
Dave