From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?=
 <marmarek@invisiblethingslab.com>
Subject: e820_host default value and libxl (not xl)
Date: Sat, 21 May 2016 04:42:11 +0200
Message-ID: <20160521024211.GK1171@mail-itl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0804501396219424649=="
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Errors-To: xen-devel-bounces@lists.xen.org
Sender: "Xen-devel" <xen-devel-bounces@lists.xen.org>
To: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org


--===============0804501396219424649==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="5QcriFbbFkKgT3aH"
Content-Disposition: inline


--5QcriFbbFkKgT3aH
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

According to xl.cfg(5) " This option defaults to true (1) if any PCI
passthrough devices are configured and false (0) otherwise."
And indeed this behaviour is implemented in xl. But not in libxl, which
means other libxl based toolstacks (libvirt) will not take advantage of
this directly.

What would be the best approach here? Duplicate that behaviour in
libvirt (currently libvirt knows nothing about this option), or move
that default handling to libxl? I think the later makes more sense, but
maybe there is some reason against it?

--=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?

--5QcriFbbFkKgT3aH
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXP8sFAAoJENuP0xzK19csqusH/3RdkgkWZaXKOcCgnIfdEvOZ
+hrUs4fDkQKZRVtS77VD7gjdTlo2GDA4r3euxeSVdmB8ExlnqPGzeG/s8L+IWbk3
Ubcy09fHK4h+2V90Unc/+8SL3zHMRL4kESfI8fgADmeBP3zqPZGlefYxcgkArTxK
FUdzEofyU+c+2vzqWvq+HUXBa+rBm8QBMePNgP1XL+aRVnzIo9HgClHijRgtroA7
x1EfipUDtwZ4VPDiWgIN9SuU3zMpekkoh9qjc0Nplfs8NBdXaydHtl42SHX3StSa
JK6RmL/Hy49FEwvcHo98n22oWUm+pu6EdxBKGdQEfK7sNPFJ+OUQFO0V3ktr6hA=
=NSa2
-----END PGP SIGNATURE-----

--5QcriFbbFkKgT3aH--


--===============0804501396219424649==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs
IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y
Zy94ZW4tZGV2ZWwK

--===============0804501396219424649==--