Xen devel - May 2005 - RE: [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
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 5/25/05, Ling, Xiaofeng <xiaofeng.ling@intel.com>
wrote:
> Is there any comment for this patch?
> Is it acceptable or not?
yes, i have the same question. sometimes patches sent to the list
receive no comment. that means they are in queu for review, and get
feedbacks later? or we should re-send the patches to the list (as in
LKML) ?

i think the policy of accepting patches should be made clear, and put
into the FAQ. that would be appreciated by contributors.

thank you,
aq

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