linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Balbir Singh <bsingharora@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc/mm/pgtable: Split mappings on hot-unplug
Date: Fri,  9 Feb 2018 15:00:35 +1100 (AEDT)	[thread overview]
Message-ID: <3zd1Yw1YWgz9t3F@ozlabs.org> (raw)
In-Reply-To: <20180207063551.8991-1-bsingharora@gmail.com>

On Wed, 2018-02-07 at 06:35:51 UTC, Balbir Singh wrote:
> This patch splits the a linear mapping if the hot-unplug range
> is smaller than the mapping size. The code detects if the mapping
> needs to be split into a smaller size and if so, uses the stop
> machine infrastructure to map the current linear mapping with
> a smaller size mapping. Then the requested area is unmapped.
> 
> The code will skip any region of the mapping that overlaps with
> kernel text and warn about it once. We don't want to remove
> a mapping where the kernel text and the LMB we intend to remove
> overlap in the same TLB mapping as it may affect the currently
> executing code (being cautious, we might be able to remove this
> restriction later, see TODOs below)
> 
> I've tested these changes under a kvm guest with 2 vcpus, from
> a split mapping point of view, some of the caveats mentioned
> above applied to the testing I did.
> 
> TODOs:
> 1. Refine the stop machine with an atomic replacement of the
> PMD. The code needs to be refactored to support those changes.
> I intend to publish those changes, but this is a minimal set
> that should be also probably backported to stable
> 
> Signed-off-by: Balbir Singh <bsingharora@gmail.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/4dd5f8a99e791a8c6500e3592f3ce8

cheers

      reply	other threads:[~2018-02-09  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  6:35 [PATCH] powerpc/mm/pgtable: Split mappings on hot-unplug Balbir Singh
2018-02-09  4:00 ` Michael Ellerman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3zd1Yw1YWgz9t3F@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).