[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • From: "Ling, Xiaofeng" <xiaofeng.ling@xxxxxxxxx>
  • Date: Wed, 25 May 2005 10:19:18 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 25 May 2005 02:20:03 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVdBMqGMA2IEEsTSdm26uwqvN7GUwDyn0Kw
  • Thread-topic: [Xen-devel] [PATCH]vbd/vnif paravirtulization driver hypervisorsupport]

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

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.