public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Hugh Dickins <hugh@veritas.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.5-aa1 arch updates
Date: Mon, 5 Apr 2004 01:09:13 +0200	[thread overview]
Message-ID: <20040404230913.GA2148@dualathlon.random> (raw)
In-Reply-To: <16496.36001.210779.472061@cargo.ozlabs.ibm.com>

On Mon, Apr 05, 2004 at 08:30:57AM +1000, Paul Mackerras wrote:
> Andrea Arcangeli writes:
> 
> > I'm unsure about the arch/ppc/mm/pgtable.c part, I mean, ppc is being
> > tested heavily, how can it be necessary if nobody ever got an oops yet? 
> > OTOH your patch certainly cannot hurt and it might be needed after all.
> > Maybe I should apply it after all, it'd be nice to get a comment on this
> > bit from ppc people who knows tlb.c better to be sure.
> 
> We definitely need page->mapping and page->index set on pte and pmd
> pages, both on ppc and ppc64.  Otherwise the flush_tlb_* functions
> won't work properly.  Hugh's patch looks good to me (at least as far
> as the ppc/ppc64 bits are concerned).

ok thanks, Hugh's arch's update adding ppc support are fully applied
right now in 2.6-aa and all other relevant trees. Thanks again Hugh!

I only still wonder how this could be unnoticed in practice in ppc(32)?
I mean page->mapping should be NULL if we don't set it and it should
cause an oops in flush_hash_one_pte, no? (if Hash != 0 of course)

  reply	other threads:[~2004-04-04 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 13:48 [PATCH] 2.6.5-aa1 arch updates Hugh Dickins
2004-04-04 15:49 ` Andrea Arcangeli
2004-04-04 22:30   ` Paul Mackerras
2004-04-04 23:09     ` Andrea Arcangeli [this message]
2004-04-04 21:51 ` Andrew Morton
2004-04-04 22:10   ` Andrew Morton

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=20040404230913.GA2148@dualathlon.random \
    --to=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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