linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Steve Rossi <srossi@ccrl.mot.com>
Cc: Dan Malek <dan@netx4.com>,
	Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: allocating non-cacheable regions
Date: Wed, 31 May 2000 18:12:53 -0400	[thread overview]
Message-ID: <39358E65.145F7EA3@embeddededge.com> (raw)
In-Reply-To: 39357BC5.A0B3E713@ccrl.mot.com


Steve Rossi wrote:

> ....does setting the _PAGE_NO_CACHE flag
> for a page table entry also invalidate any cached data for that page?

No.  It only ensures uncached behavior when the TLB is loaded.

> I am observing a write-though behavior when I write to addresses in
> the _PAGE_NO_CACHE page but when I read from addresses marked
> as _PAGE_NO_CACHE it appears to be retrieving data from the cache
> not from memory. Is this expected behavior?

That's a rhetorical, question, right :-)?  If not....of course that
isn't correct.

> .... How can I make it so that
> reads as well as writes to a particular page bypass the cache?

You need to invalidate the data cache for this address and the TLB
entry for this address when you set the flag.  Those drivers in your
example get away with it because the caches/TLB have been invalidated
and not yet touched at this point.  You also need to ensure you are not
multiple mapping the same physical address....


	-- Dan

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

  reply	other threads:[~2000-05-31 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-03 15:47 allocating non-cacheable regions Steve Rossi
2000-05-03 19:52 ` Dan Malek
2000-05-04  6:45   ` MPC860 enet driver dony
2000-05-31 20:53   ` allocating non-cacheable regions Steve Rossi
2000-05-31 22:12     ` Dan Malek [this message]
2000-05-31 22:39       ` Tom Roberts
2000-06-01 13:01       ` Steve Rossi
2000-06-01 20:10         ` Steve Rossi
2000-06-02 14:24           ` Steve Rossi

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=39358E65.145F7EA3@embeddededge.com \
    --to=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=srossi@ccrl.mot.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;
as well as URLs for NNTP newsgroup(s).