On 02/15/2018 05:51 AM, Andrii Anisov wrote:
From: Andrii Anisov
Introduce per-vcpu scheduler operations permission verification.
As long as Xvcpuinfo are in fact scheduler configuration manipulations
there is no need to introduce specific access vectors.
Signed-off-by: Andrii Anisov
Acked-
On Thu, 2018-02-15 at 12:51 +0200, Andrii Anisov wrote:
> From: Andrii Anisov
>
> Introduce per-vcpu scheduler operations permission verification.
> As long as Xvcpuinfo are in fact scheduler configuration
> manipulations
> there is no need to introduce specific access vectors.
>
> Signed-off-by
On Tue, 2018-03-20 at 14:19 +0200, Andrii Anisov wrote:
> Dear All,
>
> Any comments for the patch?
>
> It addressed the issue mentioned here:
> https://lists.xenproject.org/archives/html/xen-devel/2017-07/msg00452
> .html
>
Oops, sorry, I had missed it.
Now I've replied. I think it still need
Dear All,
Any comments for the patch?
It addressed the issue mentioned here:
https://lists.xenproject.org/archives/html/xen-devel/2017-07/msg00452.html
--
*Andrii Anisov*
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.x
From: Andrii Anisov
Introduce per-vcpu scheduler operations permission verification.
As long as Xvcpuinfo are in fact scheduler configuration manipulations
there is no need to introduce specific access vectors.
Signed-off-by: Andrii Anisov
---
xen/xsm/flask/hooks.c | 2 ++
xen/xs