xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Wei Liu <wl@xen.org>
Subject: Re: [PATCH 5/5] x86: don't build unused entry code when !PV32
Date: Mon, 4 Jan 2021 16:53:58 +0100	[thread overview]
Message-ID: <20210104155358.snzakj4kcs47tt22@Air-de-Roger> (raw)
In-Reply-To: <0341c1f1-dc50-552c-f246-56605ae7c83a@suse.com>

On Mon, Jan 04, 2021 at 02:56:12PM +0100, Jan Beulich wrote:
> On 28.12.2020 16:30, Roger Pau Monné wrote:
> > I would like to have Andrew's opinion on this one (as you and him tend
> > to modify more asm code than myself). There are quite a lot of
> > addition to the assembly code, and IMO it makes the code more complex
> > which I think we should try to avoid, as assembly is already hard
> > enough.
> 
> Well, while I can see your point (and I indeed asked myself the same
> question when making this change), this merely follows the route
> started with the addition on CONFIG_PV conditionals. If we think that
> prior step didn't set a good precedent, we ought to undo it.
> Otherwise I see no good argument against doing the same kind of
> transformation a 2nd time (and further ones, if need be down the
> road).

I think we need to apply some common sense and reach consensus about
where it's fine to make code conditional at build time as to not make
the existing code much harder to read and reason about. This is mostly
a subjective decision, so I understand your concern.

I still think I would like Andrew opinion on this one, as said you and
him are the ones mostly doing assembly coding. I find it already hard
to follow myself without the conditionals.

Thanks, Roger.


  reply	other threads:[~2021-01-04 15:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  8:42 [PATCH 0/5] x86: asm-offsets.h and !PV32 adjustments Jan Beulich
2020-11-25  8:45 ` [PATCH 1/5] x86/build: limit rebuilding of asm-offsets.h Jan Beulich
2020-12-28 12:00   ` Roger Pau Monné
2021-01-04 13:46     ` Jan Beulich
2020-11-25  8:49 ` [PATCH 2/5] x86/build: limit #include-ing by asm-offsets.c Jan Beulich
2020-12-28 12:54   ` Roger Pau Monné
2021-01-04 13:48     ` Jan Beulich
2020-11-25  8:49 ` [PATCH 3/5] x86/build: restrict contents of asm-offsets.h when !HVM / !PV Jan Beulich
2020-12-28 13:07   ` Roger Pau Monné
2020-11-25  8:50 ` [PATCH 4/5] x86: hypercall vector is unused when !PV32 Jan Beulich
2020-12-28 13:37   ` Roger Pau Monné
2020-11-25  8:51 ` [PATCH 5/5] x86: don't build unused entry code " Jan Beulich
2020-12-28 15:30   ` Roger Pau Monné
2021-01-04 13:56     ` Jan Beulich
2021-01-04 15:53       ` Roger Pau Monné [this message]
2021-01-04 16:11         ` Jan Beulich
2021-04-01  7:51         ` Ping: " Jan Beulich
2021-04-01 14:01   ` Roger Pau Monné
2021-04-01 14:20     ` Jan Beulich
2021-04-06  9:52     ` Jan Beulich
2021-04-01 14:31   ` Andrew Cooper
2021-04-01 14:37     ` Jan Beulich
2021-04-06 17:34       ` Andrew Cooper
2021-04-07  7:54         ` 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=20210104155358.snzakj4kcs47tt22@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --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 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).