Re: [PATCH 1/2] x86_64: fix mm.txt documentation

[Ingo Molnar]

* Jiri Slaby <jirislaby@xxxxxxxxx> wrote:

> Commit 85eb69a16aab5a394ce043c2131319eae35e6493 introduced 512 MiB 
> sized kernel and 1.5 GiB sized module space but omitted to change 
> documentation properly. Fix that.

thanks Jiri, applied.

> [Wasn't the hole intentional protection hole?]

> -ffffffff80000000 - ffffffff82800000 (=40 MB)   kernel text mapping, from phys 0
> -... unused hole ...
> -ffffffff88000000 - fffffffffff00000 (=1919 MB) module mapping space
> +ffffffff80000000 - ffffffffa0000000 (=512 MB)  kernel text mapping, from phys 0
> +ffffffffa0000000 - fffffffffff00000 (=1536 MB) module mapping space

yep, the image was in a 128 MB chunk from which 88 MB was left empty and 
modules started at the next 128 MB boundary. The largest image i ever 
had was around 44MB, so i doubt it's an issue in practice. Mind doing a 
patch that reinstates it, by lowering the 512 image size limit to 508 
MB? [4MB should be more than enough in practice]

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/