linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* memtest help
@ 2016-04-28 16:42 Bojan Prtvar
  2016-04-29  9:22 ` Vladimir Murzin
  0 siblings, 1 reply; 2+ messages in thread
From: Bojan Prtvar @ 2016-04-28 16:42 UTC (permalink / raw)
  To: linux-mm

Hello everyone,

I need to test all RAM cells on a linux ARM embedded system. My use case 
is very similar to the one described in [1] expect the fact I also have 
strong requirements on minimizing the boot time impact.
Instead of doing that from the bootloader, I decided to evaluate the 
linux memtest feature introduced with [2].

My questions are:

1)
Does the  early_memtest() as called in [3] really covers *all* RAM cells?

2)
As memtest happens very early in boot stage, what primitives I can use 
to measure duration of early_memtest()? Are there any known heuristics? 
I need to test ~2GB of RAM.
This is my major concern.

3)
It seems reasonable to expose the number of detected bad cells to user 
space. I was thinking about sysfs. Are the patches welcomed?

[1]
http://www.linuxforums.org/forum/newbie/173847-how-do-memory-ram-test-when-linux-running.html
[2]
http://lkml.iu.edu/hypermail/linux/kernel/1503.1/00566.html
[3]
http://lxr.free-electrons.com/source/arch/arm/mm/init.c#L291

Thanks,
Bojan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: memtest help
  2016-04-28 16:42 memtest help Bojan Prtvar
@ 2016-04-29  9:22 ` Vladimir Murzin
  0 siblings, 0 replies; 2+ messages in thread
From: Vladimir Murzin @ 2016-04-29  9:22 UTC (permalink / raw)
  To: Bojan Prtvar, linux-mm

On 28/04/16 17:42, Bojan Prtvar wrote:
> Hello everyone,
> 
> I need to test all RAM cells on a linux ARM embedded system. My use case
> is very similar to the one described in [1] expect the fact I also have
> strong requirements on minimizing the boot time impact.
> Instead of doing that from the bootloader, I decided to evaluate the
> linux memtest feature introduced with [2].
> 
> My questions are:
> 
> 1)
> Does the  early_memtest() as called in [3] really covers *all* RAM cells?

No.

> 
> 2)
> As memtest happens very early in boot stage, what primitives I can use
> to measure duration of early_memtest()? Are there any known heuristics?
> I need to test ~2GB of RAM.
> This is my major concern.

Stopwatch?

> 
> 3)
> It seems reasonable to expose the number of detected bad cells to user
> space. I was thinking about sysfs. Are the patches welcomed?
> 

$ dmesg | grep "bad mem"

Cheers
Vladimir

> [1]
> http://www.linuxforums.org/forum/newbie/173847-how-do-memory-ram-test-when-linux-running.html
> 
> [2]
> http://lkml.iu.edu/hypermail/linux/kernel/1503.1/00566.html
> [3]
> http://lxr.free-electrons.com/source/arch/arm/mm/init.c#L291
> 
> Thanks,
> Bojan
> 
> -- 
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> 
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-04-29  9:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-28 16:42 memtest help Bojan Prtvar
2016-04-29  9:22 ` Vladimir Murzin

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).