From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH v6 3/3] tools/libxc: use superpages during restore of HVM guest Date: Wed, 30 Aug 2017 16:27:19 +0200 Message-ID: <20170830142719.GB31711@aepfle.de> References: <20170826103332.24570-1-olaf@aepfle.de> <20170826103332.24570-4-olaf@aepfle.de> <20170830134839.liz6uo56ejjw2bsp@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6809446116468943300==" Return-path: In-Reply-To: <20170830134839.liz6uo56ejjw2bsp@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Wei Liu Cc: Andrew Cooper , Ian Jackson , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============6809446116468943300== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, Wei Liu wrote: > As far as I can tell the algorithm in the patch can't handle: >=20 > 1. First pfn in a batch points to start of second 1G address space > 2. Second pfn in a batch points to a page in the middle of first 1G > 3. Guest can only use 1G ram In which way does it not handle it? Over-allocation is supposed to be handled by the "ctx->restore.tot_pages + sp->count > ctx->restore.max_pages" checks. Do you mean the second 1G is allocated, then max_pages is reached, and allocation in other areas is not possible anymore? Can this actually happen with the available senders? If not, this is again the missing memory map. Olaf --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWabLRAAKCRBdQqD6ppg2 fr/UAJ9JTe7xpcWm4HUxAkT6WnbumAoSxQCgm/vqt9cNGlg892zUQlaYbMDkS1U= =BEPw -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- --===============6809446116468943300== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============6809446116468943300==--