All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Josh Boyer <jwboyer@charter.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Large TLBs on 40x
Date: Wed, 4 Aug 2004 09:39:37 -0700	[thread overview]
Message-ID: <20040804093937.B12758@home.com> (raw)
In-Reply-To: <7FA32080-E634-11D8-852B-003065F9B7DC@embeddededge.com>; from dan@embeddededge.com on Wed, Aug 04, 2004 at 12:36:56PM -0400


On Wed, Aug 04, 2004 at 12:36:56PM -0400, Dan Malek wrote:
>
> On Aug 4, 2004, at 7:49 AM, Josh Boyer wrote:
>
> > Maybe pinning a read-only TLB entry for most of the text pages for
> > however large you can get would work...  or maybe not.
>
> The problem is BATs and pinned TLBs require alignment restrictions
> that don't allow this.
>
> > .....But when someone is writing new drivers, randomly poking
> > holes in the kernel text pages and then executing instructions from
> > there leads to some strange panics.  Although, the new driver should be
> > suspect in that case anyway :).
>
> Then, on MPC8xx don't select pinned TLBs to cover the kernel
> space, and on traditional PPC MMUs select  the 'nobat' option
> on the command line.  This will write protect the kernel text pages.
> However, if you select something like CONFIG_KGDB, this will
> allow writing of the text pages to set breakpoints.  You will need
> to use a debugger like the BDI2000 and use hardware breakpoints
> to do your debugging.  When you are done, you can enable the
> performance TLB options again.  I thought the 4xx allowed
> something like this as well.  If not, it could and probably should.

We eagerly await your patch. ;)

-Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-04 16:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 23:05 Large TLBs on 40x Josh Boyer
2004-08-04  0:16 ` Matt Porter
2004-08-04 11:49   ` Josh Boyer
2004-08-04 16:36     ` Dan Malek
2004-08-04 16:39       ` Matt Porter [this message]
2004-08-04 17:03         ` Dan Malek
2004-08-10  2:21           ` Josh Boyer
2004-08-10  6:04             ` Dan Malek
2004-08-10 14:35               ` Matt Porter
2004-08-10 14:57                 ` Dan Malek
2004-08-11 13:50                 ` Josh Boyer
2004-08-11 15:30                   ` Dan Malek
2004-08-11 17:58                     ` Josh Boyer
2004-08-11 18:21                       ` Dan Malek
2004-08-11 15:45                   ` Matt Porter
2004-08-11 17:42                     ` Josh Boyer
2004-08-11 18:16                       ` Dan Malek
2004-08-11 18:38                         ` Matt Porter

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=20040804093937.B12758@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=jwboyer@charter.net \
    --cc=linuxppc-embedded@lists.linuxppc.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.