linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Finn Thain <fthain@linux-m68k.org>, linux-m68k@lists.linux-m68k.org
Cc: Mike Rapoport <rppt@kernel.org>
Subject: Re: [RFC] m68k: Enable memtest kernel parameter
Date: Mon, 13 Sep 2021 15:40:12 +1200	[thread overview]
Message-ID: <b1b630b8-d6b6-661b-b5c1-2a2831b5b8c2@gmail.com> (raw)
In-Reply-To: <9fac90da-18d5-7b89-96a5-3cf9dbc8bcf8@linux-m68k.org>

Hi Finn,

On 13/09/21 13:34, Finn Thain wrote:
>
> This appears to work on Aranym, QEMU and the Quadra 630 I have here.
> It is completely untested on Coldfire etc. I don't even know whether the
> right memory mappings are in place for this to actually work as intended.

The comment just above the section from paging_init() in your patch 
states that all physical memory is mapped into kernel virtual address 
space. I don't think that mapping is contiguous though.

> Would someone take a look please?
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index 6e40f7f29ebc..d87e12b4855b 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -9,6 +9,7 @@ config M68K
>  	select ARCH_HAVE_NMI_SAFE_CMPXCHG if RMW_INSNS
>  	select ARCH_MIGHT_HAVE_PC_PARPORT if ISA
>  	select ARCH_NO_PREEMPT if !COLDFIRE
> +	select ARCH_USE_MEMTEST
>  	select ARCH_WANT_IPC_PARSE_VERSION
>  	select BINFMT_FLAT_ARGVP_ENVP_ON_STACK
>  	select DMA_DIRECT_REMAP if HAS_DMA && MMU && !COLDFIRE
> diff --git a/arch/m68k/mm/motorola.c b/arch/m68k/mm/motorola.c
> index 3a653f0a4188..d6301a094fc1 100644
> --- a/arch/m68k/mm/motorola.c
> +++ b/arch/m68k/mm/motorola.c
> @@ -455,6 +455,8 @@ void __init paging_init(void)
>
>  	flush_tlb_all();
>
> +	early_memtest(min_addr, max_addr);
> +
>  	/*
>  	 * initialize the bad page table and bad page to point
>  	 * to a couple of allocated pages
>

I'd rather start that from availmem, not from min_addr ... I'm amazed 
this works - I'd expect the kernel text segment to get trashed by the 
memory test routines.

Cheers,

	Michael

  reply	other threads:[~2021-09-13  3:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13  1:34 [RFC] m68k: Enable memtest kernel parameter Finn Thain
2021-09-13  3:40 ` Michael Schmitz [this message]
2021-09-13  5:17   ` Michael Schmitz
2021-09-13  5:17   ` Finn Thain
2021-09-13  5:51     ` Michael Schmitz
2021-09-13  5:56     ` Mike Rapoport
2021-09-13  6:42       ` Mike Rapoport
2021-09-13  6:53       ` Michael Schmitz
2021-09-13  7:59       ` Finn Thain
2021-09-13  5:42   ` Mike Rapoport
2021-09-13  5:49     ` Michael Schmitz

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=b1b630b8-d6b6-661b-b5c1-2a2831b5b8c2@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=fthain@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=rppt@kernel.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).