VM event could only be enabled/disabled via vm_event domctl-op, so
CONFIG_VM_EVENT shall depend on CONFIG_MGMT_HYPERCALLS

Signed-off-by: Penny Zheng <Penny.Zheng@amd.com>
---
v1 -> v2:
- adapt to changes of "unify DOMCTL to MGMT_HYPERCALLS"
---
 xen/common/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xen/common/Kconfig b/xen/common/Kconfig
index c1571377d3..1aedd00b12 100644
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -176,7 +176,7 @@ config MEM_ACCESS_ALWAYS_ON
 config VM_EVENT
 	def_bool MEM_ACCESS_ALWAYS_ON
 	prompt "Memory Access and VM events" if !MEM_ACCESS_ALWAYS_ON
-	depends on HVM
+	depends on HVM && MGMT_HYPERCALLS
 	help
 
 	  Framework to configure memory access types for guests and receive
-- 
2.34.1

On 10.09.2025 09:38, Penny Zheng wrote:
> VM event could only be enabled/disabled via vm_event domctl-op, so
> CONFIG_VM_EVENT shall depend on CONFIG_MGMT_HYPERCALLS
> 
> Signed-off-by: Penny Zheng <Penny.Zheng@amd.com>

Looks plausible to me, so:
Acked-by: Jan Beulich <jbeulich@suse.com>
but really Tamas (now Cc-ed) should also get a chance to express possible
concerns.

Jan

On Wed, Sep 10, 2025 at 11:06 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 10.09.2025 09:38, Penny Zheng wrote:
> > VM event could only be enabled/disabled via vm_event domctl-op, so
> > CONFIG_VM_EVENT shall depend on CONFIG_MGMT_HYPERCALLS
> >
> > Signed-off-by: Penny Zheng <Penny.Zheng@amd.com>
>
> Looks plausible to me, so:
> Acked-by: Jan Beulich <jbeulich@suse.com>
> but really Tamas (now Cc-ed) should also get a chance to express possible
> concerns.

No concerns, thanks.

Tamas