Re: [PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-18 Thread Stefano Stabellini
On Tue, 18 Mar 2025, Jan Beulich wrote: > On 18.03.2025 00:55, Stefano Stabellini wrote: > > On Mon, 17 Mar 2025, Jason Andryuk wrote: > >> On 2025-03-17 10:22, Jan Beulich wrote: > >>> On 06.03.2025 23:03, Jason Andryuk wrote: > --- a/xen/include/xsm/dummy.h > +++ b/xen/include/xsm/dummy

Re: [PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-18 Thread Jan Beulich
On 18.03.2025 00:55, Stefano Stabellini wrote: > On Mon, 17 Mar 2025, Jason Andryuk wrote: >> On 2025-03-17 10:22, Jan Beulich wrote: >>> On 06.03.2025 23:03, Jason Andryuk wrote: --- a/xen/include/xsm/dummy.h +++ b/xen/include/xsm/dummy.h @@ -95,7 +95,11 @@ static always_inline int

Re: [PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-17 Thread Stefano Stabellini
On Mon, 17 Mar 2025, Jason Andryuk wrote: > On 2025-03-17 10:22, Jan Beulich wrote: > > On 06.03.2025 23:03, Jason Andryuk wrote: > > > --- a/xen/include/xsm/dummy.h > > > +++ b/xen/include/xsm/dummy.h > > > @@ -95,7 +95,11 @@ static always_inline int xsm_default_action( > > > return

Re: [PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-17 Thread Jason Andryuk
On 2025-03-17 10:22, Jan Beulich wrote: On 06.03.2025 23:03, Jason Andryuk wrote: --- a/xen/include/xsm/dummy.h +++ b/xen/include/xsm/dummy.h @@ -95,7 +95,11 @@ static always_inline int xsm_default_action( return 0; fallthrough; case XSM_PRIV: -if ( is_contr

Re: [PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-17 Thread Jan Beulich
On 06.03.2025 23:03, Jason Andryuk wrote: > --- a/xen/include/xsm/dummy.h > +++ b/xen/include/xsm/dummy.h > @@ -95,7 +95,11 @@ static always_inline int xsm_default_action( > return 0; > fallthrough; > case XSM_PRIV: > -if ( is_control_domain(src) ) > +case XSM

[PATCH 15/23] xen/xsm: Add XSM_HW_PRIV

2025-03-06 Thread Jason Andryuk
Xen includes disctinct concepts of a control domain (privileged) and a hardware domain, but there is only a single XSM_PRIV check. For dom0 this is not an issue as they are one and the same. With hyperlaunch and its build capabiliies, a non-privileged hwdom and a privileged control domain should