Groups > linux.kernel > #1592084

Re: [PATCH v4 1/3] x86: Introduce a new constant KERNEL_MAPPING_SIZE

From	Borislav Petkov <bp@suse.de>
Newsgroups	linux.kernel
Subject	Re: [PATCH v4 1/3] x86: Introduce a new constant KERNEL_MAPPING_SIZE
Date	2017-03-03 17:00 +0100
Message-ID	<tgUc1-102-3@gated-at.bofh.it> (permalink)
References	<t6p9v-441-11@gated-at.bofh.it> <t6p9v-441-9@gated-at.bofh.it> <taPf4-4KR-25@gated-at.bofh.it> <teYtr-1q5-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sun, Feb 26, 2017 at 12:09:08PM +0800, Baoquan He wrote:
> Am I right on understanding it?

That's exactly what I mean: KERNEL_IMAGE_SIZE is 512M by default but
we're not hard-constrained to it - we're hard-constrained to a 1G limit
as this is the 1G which is covered by level2_kernel_pgt.

And in thinking about this more, I know I suggested making the
KERNEL_IMAGE_SIZE by default 1G in order to simplify things.

But you're adding another KERNEL_MAPPING_SIZE which confuses things
more. And I fail to see why we absolutely need it.

So we suggest kernel image size should be 512M but then we still will
be using a whole 1G mapping for it anyway and a whole page of PMDs at
level2_kernel_pgt.

So why even bother?

Just make it 1G and don't introduce anything new.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH v4 1/3] x86: Introduce a new constant KERNEL_MAPPING_SIZE Borislav Petkov <bp@suse.de> - 2017-03-03 17:00 +0100

csiph-web