Skip to contentSkip to conversation

get_pteptr()

DISCUSSION David Gibson 2 participants 5 messages Jun 13, 2002

lore
Share & tools
lore
#0 lore raw

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.
- 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.
- in iopa() [arch/ppc/mm/pgtable.c]. The sanest way [*] I can
see of extending this to support large page pmds, without horrible ifdefs can't be done without either extending get_pteptr(), or removing it and walking the page tables manually.

I could extend get_pteptr() to handle large page pmds. Something like:
- if the address has no valid translation, return 0 and leave
*ptep unchanged (as now).
- if the address is translated by a normal PTE return
PAGE_MASK and set ptep to point to the PTE
- if the address is translated by a large page PMD return a
mask for the size of the large page and set ptep to point to the PMD.

That makes iopa() easy and works for the other callers.

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().

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

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

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

#1 lore raw
Quoted 3 lines · David Gibson

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.

Quoted 4 lines

- 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.

Quoted 4 lines

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.

Quoted 2 lines

[*] 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/

#2 lore raw
Quoted 9 lines · Dan Malek
Quoted 3 lines · David Gibson

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.

Ok, I will.

Quoted 8 lines
Quoted 4 lines

- 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.

I think this is easier said than done, because depending on what's being done you often need to do different things at each level of walking the page tables.

In some ways it would make more sense to handle these exec faults in handle_mm_fault() (which already implements a page table walk), along with normal read and write faults. But that would mean muddying generic code with exec fault stuff which is only relevant for a few processors.

Quoted 7 lines
Quoted 4 lines

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.

It doesn't. I know there are only those 3 (really 2) users, because I grepped the whole source for it. Debugging is a legitimate use, I guess, though, so I might leave it in for now, even though little will use it.

Quoted 8 lines
Quoted 2 lines

[*] 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.

Do you mean get_pteptr() or iopa()? If iopa() I agree with paulus, removing it from 2.4 would be unwise - it could break (already broken but kinda working) drivers. I simply don't have the hardware to test really thoroughly. I do think it should go from 2.5. though.

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

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

#3 lore raw
Quoted 1 line · David Gibson

Do you mean get_pteptr() or iopa()?

In iopa(). Just put an #ifdef in there for 4xx that does addr - KERNELBASE, just like virt_to_bus/phys does for other processors (except 8xx).

	-- Dan

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

#4 lore raw
Quoted 6 lines · Dan Malek
Quoted 1 line · David Gibson

Do you mean get_pteptr() or iopa()?

In iopa(). Just put an #ifdef in there for 4xx that does addr - KERNELBASE, just like virt_to_bus/phys does for other processors (except 8xx).

Well, if we were going to do that then we might as well just pull 4xx from the list of CONFIGs for which virt_to_bus() calls iopa() in the first place. The only other places that iopa() is called are 8xx specific anyway.

--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

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