From: Ralf Baechle <ralf@linux-mips.org>
To: Ashish anand <ashish.anand@inspiretech.com>
Cc: linux-mips@linux-mips.org
Subject: Re: low ram as source of good parity data..?
Date: Thu, 5 Jun 2003 13:27:22 +0200 [thread overview]
Message-ID: <20030605112722.GA9001@linux-mips.org> (raw)
In-Reply-To: <200306051027.h55ARnI9031919@smtp.inspirtek.com>
On Thu, Jun 05, 2003 at 03:16:41PM +0530, Ashish anand wrote:
> I have seen it a common practice to assume low RAM as source
> of good parity data and use it to fill the caches with good parity
> data in firmware during elementary hardware initialisation process.
>
> why it is always safe to assume that low RAM contains good parity data .?
> Is it always true..?
> this question came in picture after I got cacheparity error sometimes.
For the general case it's not safe. Some systems need memory to be
initialized by writing to it first because before the parity or ECC
bits may have an undefined state.
The safe way to initalize the caches is using the Index_Store_Tag_D etc.
cacheops but of course that requires knowledge about the particular
processor's exactly cache architecture.
Ralf
prev parent reply other threads:[~2003-06-05 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 9:46 low ram as source of good parity data..? Ashish anand
2003-06-05 11:27 ` Ralf Baechle [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=20030605112722.GA9001@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ashish.anand@inspiretech.com \
--cc=linux-mips@linux-mips.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