Messages in this thread | | | Date | Thu, 16 Dec 2010 17:06:18 -0800 | From | "H. Peter Anvin" <> | Subject | Re: kdump broken on 2.6.37-rc4 |
| |
On 12/16/2010 04:39 PM, Yinghai Lu wrote: > > and use that to estimate BRK size. > > so we could change the BRK calculating code to handle 896M or just limit crashkernel for 32bit to 512M... > > handle 896M one: >
Grmf... this was originally 4 GiB, but someone tried to tighten the bound. I think we should set it back to 4 GiB; 896 MiB is still approximate.
Oh yes, this isn't how to write this, either...
> + * to make crashkernel bzImage to stay high, make it map to 896M > + * but it will be claimed back when brk is concluded. So no wasting. > */ > -KERNEL_PAGES = (KERNEL_IMAGE_SIZE + MAPPING_BEYOND_END)>>PAGE_SHIFT > +KERNEL_PAGES = (KERNEL_IMAGE_SIZE + (384<<20) + MAPPING_BEYOND_END)>>PAGE_SHIFT
-hpa
-- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
| |