This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Is there a way to map pv guest pseudo physical address i

To: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Is there a way to map pv guest pseudo physical address into dom0?
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 27 Jun 2011 12:23:30 +0100
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Wei Liu <liuw@xxxxxxxxx>
Delivery-date: Mon, 27 Jun 2011 04:20:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110627093345.GH17634@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTimW6NZRSR39WpSFrKfxCtDMCheMoA@xxxxxxxxxxxxxx> <1309165317.32717.160.camel@xxxxxxxxxxxxxxxxxxxxxx> <BANLkTikK6z-e-2oEXLA7UE4qHWxnB+ra8Q@xxxxxxxxxxxxxx> <1309166253.32717.167.camel@xxxxxxxxxxxxxxxxxxxxxx> <BANLkTi=KEr3zv_S=ng2EF=-uOMupCWwmXw@xxxxxxxxxxxxxx> <20110627093345.GH17634@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Mon, 27 Jun 2011, Tim Deegan wrote:
> At 17:26 +0800 on 27 Jun (1309195596), Wei Liu wrote:
> > > You need to arrange for the Xen specific bit of the virtio frontend to
> > > do the p2m translation. All externally visible addresses from a PV guest
> > > must be in MFN space.
> > >
> > 
> > That's not a good approach. Dirvers reside on a higher level from the
> > "Xen specific bit". Doing this kind of translation will break their
> > generality. But there seems no other way to get this job done...
> This is a general problem with operating systems: bus addresses are not
> always the same as CPU memory addresses (even though in the easy case of
> a simple x86 PC they often are).  This is why OSes already have
> interfaces to allocate DMA-able memory and to translate between the
> address that CPU will map and the one the peripheral should use.  If
> your driver's not using the right address-space to program its hardware
> it is broken; the Xen PV model is just an extreme case of this.


When passing addresses to devices, drivers should use the DMA APIs to
make sure that proper address conversions take place (see
On Xen the swiotlb implementation takes care of doing pfn to mfn
conversions as well.
For example, to allocate a consistent buffer that is addressable by both
a device and the cpu, the correct API is dma_alloc_coherent, that
returns two values: the virtual address which you can use to access it
from the CPU and dma_handle which you pass to the device.

I can very well imagine that virtio drivers are not doing any of this
because they didn't need to, but it would be probably OK to submit a
patch to convert the drivers to use the proper APIs.

Xen-devel mailing list