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

Re: [Xen-ia64-devel] Protection key support for PV domains


  • To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 20 Jul 2007 15:21:56 +0200
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 20 Jul 2007 06:19:36 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=X0qTxDSCfRHMaBD/XjHIXSYLMCXK4s8ZRq8B3y1jsYPHYYZFUV6h3glptepbG6vAOYGF7/FtW33HOb/f8buYCsxfFtLRrmJRtEUt42sopE/XTe0qQg7y+3SgTNRvEjQ+;
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Hi,

Am Freitag, 13. Juli 2007 schrieb Isaku Yamahata:
> struct mapped_regs is a part of ABI beween hypervisor and guest os
> so that the layout shouldn't be changed depending on configuration.
> Since there is no user of pkrs currently, eliminating pkrs[8]; or
> replacing pkrs[8];tmp[8]; with tmp[16]; or somethine like that
> would be fine.

Can I replace pkrs[8];tmp[8]; with pkrs[16] to use this for protection keys or 
should I expand pkrs and leave tmp[8] untouched. How about changing the 
layout - is this possible here?
In addition I would use a define for the number of pkrs. The only way to get 
this is define it in arch-ia64.h for use from vmm and domU. Is this OK or is 
there another solution possible?
Btw. I'll use Isaku's suggestion and will add a new hypercall to let vmm setup 
the cpu-pkrs with the values the domU changed.
Thanks.

Dietmar.

_______________________________________________
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®.