public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-arch@vger.kernel.org
Subject: Re: regression: 2f569af (CONFIG_HIGHPTE vs. sub-page page tables.)
Date: Wed, 27 Feb 2008 15:21:34 +0100	[thread overview]
Message-ID: <1204122094.25607.24.camel@localhost> (raw)
In-Reply-To: <20080226194903.GB31527@flint.arm.linux.org.uk>

On Tue, 2008-02-26 at 19:49 +0000, Russell King wrote:
> > > For a complete fix we might want to change the type of pte?
> > 
> > You mean instead of a "struct page *" use a pgtable_t ? Yes, that would
> > be cleaner even if it is the same type.
> 
> Would someone mind investigating how the code ended up in this mess in
> the first place, so we can avoid this kind of thing in the future?

One thing I have learned is that if I ever have to do a change over all
architectures again I will split the patch into the common part and the
arch parts and send it to the respective maintainers directly. Adding
linux-arch seems NOT to be enough to get the attention of the arch
maintainers (having the patch in -mm for 3 month is not doing the trick
either).

> It looks like the pte_lock_deinit() appeared in
> 4c21e2f2441dc5fbb957b030333f5a3f2d02dea7.
> 
> The dec_zone_page_state() used to be dec_page_state(nr_page_table_pages);
> which then became a dec_zone_page_state() in
> df849a1529c106f7460e51479ca78fe07b07dc8c.
> 
> Both changes of those changes on their own look correct.
> 
> Ah, is it that someone skipped over ARM when they changed the page table
> freeing code?  Yes - 2f569afd9ced9ebec9a6eb3dbf6f83429be0a7b4 has:

Yes, sorry. I need one of these brown paper bags..

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.



      parent reply	other threads:[~2008-02-27 14:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 13:26 regression: 2f569af (CONFIG_HIGHPTE vs. sub-page page tables.) Uwe Kleine-König
2008-02-25 13:38 ` Russell King
2008-02-25 15:32   ` Uwe Kleine-König
2008-02-25 15:45     ` let __dec_zone_page_state use __dec_zone_state Uwe Kleine-König
2008-02-27 19:10       ` Christoph Lameter
2008-02-29  7:45         ` Uwe Kleine-König
2008-02-29 19:32           ` Christoph Lameter
2008-02-25 16:56 ` regression: 2f569af (CONFIG_HIGHPTE vs. sub-page page tables.) Martin Schwidefsky
2008-02-26 14:38   ` Uwe Kleine-König
2008-02-26 17:57     ` Martin Schwidefsky
2008-02-26 19:49       ` Russell King
2008-02-27 12:44         ` Uwe Kleine-König
2008-02-27 14:21         ` Martin Schwidefsky [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=1204122094.25607.24.camel@localhost \
    --to=schwidefsky@de.ibm.com \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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