From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rex Feany <RFeany@mrv.com>
Cc: Scott Wood <scottwood@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: I think I have 8xx working...
Date: Thu, 15 Oct 2009 12:12:50 +1100 [thread overview]
Message-ID: <1255569170.2347.62.camel@pasglop> (raw)
In-Reply-To: <20091015010855.GA32710@compile2.chatsunix.int.mrv.com>
On Wed, 2009-10-14 at 18:08 -0700, Rex Feany wrote:
> Thus spake Benjamin Herrenschmidt (benh@kernel.crashing.org):
>
> > On Wed, 2009-10-14 at 17:41 -0700, Rex Feany wrote:
> > > The biggest problem for me turned out to be the MMU context IDs being
> > > clamped to 32 when the 8xx only has 16. With this, things are a bit more
> > > stable :)
> >
> > This is with Joakim patches or without ?
>
> with just one: adding tlbil_va() to do_page_fault().
Ah cool, at least that keeps my sanity, I didn't get how it could work
at all without that bit :-)
Scott, Joakim: It will be interesting to figure out exactly what is the
condition where that is necessary. It definitely should make the one
in set_pte_filter() or ptep_set_access_flags_filter() unnecessary.
Joakim, you mentioned increased amount of TLB errors or misses when
doing that too often, that sounds a bit weird and worth investigating
Finally we could implement preload from update_mmu_cache() but that's a
different matter alltogether.
Cheers,
Ben.
next prev parent reply other threads:[~2009-10-15 1:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 0:41 I think I have 8xx working Rex Feany
2009-10-15 1:00 ` Benjamin Herrenschmidt
2009-10-15 1:06 ` Benjamin Herrenschmidt
2009-10-15 1:08 ` Rex Feany
2009-10-15 1:12 ` Benjamin Herrenschmidt [this message]
2009-10-15 5:42 ` Joakim Tjernlund
2009-10-15 6:21 ` Benjamin Herrenschmidt
2009-10-15 5:32 ` Joakim Tjernlund
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=1255569170.2347.62.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=RFeany@mrv.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).