All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>
Cc: "Jan Beulich" <jbeulich@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Julien Grall" <julien@xen.org>, "Wei Liu" <wl@xen.org>,
	<sergiy_kibrik@epam.com>
Subject: Re: [PATCH v2 1/4] x86: provide an inverted Kconfig control for shim-exclusive mode
Date: Fri, 17 Jan 2025 12:24:54 +0000	[thread overview]
Message-ID: <D74CH4RDRRR9.ZR6RL8U6PQ56@cloud.com> (raw)
In-Reply-To: <Z4oxZSUQ6VARiR0H@macbook.local>

On Fri Jan 17, 2025 at 10:31 AM GMT, Roger Pau Monné wrote:
> On Thu, Jan 16, 2025 at 04:31:46PM -0800, Stefano Stabellini wrote:
> > On Wed, 1 Mar 2023, Jan Beulich wrote:
> > > While we want certain things turned off in shim-exclusive mode, doing
> > > so via "depends on !PV_SHIM_EXCLUSIVE" badly affects allyesconfig: Since
> > > that will turn on PV_SHIM_EXCLUSIVE, other options will be turned off as
> > > a result. Yet allyesconfig wants to enable as much of the functionality
> > > as possible.
> > > 
> > > Retain PV_SHIM_EXCLUSIVE as a prompt-less option such that first of all
> > > C code using it can remain as is. This isn't just for less code churn,
> > > but also because I think that symbol is more logical to use in many
> > > (all?) places.
> > > 
> > > Requested-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > > Signed-off-by: Jan Beulich <jbeulich@suse.com>
> > >
> > > ---
> > > The new Kconfig control's name is up for improvement suggestions, but I
> > > think it's already better than the originally thought of
> > > FULL_HYPERVISOR.
> > 
> > I think the approach in general is OK, maybe we can improve the naming
> > further. What about one of the following?
> > 
> > NO_PV_SHIM_EXCLUSIVE
> > PV_SHIM_NOT_EXCLUSIVE
>
> IMO negated options are confusing, and if possible I think we should
> avoid using them unless strictly necessary.

The problem is that the option is negative in nature. It's asking for
hypervisor without _something_. I do agree with Stefano that shim would be
better in the name. Otherwise readers are forced to play divination tricks.

How about something like:

    SHIMLESS_HYPERVISOR

That's arguably not negated, preserves "shim" in the name and has the correct
polarity for allyesconfig to yield the right thing.

>
> I for example always considered extremely confusing that previous to
> having CONFIG_DEBUG Xen used NDEBUG (so no debug) as a way to signal
> debug vs non-debug builds.
>
> Thanks, Roger.

Cheers,
Alejandro


  reply	other threads:[~2025-01-17 12:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 14:11 [PATCH v2 0/4] x86/pv-shim: configuring / building re-arrangements Jan Beulich
2023-03-01 14:13 ` [PATCH v2 1/4] x86: provide an inverted Kconfig control for shim-exclusive mode Jan Beulich
2025-01-17  0:31   ` Stefano Stabellini
2025-01-17  7:23     ` Jan Beulich
2025-01-17 10:31     ` Roger Pau Monné
2025-01-17 12:24       ` Alejandro Vallejo [this message]
2025-01-17 12:41         ` Jan Beulich
2025-01-17 22:43           ` Stefano Stabellini
2025-01-17 23:41             ` Andrew Cooper
2025-01-20  7:53               ` Jan Beulich
2025-01-20 23:27                 ` Stefano Stabellini
2025-01-21  8:13                   ` Jan Beulich
2025-01-21  8:52                     ` Roger Pau Monné
2025-01-21 10:35                       ` Jan Beulich
2025-01-21 18:02                         ` Roger Pau Monné
2025-01-22  8:43                           ` Jan Beulich
2025-01-22  9:49                             ` Roger Pau Monné
2025-01-22 13:24                               ` Jan Beulich
2025-01-22 21:50                                 ` Stefano Stabellini
2025-02-18 19:01                                   ` Stefano Stabellini
2023-03-01 14:14 ` [PATCH v2 2/4] common: reduce PV shim footprint Jan Beulich
2023-03-01 14:15 ` [PATCH v2 3/4] x86/pv-shim: don't even allow enabling GRANT_TABLE Jan Beulich
2023-03-01 14:16 ` [PATCH v2 4/4] x86/pv-shim: suppress core-parking logic 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=D74CH4RDRRR9.ZR6RL8U6PQ56@cloud.com \
    --to=alejandro.vallejo@cloud.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sergiy_kibrik@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.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.