> From: Volodymyr Babchuk <volodymyr_babc...@epam.com> > Sent: Wednesday, August 22, 2018 10:12 AM > > As we don't want any guest to access limited resources of TEE, we need a way > to control who can work with it. > > Thus, new access vector class "tee" is added with only ony operation "call" > so far. tee framework uses this to check if guest has a right > to work with TEE. > > Also, example security context domU_with_tee_t was added. > > Signed-off-by: Volodymyr Babchuk <volodymyr_babc...@epam.com>
Are you planning to add more access vectors to this class in the future? Otherwise, it probably doesn't need its own class - since you use xen_t as the target, placing it in class xen/xen2 is preferred (like tmem and others are now). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
