From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Russell King <rmk@arm.linux.org.uk>
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: Wed, 10 Dec 2014 16:17:24 +0900 [thread overview]
Message-ID: <20141210071724.GF13371@js1304-P5Q-DELUXE> (raw)
In-Reply-To: <20141209085032.GA18348@flint.arm.linux.org.uk>
On Tue, Dec 09, 2014 at 08:50:32AM +0000, Russell King wrote:
> 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.
Thanks for suggestion.
It looks tricky but it would work. I think that this one need to be
fully tested, so the first dirty one is better for the stable tree.
I will check and test Russell's suggestion and send it as clean-up.
Thanks.
prev parent reply other threads:[~2014-12-10 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 16:39 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
2014-12-10 7:17 ` Joonsoo Kim [this message]
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=20141210071724.GF13371@js1304-P5Q-DELUXE \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=drake@endlessm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®