On 11/11/2014 08:28 PM, M A Young wrote:
> The build of xen-4.5.0-rc2 fails if XSM_ENABLE=y due to an inconsistency
> in commit fda1614 "xen/arm: Add support for GICv3 for domU" which uses
> XEN_DOMCTL_configure_domain in xen/xsm/flask/hooks.c and
> xen/xsm/flask/policy/access_vectors but XEN_DOMCT
On Tue, 2014-11-11 at 21:24 -0500, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 11, 2014 at 08:28:38PM +, M A Young wrote:
> > The build of xen-4.5.0-rc2 fails if XSM_ENABLE=y due to an inconsistency in
> > commit fda1614 "xen/arm: Add support for GICv3 for domU" which uses
> > XEN_DOMCTL_configu
On Tue, Nov 11, 2014 at 08:28:38PM +, M A Young wrote:
> The build of xen-4.5.0-rc2 fails if XSM_ENABLE=y due to an inconsistency in
> commit fda1614 "xen/arm: Add support for GICv3 for domU" which uses
> XEN_DOMCTL_configure_domain in xen/xsm/flask/hooks.c and
> xen/xsm/flask/policy/access_vec
The build of xen-4.5.0-rc2 fails if XSM_ENABLE=y due to an inconsistency
in commit fda1614 "xen/arm: Add support for GICv3 for domU" which uses
XEN_DOMCTL_configure_domain in xen/xsm/flask/hooks.c and
xen/xsm/flask/policy/access_vectors but XEN_DOMCTL_arm_configure_domain
elsewhere.
M