linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: holler@ahsoftware.de (Alexander Holler)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm: memtest
Date: Fri, 09 Nov 2012 06:00:36 +0100	[thread overview]
Message-ID: <509C8DF4.4070300@ahsoftware.de> (raw)
In-Reply-To: <CAE9FiQWeie62NYt2vyq2q+Um8NeA5xWQGy-nULmFidt4XxW=BA@mail.gmail.com>

Am 08.11.2012 23:39, schrieb Yinghai Lu:
> On Thu, Nov 8, 2012 at 12:48 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>> Hello,
>>
>> I've recently discovered the lack of the command line parameter memtest for
>> ARM. So I've made a patch.
>>
>> But I have some questions:
>>
>> 1. arch/x86/mm/memtest.c looks platform independ.
>> The only thing why I don't use it for arm, is because it uses 64bit
>> pointers. Maybe it could be moved to mm/memtest.c. If so, the memtest32.c
>> I'm using (basically a copy of memtest.c) could be moved there too.
>>
>> 2. Because the below memtest32.c is basically a copy of
>> arch/x86/mm/memtest.c, I'm not sure if the mapping from physical to virtual
>> locations there does fit (always) for ARM too. I know almost as much about
>> the in-kernel memory organization on x86 as on ARM, which is not really that
>> much (some theory about TLBs, some source code explorations, ..., but I'm
>> working on it). ;)
>
> We are using arch/x86/mm/memtest.c for x86 32bit and 64bit.
>
> So it should be ok to use it with arm 32bit and 64bit directly.

It does. But in order to enable it on every boot, I wanted it to be as 
fast as possible.

Regards,

Alexander

  reply	other threads:[~2012-11-09  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 20:48 [RFC] arm: memtest Alexander Holler
2012-11-08 22:18 ` Matthieu Castet
2012-11-08 22:39 ` Yinghai Lu
2012-11-09  5:00   ` Alexander Holler [this message]
2012-11-09 12:10 ` Alexander Holler

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=509C8DF4.4070300@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).