From: Ingo Molnar <mingo@elte.hu>
To: Alexander van Heukelum <heukelum@mailshack.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Simple changes to make traps_32.c and traps_64.c more similar
Date: Tue, 1 Jul 2008 21:50:04 +0200 [thread overview]
Message-ID: <20080701195004.GA27557@elte.hu> (raw)
In-Reply-To: <20080701193643.GA29695@mailshack.com>
* Alexander van Heukelum <heukelum@mailshack.com> wrote:
> Tiny first step at unification of traps_32.c and traps_64.c. All
> changes are meant to be trivial.
> - mostly whitespace changes
> - chose one of obviously equivalent pieces of code:
> - reordering of declarations
> - simple renaming of local variables
> - if (cond) { ... } -> if (!cond) goto end_of_block ...
> - local caching of current, cpu, etc...
>
> This makes the diff between traps_32.c and traps_64.c smaller:
>
> from:
> 1474 +++++++++++++++++++++++++++++--------------------------------
> 1 file changed, 722 insertions(+), 752 deletions(-)
>
> to:
> 1052 +++++++++++++++++++++++++++++--------------------------------
> 1 file changed, 512 insertions(+), 540 deletions(-)
nice. In terms of functionality, it is supposed to be a pure
no-changes-intended commit, correct?
In that case it makes sense to split it in two: in the first (larger)
bit put the things that are provably invariant on the .o and can be
verified that way.
In the second one, put the things that change the .o output slightly
(variable reordering can do that) - this we have to check more closely.
(One can normally do such a splitup by editing the raw diff and
splitting it in half that way - by sorting each chunk into the
appropriate target patch - and then making sure the end result is still
the same.)
Ingo
next prev parent reply other threads:[~2008-07-01 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 19:36 Alexander van Heukelum
2008-07-01 19:50 ` Ingo Molnar [this message]
2008-07-01 23:42 ` Alexander van Heukelum
2008-07-01 23:29 ` [PATCH] x86: initial changes to unify traps_32.c and traps_64.c Alexander van Heukelum
2008-07-01 23:30 ` [PATCH 2/7] x86: traps_xx: shuffle headers and globals Alexander van Heukelum
2008-07-01 23:31 ` [PATCH 3/7] x86: traps_xx: modify __die Alexander van Heukelum
2008-07-01 23:31 ` [PATCH 4/7] x86: traps_xx: modify do_trap Alexander van Heukelum
2008-07-01 23:32 ` [PATCH 5/7] x86: traps_xx: restructure do_general_protection() Alexander van Heukelum
2008-07-01 23:32 ` [PATCH] x86: traps_xx: modify default_do_nmi Alexander van Heukelum
2008-07-02 16:12 ` Cyrill Gorcunov
2008-07-02 16:39 ` [PATCHv2 6/7] " Alexander van Heukelum
2008-07-02 17:16 ` Cyrill Gorcunov
2008-07-09 6:19 ` Ingo Molnar
2008-07-01 23:33 ` [PATCH 7/7] x86: traps_xx: various small changes Alexander van Heukelum
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=20080701195004.GA27557@elte.hu \
--to=mingo@elte.hu \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome