From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [RFC PATCH 2/3] arch, arm32: add the XEN_DOMCTL_memory_mapping hypercall Date: Mon, 3 Mar 2014 16:33:51 +0100 Message-ID: <1393860831.4058.103.camel@Solace> References: <1393721365-22458-1-git-send-email-avanzini.arianna@gmail.com> <1393721365-22458-3-git-send-email-avanzini.arianna@gmail.com> <53130053.9050801@linaro.org> <1393847789.4058.62.camel@Solace> <53149DDA.2030706@linaro.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4050842686456288639==" Return-path: In-Reply-To: <53149DDA.2030706@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: paolo.valente@unimore.it, Ian Campbell , stefano.stabellini@eu.citrix.com, Tim Deegan , xen-devel@lists.xen.org, julien.grall@citrix.com, etrudeau@broadcom.com, Arianna Avanzini , viktor.kleinik@globallogic.com List-Id: xen-devel@lists.xenproject.org --===============4050842686456288639== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Ck9Pz6xmrwjQJjPhiJzh" --=-Ck9Pz6xmrwjQJjPhiJzh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On lun, 2014-03-03 at 23:20 +0800, Julien Grall wrote: > On 03/03/14 19:56, Dario Faggioli wrote: > > Right. FTR, xen/arch/x86/domain_build.c, has this (also in > > construct_dom0): > > > > /* DOM0 is permitted full I/O capabilities. */ > > rc |=3D ioports_permit_access(dom0, 0, 0xFFFF); > > rc |=3D iomem_permit_access(dom0, 0UL, ~0UL); > > rc |=3D irqs_permit_access(dom0, 1, nr_irqs_gsi - 1); > > > > Do you want a patch to that/similar effect? >=20 > Yes. Maybe a bit more smarter than permitting full I/0 caps for dom0. >=20 EhEh... do you mean to say that x86 is "not smart" ? :-) > > So, this is probably me messing up with the terminology, but what > > 'devices passthrough to it [dom0]' would mean, for example in cases > > where we don't have an IOMMU (like cubie* boards), and hence where > > proper passtrhogh will never be, I think, supported? Or do we plan to > > have it working there too? >=20 > My term seems to be wrong for dom0 :). >=20 > On ARM, some device is used by Xen and therefore not exposed to dom0. By= =20 > passthrough to dom0 I meant every device that are given to dom0, no=20 > matter if the platform has an IOMMU. >=20 Ok, now I got it. > I think DOM0 should only be able to map theses devices to a guest. It=20 > seems stupid to allow dom0 mapping RAM or the UART used by Xen. >=20 I see, and it does make sense. Of course, I really don't know what these devices are and what the best approach would be to hide/revoke permissions to their iomem/irqs (e.g., allow everything and then revoke some, allow selectively in the first place, etc.). I'm quite sure Arianna is keen on helping with this, but it better be, if possible, someone of you ARM folks suggesting her what, where and how. :-) Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-Ck9Pz6xmrwjQJjPhiJzh 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) iEYEABECAAYFAlMUoN8ACgkQk4XaBE3IOsTh1ACeOlKYDSPIlqlGXXpafS5w1qSk vr4AnjZcMIghhK/5gQSr2vPFm0iPODRS =AyUw -----END PGP SIGNATURE----- --=-Ck9Pz6xmrwjQJjPhiJzh-- --===============4050842686456288639== 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 --===============4050842686456288639==--