WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] Re: PMT table for XEN/IA64 (was: RE: Transparentpar

To: "Matt Chapman" <matthewc@xxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Re: PMT table for XEN/IA64 (was: RE: Transparentparavirtualization vs. xen paravirtualization)
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Mon, 31 Oct 2005 11:09:04 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 31 Oct 2005 03:06:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXdxy9dcYTeGtCzSuaLH4w3w24PBAAADQkA
Thread-topic: [Xen-ia64-devel] Re: PMT table for XEN/IA64 (was: RE: Transparentparavirtualization vs. xen paravirtualization)
Hi, Matt,
        It's not related to mapped virtual address, but only for 
physical/machine pfn. Current vnif backend (on x86) works as:

1. Allocate a set of physical pfns from kernel
2. chop up the mapping between physical pfn and old machine pfn
3. Transfer ownership of old machine pfn to frontend
4. Allocate new machine pfn and bound to that physical pfn
(In this case, there's no ownership return from frontend for performance reason)

        If without PMT table (Assuming guest==machine for dom0), that means you 
have to hotplug physical pfns from guest (based on page granularity) based on 
current vnif model. Or maybe you have better alternative without PMT, and 
without big change to existing vnif driver simultaneously?

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Matt Chapman
>Sent: 2005年10月31日 10:59
>To: Dong, Eddie
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] Re: PMT table for XEN/IA64 (was: RE:
>Transparentparavirtualization vs. xen paravirtualization)
>
>Hi Eddie,
>
>The way I did it was to make the address argument to grant
>hypercalls in/out; that is, the hypervisor might possibly return
>a different address than the one requested, like mmap on UNIX.
>
>For DomU, the hypervisor would map the page at the requested
>address.  For Dom0, the hypervisor would instead return the
>existing address of that page, since Dom0 already has access
>to the whole address space.
>
>(N.B. I'm referring to physical/machine mappings here; unlike
>the x86 implementation where the grant table ops map pages
>directly into virtual address space).
>
>Matt
>
>
>On Fri, Oct 28, 2005 at 10:28:08PM +0800, Dong, Eddie wrote:
>> >  Page flipping should work just fine
>> > in the current design; Matt had it almost working (out of tree)
>> > before he went back to school.
>> >
>> Matt:
>>      Dan mentioned that you had VNIF work almost done without PMT
>> table support for dom0, Can you share the idea with us?
>>      Usually VNIF swap page between dom0 and domU so that network
>> package copy (between dom0 native driver and domU  frontend driver) can
>> be avoided and thus achieve high performance. With this swap, we can no
>> longer assume dom0 gpn=mfn. So what did you ever propose to port VNIF
>> without PMT table?
>>      Thanks a lot, eddie
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel