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
 
   
 

xense-devel

Re: [Xense-devel] ACM doesnt scale

To: aq <aquynh@xxxxxxxxx>
Subject: Re: [Xense-devel] ACM doesnt scale
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Thu, 23 Jun 2005 23:31:33 +0100
Cc: xense-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Jun 2005 22:30:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Message from aq <aquynh@xxxxxxxxx> of "Fri, 24 Jun 2005 07:23:37 +0900." <9cde8bff05062315239f384cb@xxxxxxxxxxxxxx>
List-help: <mailto:xense-devel-request@lists.xensource.com?subject=help>
List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
List-post: <mailto:xense-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
>at the moment, ACM supports only 2 models, and the code doesnt scale
>enough (at all) to support more models in the future? any plan to fix
>that?

Yes - the current ACM code is a proof of concept derived from the 
IBM sHype code. The model at present is that two policies (a primary
and secondary) will be in place at any time, although it is intended
that the selection of these will be more dynamic in the future. It's
not yet clear if extending this will be required, but we're certainly
aware of the structure and limitations of the current code. 

>if no, i am ready to offer some code for this problem.

We don't really want to smother things with code - for the security
functionality in particular we'd prefer to generate a stable, sensible
and well-justified design or set of designs which we can consider and 
decide upon. 

If you're keen to help with this process, one important task we hope 
to get rolling soon is a complete audit of the 'hypervisor interface', 
aka all the regular hypercalls & dom0_ops, plus the implicit protocols
(shared info page, event channel & grant table state machines, etc) to
identify the various points at which access control or information  
exchange can occur. 

cheers,

S.

_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel