From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [RFC PATCH v2 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall Date: Fri, 14 Mar 2014 17:25:21 +0100 Message-ID: <1394814321.4159.236.camel@Solace> References: <1394439953-5723-1-git-send-email-avanzini.arianna@gmail.com> <1394439953-5723-4-git-send-email-avanzini.arianna@gmail.com> <1394724477.25873.105.camel@kazak.uk.xensource.com> <5321D005.8020203@linaro.org> <1394728598.4159.47.camel@Solace> <5321E111.2000103@linaro.org> <1394731935.16364.36.camel@kazak.uk.xensource.com> <1394735851.4159.82.camel@Solace> <1394790366.16364.64.camel@kazak.uk.xensource.com> <1394799318.4159.183.camel@Solace> <1394801349.6442.68.camel@kazak.uk.xensource.com> <1394811906.4159.229.camel@Solace> <1394813999.6442.147.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1309961981869095685==" Return-path: In-Reply-To: <1394813999.6442.147.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: paolo.valente@unimore.it, Keir Fraser , stefano.stabellini@eu.citrix.com, Ian.Jackson@eu.citrix.com, Julien Grall , Tim Deegan , xen-devel@lists.xen.org, julien.grall@citrix.com, etrudeau@broadcom.com, Jan Beulich , Arianna Avanzini , viktor.kleinik@globallogic.com List-Id: xen-devel@lists.xenproject.org --===============1309961981869095685== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-REmg+X0Ta0ma0ACRCK2l" --=-REmg+X0Ta0ma0ACRCK2l Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On ven, 2014-03-14 at 16:19 +0000, Ian Campbell wrote: > On Fri, 2014-03-14 at 16:45 +0100, Dario Faggioli wrote: > > > If "one" here is the user then I don't think so. > > >=20 > > Well, fact is "user", in this context, is who puts the embedded system > > together into a product, rather than folks actually using such product, > > so, I don't see that much unlikely. >=20 > I don't imagine even those folks are going to want to hack the > hypervisor to change the guest address space layout, so I don't think > you can assume they have full control, they will get whatever the layout > for that version of Xen is.=20 > Don't want to speak for someone else, of course. For what I've seen, no, they're not going to hack Xen, they're going to stick to a specific version as long as possible. For different reasons, that's not much different from what happens in way less embedded contexts, I think. :-) > They do control the hypervisor version so I > suppose they control in that sense. >=20 Indeed that was the control I meant. Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-REmg+X0Ta0ma0ACRCK2l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlMjLXEACgkQk4XaBE3IOsRJ3wCfRW/YV0RIS+HRAcY89nxb44J5 JS8AoIP/czQalIZo8q6WdpjB7mm0Nafy =a4IZ -----END PGP SIGNATURE----- --=-REmg+X0Ta0ma0ACRCK2l-- --===============1309961981869095685== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============1309961981869095685==--