Re: [Xen-devel] Re: xsm: Consolidate xsm processing within domain control hypercall.

["George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>]

I've been getting together the necessary updates to XSM and Flask to deal
with the updates to domctl and a few other hypercall operations.  I've also
been working on a default module that captures the existing dom0/domU
capability model.  This default module will allow one to exercise XSM as the
extensible security framework for Xen.  However, the xsm_domctl throws a
wrench into these activities.

I'd really like to get a better understanding of the argument that motivated
the change to the creation of the xsm_domctl rollup.

> On 04/12/07 13:06 -0700, Alex Williamson wrote:
>> 
>>   Does this work right across a PV domain save/restore on x86?  On ia64
>> I end up with "Domain-Unnamed" after I save a PV domain and another
>> after I restore it, then do a shutdown.  Reverting this patch restores
>> correct behavior.  Thanks,
> 
> Keir, please revert this patch. I'll implement the flask module and
> investigate the save/restore issue, then resubmit.
> 
> thanks,
> 
> Mike

-- 
George S. Coker, II <gscoker@xxxxxxxxxxxxxx>



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