From: Jan Beulich <jbeulich@suse.com>
To: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/4] x86:monitor: control monitor.c build with CONFIG_VM_EVENT option
Date: Thu, 30 Jan 2025 14:27:47 +0100 [thread overview]
Message-ID: <c0a9c3fa-1812-4a7f-9508-aa109c3221d7@suse.com> (raw)
In-Reply-To: <6fe254034570e1443a41c7dc5e3e3767b9c77f79.1737452864.git.Sergiy_Kibrik@epam.com>
On 21.01.2025 11:21, Sergiy Kibrik wrote:
> Replace more general CONFIG_HVM option with CONFIG_VM_EVENT which is more
> relevant and specific to monitoring. This is only to clarify at build level
> to which subsystem this file belongs.
>
> No functional change here, as VM_EVENT depends on HVM.
>
> Signed-off-by: Sergiy Kibrik <Sergiy_Kibrik@epam.com>
As long as patch 1 stays roughly as it is right now:
Acked-by: Jan Beulich <jbeulich@suse.com>
Jan
next prev parent reply other threads:[~2025-01-30 13:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 10:17 [PATCH v2 0/4] make build of vm_event/mem_access/monitor optional Sergiy Kibrik
2025-01-21 10:19 ` [PATCH v2 1/4] xen: kconfig: rename MEM_ACCESS -> VM_EVENT Sergiy Kibrik
2025-01-30 13:24 ` Jan Beulich
2025-01-31 0:26 ` Tamas K Lengyel
2025-01-31 6:30 ` Jan Beulich
2025-01-31 23:36 ` Tamas K Lengyel
2025-02-03 7:36 ` Jan Beulich
2025-02-04 1:07 ` Tamas K Lengyel
2025-01-30 13:26 ` Jan Beulich
2025-01-31 0:29 ` Tamas K Lengyel
2025-01-21 10:21 ` [PATCH v2 2/4] x86:monitor: control monitor.c build with CONFIG_VM_EVENT option Sergiy Kibrik
2025-01-30 13:27 ` Jan Beulich [this message]
2025-01-21 10:23 ` [PATCH v2 3/4] automation: rename CONFIG_MEM_ACCESS -> CONFIG_VM_EVENT Sergiy Kibrik
2025-01-22 8:03 ` Nicola Vetrini
2025-01-30 13:14 ` Jan Beulich
2025-01-21 10:25 ` [PATCH v2 4/4] xen: mem_access: conditionally compile vm_event.c & monitor.c Sergiy Kibrik
2025-01-30 13:32 ` Jan Beulich
2025-01-31 0:33 ` Tamas K Lengyel
2025-01-31 6:42 ` Jan Beulich
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=c0a9c3fa-1812-4a7f-9508-aa109c3221d7@suse.com \
--to=jbeulich@suse.com \
--cc=Sergiy_Kibrik@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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.