linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: get_pteptr()
Date: Thu, 13 Jun 2002 01:02:37 -0400	[thread overview]
Message-ID: <3D08276D.3080502@embeddededge.com> (raw)
In-Reply-To: 20020613040345.GD4228@zax


David Gibson wrote:

> get_pteptr() is used in exactly three places:
> 	- in arch/ppc/8xx_io/commproc.c in the #else side of a #if 1,
> i.e. not really used at all.

That was one of my earliest cache management hacks, that predated iopa()
and consistent_alloc().  You can get rid of it.

> 	- in do_page_fault() [arch/ppc/mm/fault.c] for the handling of
> page execute faults on 40x.  It's use here is arguably incorrect if
> large page pmds are introduced, although we won't ever get execute
> faults on large pages, so it doesn't really matter.

Hmmmm.....I was always hoping we could use "standard" VM functions to
find and update PTEs, but I guess that isn't happening.  I would suggest
just placing a comment around this about the large pages and leave it.


> But given that iopa() is pretty much the only user of this function
> (do_page_fault() should be done slightly differently, I think), there
> doesn't seem a lot of point.  Why not just eliminate get_pteptr() and
> walk the page tables explicitly in iopa().

I sometimes use get_pteptr() for debug.  Make sure xmon doesn't use it
for printing page table information.

> [*] Well, apart from removing iopa() entirely, but that's another
> flamewar^Wdiscussion.

Just remove it for 4xx, or put an #ifdef in iopa() to do the arithmetic
conversion.  It's only used on 4xx and 8xx, and I would like to ensure
the 8xx still works correctly before we nuke everything.  I would just
be a little careful to ensure you have run enough PCI cards to verify
everything is OK.

Thanks.


	-- Dan


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

  reply	other threads:[~2002-06-13  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  4:03 get_pteptr() David Gibson
2002-06-13  5:02 ` Dan Malek [this message]
2002-06-13  5:27   ` get_pteptr() David Gibson
2002-06-13  7:29     ` get_pteptr() Dan Malek
2002-06-13  7:51       ` get_pteptr() David Gibson

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=3D08276D.3080502@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).