From: Peter Maydell <peter.maydell@linaro.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Peter Maydell <Peter.Maydell@arm.com>,
"Wang, Yalin" <Yalin.Wang@sonymobile.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v2] arm:extend the reserved mrmory for initrd to be page aligned
Date: Fri, 5 Dec 2014 18:59:32 +0000 [thread overview]
Message-ID: <CAFEAcA_4ZNq-mxEK82nXAMJCg8oSyqXeUte3wGXHcLv5dWr_OQ@mail.gmail.com> (raw)
In-Reply-To: <20141205184418.GF31222@e104818-lin.cambridge.arm.com>
On 5 December 2014 at 18:44, Catalin Marinas <catalin.marinas@arm.com> wrote:
> On Fri, Dec 05, 2014 at 05:27:02PM +0000, Russell King - ARM Linux wrote:
>> which makes the summary line rather misleading, and I really don't think
>> we need to do this on ARM for the simple reason that we've been doing it
>> for soo long that it can't be an issue.
>
> I started this as a revert and then realised that it doesn't solve
> anything for arm32 without changing the poisoning.
>
> Anyway, if you are happy with how it is, I'll drop the arm32 part. As I
> said yesterday, the issue is worse for arm64 with 64K pages.
If you do want to retain the arm32 "mustn't be in the 4K page of
the initrd tail" behaviour then it would probably be a good idea
to document this in the Booting spec.
thanks
-- PMM
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-12-05 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 11:07 Wang, Yalin
2014-09-15 11:33 ` Russell King - ARM Linux
2014-09-15 14:20 ` Wang, Yalin
2014-12-04 12:03 ` Catalin Marinas
2014-12-05 2:35 ` Wang, Yalin
2014-12-05 14:41 ` Catalin Marinas
2014-12-05 12:05 ` Will Deacon
2014-12-05 17:07 ` Catalin Marinas
2014-12-05 17:27 ` Russell King - ARM Linux
2014-12-05 17:52 ` Peter Maydell
2014-12-05 18:44 ` Catalin Marinas
2014-12-05 18:59 ` Peter Maydell [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=CAFEAcA_4ZNq-mxEK82nXAMJCg8oSyqXeUte3wGXHcLv5dWr_OQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Peter.Maydell@arm.com \
--cc=Will.Deacon@arm.com \
--cc=Yalin.Wang@sonymobile.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@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