From: Jan Beulich <jbeulich@suse.com>
To: dmkhn@proton.me
Cc: andrew.cooper3@citrix.com, anthony.perard@vates.tech,
julien@xen.org, michal.orzel@amd.com, roger.pau@citrix.com,
sstabellini@kernel.org, teddy.astie@vates.tech, dmukhin@ford.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 1/2] xen/domain: introduce common hardware emulation flags
Date: Wed, 4 Jun 2025 12:36:17 +0200 [thread overview]
Message-ID: <093dc85d-ebf3-4982-8888-db4e7cfd0e45@suse.com> (raw)
In-Reply-To: <20250602191717.148361-2-dmukhin@ford.com>
On 02.06.2025 21:17, dmkhn@proton.me wrote:
> From: Denis Mukhin <dmukhin@ford.com>
>
> Add common emulation_flags for configuring domain emulation features.
>
> Print d->emulation_flags from 'q' keyhandler for better traceability while
> debugging.
>
> Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
It's not becoming clear why this would want doing, nor in how far some of
the bits there may gain "common" meaning, too. Imo this kind of change is
meaningful only in a series where later the common-ness is also used.
Jan
next prev parent reply other threads:[~2025-06-04 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 19:17 [PATCH v5 0/2] xen/domain: updates to hardware emulation flags dmkhn
2025-06-02 19:17 ` [PATCH v5 1/2] xen/domain: introduce common " dmkhn
2025-06-04 10:36 ` Jan Beulich [this message]
2025-06-05 1:17 ` dmkhn
2025-06-05 6:44 ` Jan Beulich
2025-06-05 23:46 ` Stefano Stabellini
2025-06-06 7:33 ` dmkhn
2025-06-05 9:08 ` Roger Pau Monné
2025-06-06 7:18 ` dmkhn
2025-06-02 19:17 ` [PATCH v5 2/2] xen/domain: rewrite emulation_flags_ok() dmkhn
2025-06-04 10:43 ` Jan Beulich
2025-06-05 2:00 ` dmkhn
2025-06-05 8:58 ` Roger Pau Monné
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=093dc85d-ebf3-4982-8888-db4e7cfd0e45@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--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.