Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1333047 > unrolled thread

Re: [PATCH 03/11] x86/mm/hotplug: Don't remove PGD entries in remove_pagetable()

Started byAndy Lutomirski <luto@amacapital.net>
First post2016-02-12 20:10 +0100
Last post2016-02-12 20:10 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 03/11] x86/mm/hotplug: Don't remove PGD entries in remove_pagetable() Andy Lutomirski <luto@amacapital.net> - 2016-02-12 20:10 +0100

#1333047 — Re: [PATCH 03/11] x86/mm/hotplug: Don't remove PGD entries in remove_pagetable()

FromAndy Lutomirski <luto@amacapital.net>
Date2016-02-12 20:10 +0100
SubjectRe: [PATCH 03/11] x86/mm/hotplug: Don't remove PGD entries in remove_pagetable()
Message-ID<r1rgl-2Ho-9@gated-at.bofh.it>
On Mon, Sep 21, 2015 at 11:23 PM, Ingo Molnar <mingo@kernel.org> wrote:
> So when memory hotplug removes a piece of physical memory from pagetable
> mappings, it also frees the underlying PGD entry.
>
> This complicates PGD management, so don't do this. We can keep the
> PGD mapped and the PUD table all clear - it's only a single 4K page
> per 512 GB of memory hotplugged.

Ressurecting an ancient thread: I want this particular change to make
it (much) easier to make vmapped stacks work correctly.  Could it be
applied by itself?

--Andy

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web