public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Glauber de Oliveira Costa <glommer@gmail.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH 0/5] x86: another attempt at x86 pagetable unification
Date: Thu, 20 Dec 2007 22:39:06 +0100	[thread overview]
Message-ID: <20071220213906.GB11897@elte.hu> (raw)
In-Reply-To: <476AD9EA.7010108@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> > found a couple of bugs.
> >
> > firstly, 64-bit wasnt so lucky, you broke 
> > iounmap()/change_page_attr()
> > :-)
> 
> Crap.  Worked for me.  I'll look into it.

well, there's an easy solution for unification patches: the resulting 
object files must have _exactly the same_ content as without the 
unification patches. (Modulo strings as WARN_ON()s referring to 
include-file names.)

If they differ then the unification did something wrong. With your 
patchset and the config i sent, the difference is visible in the image 
size already:

   text     data   bss     dec              hex    filename
   7763766  967330 5812328 14543424         ddea40 vmlinux.after
   7763811  967330 5812328 14543469         ddea6d vmlinux.before

also, reducing the size and scope of changes helps as well - because 
that way it can be bisected down to specific changes. Mistakes 
inevitably happen, especially if you do not enforce a rigid 
byte-for-byte correctness along the way. You did 5 rather large patches, 
and it's not testable because your unification steps were too coarse.

In other words: you were asking for trouble and you got it :-)

	Ingo

  reply	other threads:[~2007-12-20 21:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 22:35 [PATCH 0/5] x86: another attempt at x86 pagetable unification Jeremy Fitzhardinge
2007-12-19 22:35 ` [PATCH 1/5] x86: clean up asm-x86/page*.h Jeremy Fitzhardinge
2007-12-19 22:35 ` [PATCH 2/5] x86: unify pgtable*.h Jeremy Fitzhardinge
2007-12-20 12:19   ` Eduardo Habkost
2007-12-20 21:02     ` Jeremy Fitzhardinge
2007-12-19 22:35 ` [PATCH 3/5] x86: fix up formatting in pgtable*.h Jeremy Fitzhardinge
2007-12-19 22:35 ` [PATCH 4/5] x86: use a uniform structure for pte_t Jeremy Fitzhardinge
2007-12-19 22:35 ` [PATCH 5/5] x86: clean up pagetable-related printk format warnings Jeremy Fitzhardinge
2007-12-20  9:13 ` [PATCH 0/5] x86: another attempt at x86 pagetable unification Ingo Molnar
2007-12-20  9:49 ` Ingo Molnar
2007-12-20 11:20   ` Ingo Molnar
2007-12-20 21:08     ` Jeremy Fitzhardinge
2007-12-20 21:39       ` Ingo Molnar [this message]
2007-12-20 22:08         ` Jeremy Fitzhardinge
2007-12-20 22:24           ` Ingo Molnar
2007-12-21  0:52             ` Jeremy Fitzhardinge
2007-12-21  0:58               ` Ingo Molnar
2007-12-21  1:03                 ` Glauber de Oliveira Costa
2007-12-20 21:03   ` Jeremy Fitzhardinge

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=20071220213906.GB11897@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=glommer@gmail.com \
    --cc=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --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