From: "Richard D" <richard@embunus.com>
To: "'Pavel Machek'" <pavel@ucw.cz>
Cc: "'Matthew Bloch'" <matthew@bytemark.co.uk>, <linux-kernel@vger.kernel.org>
References: <fk8umh$n7o$1@ger.gmane.org> <20071221125812.GA4052@ucw.cz> <000001c84472$74b245e0$5e16d1a0$@com> <20071222134612.GA4098@ucw.cz>
In-Reply-To: <20071222134612.GA4098@ucw.cz>
Subject: RE: Testing RAM from userspace / question about memmap= arguments
Date: Sat, 22 Dec 2007 21:00:11 +0530
Message-ID: <000a01c844af$8e76b910$ab642b30$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AchEoQqzCgXTQ7MPSC69bkKKNa/+wQADiDqw
Content-Language: en-us
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1111
Lines: 29

I was thinking that by the time userspace is ready, the memory that can be
tested will be less. 

-----Original Message-----
From: Pavel Machek [mailto:pavel@ucw.cz] 
Sent: Saturday, December 22, 2007 7:16 PM
To: Richard D
Cc: 'Matthew Bloch'; linux-kernel@vger.kernel.org
Subject: Re: Testing RAM from userspace / question about memmap= arguments

On Sat 2007-12-22 13:42:47, Richard D wrote:
> Cant you, modify bootmem allocator to test with memtest patterns and then
> use kexec (as Pavel suggested) to test the one where kernel was sitting
> earlier?


I do not think you need to modify anything in kernel. Just use
/dev/mem to test areas that kernel doesn't see, then kexec into place
you already tested, and test the rest.
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/