From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= Subject: Re: xc_evtchn_status fails with EFAULT on HVM, the same on PV works Date: Fri, 13 Jan 2017 19:59:22 +0100 Message-ID: <20170113185922.GL1341@mail-itl> References: <20170113173130.GI5268@mail-itl> <20170113180348.GJ5268@mail-itl> <3f9e01ca-3450-6af9-eb0c-8c867c3a6f96@citrix.com> <20170113183239.GK5268@mail-itl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3525281264378967308==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Andrew Cooper Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --===============3525281264378967308== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3U8TY7m7wOx7RL1F" Content-Disposition: inline --3U8TY7m7wOx7RL1F Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 13, 2017 at 06:37:06PM +0000, Andrew Cooper wrote: > On 13/01/17 18:32, Marek Marczykowski-G=C3=B3recki wrote: > > On Fri, Jan 13, 2017 at 06:15:35PM +0000, Andrew Cooper wrote: > >> Can you get the result of this piece of debugging in the failure case? > > I've got this: > > ** d4v0 CFG(24, 00007f794bd07004, 1) =3D 24 >=20 > Silly question (and I really hope the answer isn't yes, but I have a > sinking feeling it is). >=20 > Is the guest in question using SMAP? If so, does disabling SMAP fix the > problem? How can I check that? If looking at 0x200000 CR4 bit in `xl debug-keys v` output enough, then yes - it's enabled. And booting hypervisor with smap=3D0 "fixed" the problem. So, what would be the correct solution? I'd prefer not to disable SMAP "just" for this reason... --=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? --3U8TY7m7wOx7RL1F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYeSOKAAoJENuP0xzK19csUgIH/jKc0f9mho2//Y9vGL/kUK9m iuf5mFB+l9lspC1zJUmpDuLfle71BI/NDGsdooT+nPcPDclgFayezyzteAqgW0+7 CaHLGhOj29PouDK7kQSwlSuz0Nwx4+j7aVoeEtKYwj5fbyvVoU9eseNxDE1s44rn 2g/hdL/GN9aEl7FRTOPP5frhpDW/cQvKWALAwY9B9oFq+luWzSZRXSXA9Xvg3/1v bYXc3Jz0CPgvkkqPCaRb27OTHoCLkjggM8TDlkbuSiDu4Pa/kreFKJZBSkxt/CmG gUjhDU1Yaer9B3ORasbc+nrZ8B7t7gGL6Y5mSSUmkxZGN2mlh5ifqkIXzCS6F2Q= =DTt4 -----END PGP SIGNATURE----- --3U8TY7m7wOx7RL1F-- --===============3525281264378967308== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3525281264378967308==--