From: Roman Zippel <zippel@linux-m68k.org>
To: Armin Kuster <akuster@mvista.com>
Cc: ppcdevel <linuxppc-dev@lists.linuxppc.org>,
ppclists <Majordomo@lists.linuxppc.org>
Subject: Re: New API for non cache coherent ppc cpu's
Date: Wed, 21 Nov 2001 12:15:39 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0111211152230.6681-100000@serv> (raw)
In-Reply-To: <3BFAB960.DAA72239@mvista.com>
Hi,
On Tue, 20 Nov 2001, Armin Kuster wrote:
> About a month ago a new API made its way into the ppc,
> consistent_sync_page.
Another one?
We have now 3 APIs for this:
- cache_(push|clear): that's the old m68k API (and also used by APUS)
- dma_cache_(inv|wback|wback_inv): used by mips(64), parisc, sh
- consistent_sync_page: ppc
> For CONFIG_NOT_COHERENT_CACHE processors,
> requires
> proper flushing of the page being used. Please review and provide feed
> back
Two comments:
- I'm not sure about the page argument, although I'd like to see it, the
problem is the drivers usually don't have a page pointer.
- I think it was never defined, what should be done if offset/size isn't
cache line aligned. That's especially a problem in the invalidate only
case. I'd prefer to make this illegal, as it's mostly not a problem for
drivers.
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-21 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 20:13 New API for non cache coherent ppc cpu's Armin Kuster
2001-11-21 11:15 ` Roman Zippel [this message]
2001-11-21 18:29 ` Armin Kuster
2001-11-21 20:20 ` Roman Zippel
2001-11-22 20:57 ` Paul Mackerras
2001-11-22 23:07 ` Dan Malek
2001-11-22 23:54 ` Roman Zippel
2001-11-23 1:32 ` Paul Mackerras
2001-11-23 16:08 ` Dan Malek
2001-11-22 23:50 ` Roman Zippel
2001-11-23 1:09 ` Paul Mackerras
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=Pine.LNX.4.33.0111211152230.6681-100000@serv \
--to=zippel@linux-m68k.org \
--cc=Majordomo@lists.linuxppc.org \
--cc=akuster@mvista.com \
--cc=linuxppc-dev@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 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).