All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: ray.huang@amd.com, grygorii_strashko@epam.com,
	Penny Zheng <Penny.Zheng@amd.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/7] xen/xsm: wrap xsm_vm_event_control() with CONFIG_VM_EVENT
Date: Tue, 25 Nov 2025 16:01:34 +0100	[thread overview]
Message-ID: <04644f55-457a-407d-9895-ca73f508fb5c@suse.com> (raw)
In-Reply-To: <d441c5b1-7ab0-4b28-b00a-67b8d6869fbf@apertussolutions.com>

On 25.11.2025 15:57, Daniel P. Smith wrote:
> On 11/21/25 4:15 AM, Penny Zheng wrote:
>> Function xsm_vm_event_control() is only invoked under CONFIG_VM_EVENT, so
>> it shall be wrapped with it, otherwiae it will become unreachable when
> 
> otherwiae --> otherwise (maybe committer is willing to fix on commit?)

Sure.

Jan


  reply	other threads:[~2025-11-25 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  9:15 [PATCH v3 0/7] consolidate vm event subsystem Penny Zheng
2025-11-21  9:15 ` [PATCH v3 1/7] xen/x86: move declaration from mem_access.h to altp2m.h Penny Zheng
2025-11-21  9:15 ` [PATCH v3 2/7] xen/xsm: wrap xsm_vm_event_control() with CONFIG_VM_EVENT Penny Zheng
2025-11-25 14:57   ` Daniel P. Smith
2025-11-25 15:01     ` Jan Beulich [this message]
2025-11-21  9:15 ` [PATCH v3 4/7] x86/monitor: wrap monitor_op under CONFIG_VM_EVENT Penny Zheng
2025-11-21  9:15 ` [PATCH v3 5/7] xen/p2m: move xenmem_access_to_p2m_access() to common p2m.c Penny Zheng
2025-11-24 14:01   ` Jan Beulich
2025-11-21  9:15 ` [PATCH v3 6/7] xen/mem_access: wrap memory access when VM_EVENT=n Penny Zheng
2025-11-24 14:09   ` Jan Beulich
2025-12-01  3:46     ` Penny, Zheng
2025-11-21  9:15 ` [PATCH v3 7/7] xen/vm_event: consolidate CONFIG_VM_EVENT Penny Zheng

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=04644f55-457a-407d-9895-ca73f508fb5c@suse.com \
    --to=jbeulich@suse.com \
    --cc=Penny.Zheng@amd.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=grygorii_strashko@epam.com \
    --cc=ray.huang@amd.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.