From: Matthew Wilcox <matthew@wil.cx>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: David Huggins-Daines <dhd@linuxcare.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 2.4.0-test6 lack of speed
Date: Tue, 29 Aug 2000 17:23:08 -0400 [thread overview]
Message-ID: <20000829172308.A1032@vodka.thepuffingroup.com> (raw)
In-Reply-To: <20000823172320.E4060@linuxcare.com>; from Richard Hirst on Wed, Aug 23, 2000 at 05:23:20PM +0100
On Wed, Aug 23, 2000 at 05:23:20PM +0100, Richard Hirst wrote:
> It looks to me like all calls to flush_cache_range() are passed a user
> virtual address, except for those calls from arch/parisc/kernel/pci-dma.c
> where we pass kernel virtual addresses.
agreed.
> So perhaps flush_cache_range() should generate FIC/FICE/FDC/FDCE
> instructions with a space register of %sr3, and pci-dma.c should
> use some other method of flushing memory.
>
> I was looking at the difference between FDC and FDCE; it seems FDC
> does address translation and FDCE does not, so should we use FDC
> really? flush_cache_range() currently uses FDCE/FICE.
we should stop using FICE/FDCE/PDTLBE/PITLBE except in the `flush
entire cache' routines. the definitions should be moved from cache.h
to cache.c. No-one else should be given the opportunaity to use them.
They are too undefined.
> Helge Deller wrote some code in drivers/net/lasi_82596.c that plays
> with %sr1 and uses FDC, FIC, PDC, SYNC, and SYNCDMA.
>
> Can someone tell me why include/asm/cache.h has no space register
> specified on fdce():
>
> > #define fdce(addr) asm volatile("fdce 0(%0)" : : "r" (addr))
> > #define fice(addr) asm volatile("fice 0(%%sr1,%0)" : : "r" (addr))
> >
> > #define pdtlbe(addr) asm volatile("pdtlbe 0(%%sr1,%0)" : : "r" (addr))
> > #define pitlbe(addr) asm volatile("pitlbe 0(%%sr1,%0)" : : "r" (addr))
My attempt at fixing this in a sane manner led me to create:
#define user_fdc(addr) asm volatile("fdc 0(%%sr3,%0)" : : "r" (addr))
(...)
and
#define kernel_fdc(addr) asm volatile("fdc 0(%%sr0,%0)" : : "r" (addr))
(...)
however, the resulting kernel wouldn't boot. So let's take this a
step at a time and see how far we can go towards eliminating the *E
variants. I've written a little rant on this suject which you can find
in linux-2.3/Documentation/parisc/mm. feel free to ignore it if you want.
> ps. as you can see, I am learning as I go here, so all hints and
> clues are gratefully accepted!
Likewise! BTW, I hear davem wrote a doc about this which is in
-test8-pre1 which may help somewhat.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2000-08-29 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 14:38 [parisc-linux] 2.4.0-test6 lack of speed Richard Hirst
2000-08-22 14:52 ` Richard Hirst
2000-08-22 15:50 ` Richard Hirst
2000-08-22 16:05 ` David Huggins-Daines
2000-08-23 16:23 ` Richard Hirst
2000-08-23 16:38 ` Paul Bame
2000-08-24 13:46 ` Richard Hirst
2000-08-29 21:23 ` Matthew Wilcox [this message]
2000-08-30 0:17 ` Matthew Wilcox
2000-08-30 8:15 ` Richard Hirst
2000-08-30 12:41 ` Richard Hirst
2000-08-30 10:15 ` Richard Hirst
2000-08-30 13:18 ` Matthew Wilcox
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=20000829172308.A1032@vodka.thepuffingroup.com \
--to=matthew@wil.cx \
--cc=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=rhirst@linuxcare.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