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

[Xen-ia64-devel] [RFC][PATCH] support special domU optimisation's in the hypervisor


  • To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 27 Jun 2007 13:57:03 +0200
  • Delivery-date: Wed, 27 Jun 2007 04:54:55 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=jTDTPVlNZbyxVI3jECQNPMbUYsTpN6h0DONCrdzYlrGTxbQ2BgzHF2F/IgheefJTGK8RPx2LarM3IQKO7LLfMANDXOdk3PRXE6OJ6D6PysaFx8xEBP0hqV18cowd6/wp;
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Hi,

attached is a patch to the discussion on
http://lists.xensource.com/archives/html/xen-ia64-devel/2007-06/msg00273.html
I added a new 'struct opt_feature' to the struct arch_domain. Further I added 
a new hypercall interface, which sets a flag in the mask in the struct 
opt_feature and a value for the pte-flags.
My problem here is, that I found 2 hypercall interfaces:
1. the common using the ia64_hypercall_table
2. the special way via ia64_hypercall()
In my opinion this opt_feature hypercall should be a common hypercall usable 
from dom0 and domU. So I have now a mixture of both. The interface from the 
user is similar to the point 1 with
HYPERVISOR_opt_feature(int cmd, void *arg) via xencomm and _hypercallN
but with the exit in ia64_hypercall().
Maybe I overlooked the better way!?
I tested this feature with a small change in mini-os.
Please have a look and send comments or checkin the patch.
The next step is the patch for dom0/domU linux to switch this feature on.
Thanks.

Dietmar

Attachment: opt_feature.patch
Description: Text Data

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

 


Rackspace

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