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-devel

RE: [Xen-devel] [PATCH]vbd/vnif paravirtulization driver hypervisorsuppo

To: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH]vbd/vnif paravirtulization driver hypervisorsupport]
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 25 May 2005 06:00:33 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 May 2005 04:59:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVdBMqGMA2IEEsTSdm26uwqvN7GUwDyn0KwAAWzq3A=
Thread-topic: [Xen-devel] [PATCH]vbd/vnif paravirtulization driver hypervisorsupport]
 

> Is there any comment for this patch?
> Is it acceptable or not?

I think it needs a more work. Using grant tables should help unify
things. I'm convinced that you're missing out on some unifying paradigm
that will cause many of the "if(VMX_DOMAIN(current))" clauses to
evaporate. 

I'll think a bit more about this and get back to you.

BTW: have you performance figures?

Best,
Ian

 
> Xiaofeng Ling <> wrote:
> > This patch adds paravirutulization driver support for vmx domain in 
> > hypervisor.  The VBD and VNIF frontend driver can then be used in 
> > unmodified kernel as a module to get better performance than device 
> > model. The backend driver needs no change and can work together with
> > xeno-linux.   
> > The event channel mechanism works as a pci device in guest 
> linux, so a 
> > event channel device driver will as basic module in guest kernel.
> > 
> > What's the patch done is:
> > 1.copy_to/from_guest support, which is used to copy context from/to 
> > guest space to hypervisor space.
> > 2.copy_to/from_user will call copy_to/from_guest for a vmx domain.
> > 3.A separate hypercall table for paravirutulization driver 
> which mask 
> > some unused entries.
> > 4.add hypercalls for address translation.and share page 
> mapping (event
> >   channel and grant table)
> > 5.clean some hypercalls path for vmx domain.
> 

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