All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Drake <drake@endlessm.com>,
	Minchan Kim <minchan@kernel.org>
Subject: Re: [regression] Boot crash with: f7426b983a6a ("mm: cma: adjust address limit to avoid hitting low/high memory boundary")
Date: Tue, 9 Dec 2014 08:50:32 +0000	[thread overview]
Message-ID: <20141209085032.GA18348@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20141209075541.GA7714@js1304-P5Q-DELUXE>

On Tue, Dec 09, 2014 at 04:55:42PM +0900, Joonsoo Kim wrote:
> Could you manage this fix for above boot regression in x86?
> Patch itself is so dirty, because __pa_nodebug() is implemented only
> in x86. If someone knows better idea, please let me know.

> +#ifdef CONFIG_X86
> +	/*
> +	 * high_memory isn't direct mapped memory so retrieving it's
> +	 * physical address isn't appropriate. But, it would be useful
> +	 * to check physical address of highmem boundary so it's
> +	 * justfiable to get physical address from it. In x86, there is
> +	 * a validation check for this case, so following workaround is
> +	 * needed to avoid it.
> +	 */
> +	highmem_start = __pa_nodebug(high_memory);
> +#else
> +	highmem_start = __pa(high_memory);
> +#endif

What about:

	highmem_start = __pa(high_memory - 1) + 1;

As "high_memory - 1" should be a valid lowmem address.

-- 
Russell King
ARM architecture Linux Kernel maintainer

  reply	other threads:[~2014-12-09  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 16:39 [regression] Boot crash with: f7426b983a6a ("mm: cma: adjust address limit to avoid hitting low/high memory boundary") Ingo Molnar
2014-11-27 13:05 ` Ingo Molnar
2014-11-28  7:02   ` Joonsoo Kim
2014-12-08 10:56     ` Ingo Molnar
2014-12-09  7:55       ` Joonsoo Kim
2014-12-09  8:50         ` Russell King [this message]
2014-12-10  7:17           ` Joonsoo Kim

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=20141209085032.GA18348@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=drake@endlessm.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=minchan@kernel.org \
    --cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.