From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: memtest updates
Date: Tue, 27 Oct 2015 18:35:27 +0100 [thread overview]
Message-ID: <20151027173526.GA9341@omega> (raw)
In-Reply-To: <20151027172742.GA8942@omega>
On Tue, Oct 27, 2015 at 06:27:42PM +0100, Alexander Aring wrote:
> On Tue, Oct 27, 2015 at 05:54:59PM +0100, Alexander Aring wrote:
> > On Tue, Oct 27, 2015 at 09:29:53AM +0100, Sascha Hauer wrote:
> > > This series has some updates for the memory test. The output and the
> > > code are made more compact and some additional options are added. Also
> > > the remap_range function is reworked.
> > >
> >
> ...
> >
> > What means 0xdeadbeef here?
>
> okay, I it's guess the pattern argument which doesn't exist anymore.
>
> I run memtest now with:
>
> memtest -t -u
>
> on the RPi and it seems the first progressbar range of "0/3" - "1/3" runs
> faster than the last range of "1/3" - "3/3".
>
> This sounds like that remap_range does not full manipulate the range
> of page tables (the range at the start address). Okay we can't full use
> the range, because we need to be PAGE_ALIGN, but the whole first range of
> "0/3" - "1/3" sounds not correct for me (it's bigger than PAGE_ALIGN).
>
> Maybe everything is correct and the first address room is always a
> little bit faster than the others, but I don't think that.
>
> I haven't tried to debug this issue. Can somebody confirm that on an
> other arm board?
>
okay, false alarm. It's confusing me, we do not always the same
operation in each progressbar step.
We doing in the first part filling some pattern, in second/third part we
doing filling pattern and compare. This is why it takes longer. It just
looks like some area is still cached and the other uncached.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-10-27 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 8:29 Sascha Hauer
2015-10-27 8:29 ` [PATCH 1/9] memtest: move request/release regions to common/ Sascha Hauer
2015-10-27 8:29 ` [PATCH 2/9] rework remap_range Sascha Hauer
2015-10-27 8:29 ` [PATCH 3/9] memtest: split tests in separate functions Sascha Hauer
2015-10-27 8:29 ` [PATCH 4/9] memtest: Make output more compact Sascha Hauer
2015-10-27 8:29 ` [PATCH 5/9] memtest: Make comments single line when appropriate Sascha Hauer
2015-10-27 8:29 ` [PATCH 6/9] memtest: move ctrlc check / progress showing into separate function Sascha Hauer
2015-10-27 8:30 ` [PATCH 7/9] memtest: move error handling to end of function Sascha Hauer
2015-10-27 8:30 ` [PATCH 8/9] memtest: By default only test biggest region Sascha Hauer
2015-10-27 8:30 ` [PATCH 9/9] memtest: Make cached/uncached test configurable Sascha Hauer
2015-10-27 16:55 ` memtest updates Alexander Aring
2015-10-27 17:27 ` Alexander Aring
2015-10-27 17:35 ` Alexander Aring [this message]
2015-10-28 6:17 ` Sascha Hauer
2015-10-28 9:11 ` Alexander Aring
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=20151027173526.GA9341@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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