From: Arjan van de Ven <arjan@infradead.org>
To: Matthew Bloch <matthew@bytemark.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Testing RAM from userspace / question about memmap= arguments
Date: Sat, 22 Dec 2007 12:09:59 -0800 [thread overview]
Message-ID: <20071222120959.475ebced@laptopd505.fenrus.org> (raw)
In-Reply-To: <fk8umh$n7o$1@ger.gmane.org>
On Tue, 18 Dec 2007 17:06:24 +0000
Matthew Bloch <matthew@bytemark.co.uk> wrote:
> Hi - I'm trying to come up with a way of thoroughly testing every byte
> of RAM from within Linux on amd64 (so that it can be automated better
> than using memtest86+), and came up with an idea which I'm not sure is
> supported or practical.
>
> The obvious problem with testing memory from user space is that you
> can't mlock all of it, so the best you can do is about three quarters,
> and hope that the rest of the memory is okay.
well... to be honest the more obvious problem will be that you won't be testing the RAM, you'll be testing the CPU's cache.. over and over again.
memtest86+ does various magic to basically bypass the caches (by disabling them ;-)...
Doing that in a live kernel situation, and from userspace to boot...... that's... and issue.
next prev parent reply other threads:[~2007-12-22 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 17:06 Matthew Bloch
2007-12-20 12:33 ` Jon Masters
2007-12-20 14:17 ` Matthew Bloch
2007-12-21 12:58 ` Pavel Machek
2007-12-22 8:12 ` Richard D
2007-12-22 13:46 ` Pavel Machek
2007-12-22 15:30 ` Richard D
2007-12-22 18:43 ` Pavel Machek
2007-12-22 16:06 ` David Newall
2007-12-22 18:47 ` Pavel Machek
2007-12-22 20:36 ` David Newall
2007-12-22 20:54 ` Pavel Machek
2007-12-23 7:35 ` David Newall
2007-12-23 11:17 ` Pavel Machek
2007-12-22 20:48 ` Matthew Bloch
2007-12-22 20:09 ` Arjan van de Ven [this message]
2007-12-25 23:09 ` Pavel Machek
2007-12-26 10:17 ` Arjan van de Ven
2007-12-26 20:37 ` Maxim Levitsky
2007-12-20 17:01 Siva Prasad
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=20071222120959.475ebced@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@bytemark.co.uk \
/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
Powered by JetHome