From: Balbir Singh <bsingharora@gmail.com>
To: rashmica <rashmica.g@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, Michael Neuling <mikey@neuling.org>
Subject: Re: [resend] Revert "powerpc/powernv: Increase memory block size to 1GB on radix"
Date: Wed, 2 May 2018 15:57:57 +1000 [thread overview]
Message-ID: <20180502155757.1a80b51e@balbir.ozlabs.ibm.com> (raw)
In-Reply-To: <58c3feb3-390c-2461-2bca-5b71f8dd14df@gmail.com>
On Wed, 2 May 2018 15:10:33 +1000
rashmica <rashmica.g@gmail.com> wrote:
> Tested hot-unplugging dimm device on radix guest on p9 host with KVM.
>
>
> On 01/05/18 12:57, Balbir Singh wrote:
> > This commit was a stop-gap to prevent crashes on hotunplug, caused by
> > the mismatch between the 1G mappings used for the linear mapping and the
> > memory block size. Those issues are now resolved because we split the
> > linear mapping at hotunplug time if necessary, as implemented in commit
> > 4dd5f8a99e79 ("powerpc/mm/radix: Split linear mapping on hot-unplug").
> >
> > Signed-off-by: Balbir Singh <bsingharora@gmail.com>
> > Signed-off-by: Michael Neuling <mikey@neuling.org>
> Tested-by: Rashmica Gupta <rashmica.g@gmail.com>
I tested the following:
a. memtrace - enable a region smaller than 1G, which split the mappings
as expected.
b. Checked linear mapping is 1G and not impacted by the revert
c. I can hotplug sizes less than 1G via the probe method
Tested-by: Balbir Singh <bsingharora@gmail.com>
> > ---
> >
> > Resend with a newer commit message grabbed from an email sent by mpe.
> >
> > arch/powerpc/platforms/powernv/setup.c | 10 +---------
> > 1 file changed, 1 insertion(+), 9 deletions(-)
> >
> > diff --git a/arch/powerpc/platforms/powernv/setup.c b/arch/powerpc/platforms/powernv/setup.c
> > index ef8c9ce53a61..fa63d3fff14c 100644
> > --- a/arch/powerpc/platforms/powernv/setup.c
> > +++ b/arch/powerpc/platforms/powernv/setup.c
> > @@ -356,15 +356,7 @@ static void pnv_kexec_cpu_down(int crash_shutdown, int secondary)
> > #ifdef CONFIG_MEMORY_HOTPLUG_SPARSE
> > static unsigned long pnv_memory_block_size(void)
> > {
> > - /*
> > - * We map the kernel linear region with 1GB large pages on radix. For
> > - * memory hot unplug to work our memory block size must be at least
> > - * this size.
> > - */
> > - if (radix_enabled())
> > - return 1UL * 1024 * 1024 * 1024;
> > - else
> > - return 256UL * 1024 * 1024;
> > + return 256UL * 1024 * 1024;
> > }
> > #endif
> >
>
next prev parent reply other threads:[~2018-05-02 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 2:57 [resend] Revert "powerpc/powernv: Increase memory block size to 1GB on radix" Balbir Singh
2018-05-02 5:10 ` rashmica
2018-05-02 5:57 ` Balbir Singh [this message]
2018-05-08 14:52 ` Michael Ellerman
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=20180502155757.1a80b51e@balbir.ozlabs.ibm.com \
--to=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=rashmica.g@gmail.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).