All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: User mode address error problems on 7763
Date: Tue, 15 Sep 2009 12:36:16 +0000	[thread overview]
Message-ID: <20090915123615.GA23432@linux-sh.org> (raw)
In-Reply-To: <6e6aa1a80909111106l6dbcfccag4e9e7a3abb922688@mail.gmail.com>

On Tue, Sep 15, 2009 at 07:20:27AM -0500, Dale Larson wrote:
> >> The 7763 only supports 1K, 4K, 64K and 1M pages. Would a 64K page
> >> yield any useful info?
> > You can get 8kB pages by enabling extended mode TLB. But yes, 64k pages
> > are fine too, if using the compat mode TLB.
> 
> I can? I don't see it in the 7763 hardware manual. I only see this in
> the MMU section:
> 
> "This LSI has four instruction TLB (ITLB) entries and 64 unified TLB
> (UTLB) entries. UTLB
> copies are stored in the ITLB by hardware. A paging system is used for
> address translation, with
> four page sizes (1, 4, and 64 Kbytes, and 1 Mbyte) supported. It is
> possible to set the virtual
> address space access right and implement memory protection
> independently for privileged mode
> and user mode."
> 
I assumed SH7763 was an SH-X2 based core, but it turns out it is a
first-generation SH-4A, in which case it does not implement the extended
mode TLB. So the next available page size above 4k is 64k. I wasn't aware
there was anyone still running first generation SH-4A, I'll have to dust
some of mine off to see if I can reproduce your issues.

> If 64K would work with "compat mode TLB" how do I turn it on?

From the top menu, System Type -> Memory management options -> Kernel
page size. That will bring up a menu where you can cycle through the
available page sizes. I don't recommend 1MB for a system page size, as it
tends to interact badly with some of the slab allocators. 64k will give
you an idea of whether there are indeed any aliasing bugs lurking about.

  parent reply	other threads:[~2009-09-15 12:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 18:06 User mode address error problems on 7763 Dale Larson
2009-09-11 18:35 ` Matt Fleming
2009-09-11 19:16 ` Dale Larson
2009-09-14 13:02 ` Dale Larson
2009-09-14 13:10 ` Paul Mundt
2009-09-14 13:14 ` Matt Fleming
2009-09-14 13:54 ` Dale Larson
2009-09-15  8:39 ` Matt Fleming
2009-09-15 11:54 ` Dale Larson
2009-09-15 11:57 ` Paul Mundt
2009-09-15 12:20 ` Dale Larson
2009-09-15 12:36 ` Paul Mundt [this message]
2009-09-15 12:55 ` Dale Larson
2009-09-15 13:07 ` Paul Mundt
2009-09-15 13:16 ` Dale Larson
2009-09-15 13:23 ` Dale Larson
2009-09-15 13:29 ` Dale Larson
2009-09-15 13:39 ` Paul Mundt
2009-09-15 13:49 ` Valentin R Sitsikov
2009-09-15 14:43 ` Dale Larson
2009-09-15 23:42 ` Paul Mundt
2009-09-16 12:45 ` Dale Larson
2009-09-16 19:22 ` Dale Larson

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=20090915123615.GA23432@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.