From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= Subject: PVH hypercall interface Date: Mon, 8 Aug 2016 12:21:40 +0200 Message-ID: <20160808102140.GF24847@mail-itl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3357621288932168866==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel Cc: Joanna Rutkowska List-Id: xen-devel@lists.xenproject.org --===============3357621288932168866== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Fr7jhMP26BSURKlp" Content-Disposition: inline --Fr7jhMP26BSURKlp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, What hypercalls are available for PVH guests? How is it different for HVM guests? Is it documented somewhere? For example I'd expect that do_mmu_update is available only for PV guests, but looking at the code I can't find anything preventing other guest types from using it (no, some obscure conditions deep in execution path doesn't count). --=20 Best Regards, Marek Marczykowski-G=C3=B3recki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? --Fr7jhMP26BSURKlp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXqF01AAoJENuP0xzK19csf/EH/ipMMiFCnyHTBhTp6+Hm824a 15oDgwCAaYKUA8dXDJkbfHnyie/RZQk7MbfhSyoijxo2mFzznSI1keVOVQ/ThCCR g5JKIwhq2yqJwdHrO1/LfHucmq5ptpW7m2qQOfZWE5NadG8kD3S8qaP3mAsWkqYU K+1yhTrDfVi7gDl6bhslvsm2mr+gLySkwElmACRGc600wFNj/NKxdMwkWUO6te1N qnjefM9zK6EmWquw05z26lRTcxG7u0Ad9vkf7ye9KJvgG6O6YUMGDEUSy1CctAKf zCOdky9PSPN/gG1MEpYHUhHmN44bMp0/lL6Se45CKN6loM2V+lzgTiqO9bq6FU0= =62+s -----END PGP SIGNATURE----- --Fr7jhMP26BSURKlp-- --===============3357621288932168866== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3357621288932168866==--