linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com,
	mpe@ellerman.id.au, david@gibson.dropbear.id.au, anton@samba.org,
	Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: [RFC FIX v1 0/2] powerpc: Fix memory unplug failure for radix guests
Date: Fri,  5 Jan 2018 16:35:19 +0530	[thread overview]
Message-ID: <1515150321-24894-1-git-send-email-bharata@linux.vnet.ibm.com> (raw)

This is an RFC patchset to fix the call trace observed during memory
unplug for radix guests. The problem and the fix is described in patch 2/2.

The ideal fix for this is to break the bigger radix mapping into smaller
mappings during memory hot removal, but in the meanwhile I am just posting
an alternate and easier solution which of course, has its own
limitations (mentioned in 2/2)

Changes in v1:
--------------
- Move mmu-early-init-devtree() ahead of scanning memory DT nodes
  so that we know if the guest is radix or not when scanning
  memory nodes.
- Make the marking of hotpluggable only if the guest is radix.

v0: http://patchwork.ozlabs.org/patch/800142/

Bharata B Rao (2):
  powerpc: Discover radix availability before scanning the memory nodes
  powerpc: Fix memory unplug failure on radix guest

 arch/powerpc/kernel/prom.c      |  6 ++++--
 arch/powerpc/mm/pgtable-radix.c | 17 ++++++++++++++---
 2 files changed, 18 insertions(+), 5 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-01-05 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 11:05 Bharata B Rao [this message]
2018-01-05 11:05 ` [RFC FIX v1 1/2] powerpc: Discover radix availability before scanning the memory nodes Bharata B Rao
2018-01-05 11:16   ` Aneesh Kumar K.V
2018-01-05 23:28   ` Michael Ellerman
2018-01-08  9:16     ` Bharata B Rao
2018-01-05 11:05 ` [RFC FIX v1 2/2] powerpc: Fix memory unplug failure on radix guest Bharata B Rao

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=1515150321-24894-1-git-send-email-bharata@linux.vnet.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=nfont@linux.vnet.ibm.com \
    /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).