xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/3] xen/x86: Drop the uses of invbool_param()
Date: Thu, 11 Feb 2016 09:58:38 +0000	[thread overview]
Message-ID: <1455184718.814.21.camel@citrix.com> (raw)
In-Reply-To: <56B9EDA602000078000D00CF@prv-mh.provo.novell.com>

On Tue, 2016-02-09 at 05:46 -0700, Jan Beulich wrote:
> > > > On 08.02.16 at 18:07, <andrew.cooper3@citrix.com> wrote:
> > There are only four users, and invbool_param() is an unnecessary
> > cognitive
> > overhead to use.
> 
> While this isn't necessarily a bad change, I don't agree to either of
> these arguments. So I'm going to make my ack here dependent on
> seeing some kind of positive feedback on patch 2 by another
> REST maintainer.

FWIW I do have to think a little harder about the double negative in
        bool_t foo; /* implicitly 0  init */
        invbool_param("foo", foo_disabled);
and what no-foo on the command line actually does in this case than I would
otherwise with:
        bool_t foo = true;
        boolean_param("foo", foo);

AFAICT the only real benefit of the inversion is that the variable can live
in .bss instead of .data, but it's a total of 4 bool_t's (so 4 bytes? Or
maybe 16 at the most) which hardly seems worth it to me.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-02-11  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 17:07 [PATCH 1/3] xen/x86: Drop the uses of invbool_param() Andrew Cooper
2016-02-08 17:07 ` [PATCH 2/3] xen/init: Drop invbool_param() Andrew Cooper
2016-02-09 12:47   ` Jan Beulich
2016-02-08 17:07 ` [PATCH 3/3] xen/init: Annotate all command line parameter infrastructure as const Andrew Cooper
2016-02-09 12:43   ` Jan Beulich
2016-02-09 13:52     ` Andrew Cooper
2016-02-09 14:32       ` Jan Beulich
2016-02-09 14:40         ` Andrew Cooper
2016-02-09 14:50           ` Jan Beulich
2016-02-22 16:36   ` Jan Beulich
2016-02-22 16:41     ` Andrew Cooper
2016-02-22 18:43     ` Doug Goldstein
2016-02-23  8:07       ` Jan Beulich
2016-02-09 12:46 ` [PATCH 1/3] xen/x86: Drop the uses of invbool_param() Jan Beulich
2016-02-11  9:58   ` Ian Campbell [this message]

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=1455184718.814.21.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).