Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <621dd76a8e0b449db66ba2c3ad20fb2c743a1f1b.camel@linux.ibm.com>
Subject: Re: [PATCH 1/1] powerpc/kernel: Enables memory hot-remove after
 reboot on pseries guests
From:   Leonardo Bras <leonardo@linux.ibm.com>
To:     Bharata B Rao <bharata.rao@gmail.com>
Cc:     ndfont@gmail.com,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        arbab@linux.ibm.com, Claudio Carvalho <cclaudio@linux.ibm.com>,
        Michael Roth <mdroth@linux.vnet.ibm.com>,
        Paul Mackerras <paulus@samba.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
        Hari Bathini <hbathini@linux.ibm.com>
Date:   Wed, 04 Mar 2020 04:18:32 -0300
In-Reply-To: <CAGZKiBr=8i11YPDn+1y5j6YfGj+tVbbTKakoGje9QQ8TEw9g5g@mail.gmail.com>
References: <20200228060439.52749-1-leonardo@linux.ibm.com>
         <CAGZKiBr=8i11YPDn+1y5j6YfGj+tVbbTKakoGje9QQ8TEw9g5g@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
        protocol="application/pgp-signature"; boundary="=-sL1rgkZbhhqGAClQPGna"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) 
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--=-sL1rgkZbhhqGAClQPGna
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Bharata, thanks for this feedback!

On Wed, 2020-03-04 at 10:13 +0530, Bharata B Rao wrote:
> Hi,
>=20
> I tried this a few years back
> (https://patchwork.ozlabs.org/patch/800142/) and didn't pursue it
> further because at that time, it was felt that the approach might not
> work for PowerVM guests, because all the present memory except RMA
> gets marked as hot-pluggable by PowerVM. This discussion is not
> present in the above thread, but during my private discussions with
> Reza and Nathan, it was noted that making all that memory as MOVABLE
> is not preferable for PowerVM guests as we might run out of memory for
> kernel allocations.

Humm, this makes sense.
But with mu change, these pieces of memory only get into ZONE_MOVABLE
if the boot parameter 'movable_node' gets passed to guest kernel.=20

So, even if we are unable to sort out some flag combination that work
fine for both use-cases, if PowerVM don't pass 'movable_node' as boot
parameter to kernel, it will behave just as today.

What are your thoughts on that?

Best regards,

Leonardo Bras

--=-sL1rgkZbhhqGAClQPGna
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEMdeUgIzgjf6YmUyOlQYWtz9SttQFAl5fVkgACgkQlQYWtz9S
ttTcqw/+KygdoD/4CjbE1qeM/UgE8K0p7R0VEctB20M41BvMj0yC4c+sHA+CPbkW
o273+a2KeG6le9K5sp7Gy7ElrSqczN2AuInkYHJ2AezPBw4pDRGTBTp2a91ivGdf
DidQrsx856IW6qouXsqo1NOIwDicuuy12/HCGzqvkFGaY6/89FdihM5FbBTtQ8Ps
DRKJnOwhz5gr0vcYLHtJdfyzuzPM4VzFDIYmTH3+vLgfYvfQFt0S4RqmoEsI0AXR
+u33lx995GzsafkladGDNKbX/v/xt9MRImGdhuHKmH5+ccnR/GankA5W4mOR+hw/
1caHR2Sn5bXlHwtJjL9OslJmPfWIho8D/v9SmRfJIgfE0Br9hNMrl9ttB4V9LmUV
Oe9e3hyyR3F0fVpKLrYvA9KQJ7ocm3I1e2hEwxYphtDiasCVCCFHD/Ue2sHpaNc2
0TcoIsWifC1TBMq2pMWIRVlkdee0B1V6Sj1pmyoRpuH7ZweP41ge2aG4Yw7CDStd
TM7jngOQymRfgLrG1jjSnEjtCEG/ZPSXQVw39Ux7NXXUbEyuA07jYhVXON1J/qgl
kL2RklPet9fjO0UTBE1TKxDepUdGECZHENUZ4q4Bo7uafSDxWY/V6b7AJm7zFZcA
tTL7fYUiZbh9m7DzZZNLyVZXRt6BfMzPlgLjK8nEZXLbvF/n0zQ=
=A/1r
-----END PGP SIGNATURE-----

--=-sL1rgkZbhhqGAClQPGna--