From: Pavel Machek <pavel@ucw.cz>
To: Richard Yao <ryao@gentoo.org>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Is there anyway to do direct mapped cache on Intel hardware?
Date: Wed, 1 Jul 2015 11:35:55 +0200 [thread overview]
Message-ID: <20150701093554.GA24985@amd> (raw)
In-Reply-To: <555A2A62.80309@gentoo.org>
On Mon 2015-05-18 14:07:30, Richard Yao wrote:
> Is there anyway to do direct mapped cache on Intel hardware?
>
> Direct mapped cache should allow me to implement software ECC via the
> low memory / high memory split. It would be slow, but I would prefer to
> have a slow laptop than one that is vulnerable to bit flips.
One of the bit flip papers actually presented the way to detect RAM
attacks using performance coutners....
But yes, software ECC would be cooler hack ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2015-07-01 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 18:07 Is there anyway to do direct mapped cache on Intel hardware? Richard Yao
2015-05-18 18:33 ` Richard Yao
2015-07-01 9:35 ` Pavel Machek [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=20150701093554.GA24985@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ryao@gentoo.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