From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] cache question
Date: Fri, 28 Jan 2005 13:24:07 -1000 [thread overview]
Message-ID: <Pine.BSI.4.61.0501281322130.23562@malasada.lava.net> (raw)
In-Reply-To: <Pine.BSI.4.61.0501281208210.23562@malasada.lava.net>
> I'm seeing a bug where I get some random crashes when I boot
> my kernel with the dcache on which go away if I turn off the
> dcache. I'm guessing this means that something in the cache
> needs to get flushed that isnt. What it is or when I should
> flush is less clear to me. The portable code lets the machine
> specific code know when it should perform an instruction cache
> flush, but never indicates any data flushes.
The closest thing I've found to a solution so far is to flush
a page from the dcache in putmmu() every time a page is added.
This seems a bit excessive (compare with icache which is only
flushed when PG_TXTFLUSH is indicated).
Tim N.
prev parent reply other threads:[~2005-01-28 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 22:19 Tim Newsham
2005-01-28 23:24 ` Tim Newsham [this message]
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.BSI.4.61.0501281322130.23562@malasada.lava.net \
--to=newsham@lava.net \
--cc=9fans@cse.psu.edu \
/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).