All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Penny Zheng <Penny.Zheng@amd.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Jason Andryuk" <jason.andryuk@amd.com>,
	"Tamas K Lengyel" <tamas@tklengyel.com>,
	"Alexandru Isaila" <aisaila@bitdefender.com>,
	"Petre Pircalabu" <ppircalabu@bitdefender.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v1 3/7] xen/monitor: wrap monitor_op under CONFIG_VM_EVENT
Date: Thu, 13 Nov 2025 10:18:07 +0100	[thread overview]
Message-ID: <e443bbe9-e2ac-42c7-803f-2017848c4f58@suse.com> (raw)
In-Reply-To: <20251113031630.1465599-4-Penny.Zheng@amd.com>

On 13.11.2025 04:16, Penny Zheng wrote:
> Feature monitor_op is based on vm event subsystem, so monitor.o shall be
> wrapped under CONFIG_VM_EVENT.
> The following functions are only invoked by monitor-op, so they all shall be
> wrapped with CONFIG_VM_EVENT (otherwise they will become unreachable and
> violate Misra rule 2.1 when VM_EVENT=n):
> - hvm_enable_msr_interception
>   - hvm_function_table.enable_msr_interception
> - hvm_has_set_descriptor_access_existing
>   - hvm_function_table.set_descriptor_access_existi
> - arch_monitor_get_capabilities
> Function monitored_msr() still needs a stub to pass compilation when
> VM_EVENT=n.
> 
> Signed-off-by: Penny Zheng <Penny.Zheng@amd.com>
> ---
> v3 -> v4:
> - a new commit split from previous "xen/vm_event: consolidate CONFIG_VM_EVENT"
> - Another blank line ahead of the #ifdef
> - Move hvm_enable_msr_interception() up into the earlier #ifdef
> - only arch_monitor_get_capabilities() needs wrapping, as this static inline
> function calls hvm_has_set_descriptor_access_exiting(), which is declared only
> when VM_EVENT=y
> ---
>  xen/arch/x86/hvm/Makefile          |  2 +-
>  xen/arch/x86/hvm/svm/svm.c         |  8 +++++++-
>  xen/arch/x86/hvm/vmx/vmx.c         | 10 ++++++++++
>  xen/arch/x86/include/asm/hvm/hvm.h | 18 +++++++++++-------
>  xen/arch/x86/include/asm/monitor.h |  9 +++++++++
>  5 files changed, 38 insertions(+), 9 deletions(-)

Same remark as for patch 2 regarding the subject prefix. Then
Acked-by: Jan Beulich <jbeulich@suse.com>

Jan


  reply	other threads:[~2025-11-13  9:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  3:16 [PATCH v1 0/7] consolidate vm event subsystem Penny Zheng
2025-11-13  3:16 ` [PATCH v1 3/7] xen/monitor: wrap monitor_op under CONFIG_VM_EVENT Penny Zheng
2025-11-13  9:18   ` Jan Beulich [this message]
2025-11-18 23:32     ` Jason Andryuk
2025-11-13  3:16 ` [PATCH v1 4/7] xen/p2m: move xenmem_access_to_p2m_access() to common p2m.c Penny Zheng
2025-11-13  9:29   ` Jan Beulich
2025-11-13  3:16 ` [PATCH v1 5/7] xen/x86: move declaration from mem_access.h to altp2m.h Penny Zheng
2025-11-13  9:35   ` Jan Beulich
2025-11-18 11:09     ` Penny, Zheng
2025-11-18 23:40       ` Jason Andryuk
2025-11-13  3:16 ` [PATCH v1 6/7] xen/mem_access: wrap memory access when VM_EVENT=n Penny Zheng
2025-11-13  9:48   ` Jan Beulich
2025-11-13  3:16 ` [PATCH v1 7/7] xen/vm_event: consolidate CONFIG_VM_EVENT Penny Zheng
2025-11-13 10:16   ` Jan Beulich
2025-11-18 23:49     ` Jason Andryuk
     [not found] ` <20251113031630.1465599-2-Penny.Zheng@amd.com>
2025-11-13  8:56   ` [PATCH v1 1/7] xen/svm: limit the scope of "rc" Jan Beulich
2025-11-18  7:11     ` Penny, Zheng
2025-11-18 23:20       ` Jason Andryuk
     [not found] ` <20251113031630.1465599-3-Penny.Zheng@amd.com>
2025-11-13  9:13   ` [PATCH v1 2/7] xen/vm_event: introduce vm_event_is_enabled() Jan Beulich
2025-11-18 10:11     ` Penny, Zheng
2025-11-18 23:30       ` Jason Andryuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e443bbe9-e2ac-42c7-803f-2017848c4f58@suse.com \
    --to=jbeulich@suse.com \
    --cc=Penny.Zheng@amd.com \
    --cc=aisaila@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jason.andryuk@amd.com \
    --cc=ppircalabu@bitdefender.com \
    --cc=roger.pau@citrix.com \
    --cc=tamas@tklengyel.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.