Re: [Xen-devel] XSM instead of IS_PRIV

[Keir Fraser <keir.xen@xxxxxxxxx>]

On 01/08/2012 03:51, "Shakeel Butt" <shakeel.butt@xxxxxxxxx> wrote:

>> Once this is done, it will make sense to change the XSM header file so
>> that the appropriate xsm_* hooks resolve to IS_PRIV when XSM is not
>> enabled. This would allow the IS_PRIV hooks covered by XSM to be
>> completely removed, assuming the Xen developers agree that the XSM hooks
>> cover all all the important code.
> 
> Thanks for replying. So, is there consensus among the Xen community
> to adopt this patch (xsm hooks replacing IS_PRIV) on upstream Xen?

Assuming it can be done cleanly and comprehensively, with same behaviour as
IS_PRIV for an out-of-the-box setup, yes. What's not to like about that? :)

 -- Keir

> thanks,
> Shakeel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel