From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, yanok@emcraft.com,
kvm-ppc@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
dwg@au1.ibm.com
Subject: Re: [PATCH] [v3] powerpc/4xx: work around CHIP11 errata in a more PAGE_SIZE-friendly way
Date: Wed, 12 Nov 2008 06:31:29 -0500 [thread overview]
Message-ID: <20081112063129.4d3ae18b@zod.rchland.ibm.com> (raw)
In-Reply-To: <1226464663.13515.1.camel@pasglop>
On Wed, 12 Nov 2008 15:37:43 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2008-11-11 at 18:06 -0600, Hollis Blanchard wrote:
> > The current CHIP11 errata truncates the device tree memory node, and subtracts
> > (hardcoded) 4096 bytes. This breaks kernels with larger PAGE_SIZE, since the
> > bootmem allocator assumes that total memory is a multiple of PAGE_SIZE.
> >
> > Instead, use a device tree memory reservation to reserve only the 256 bytes
> > actually affected by the errata, leaving the total memory size unaltered.
> >
> > Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
>
> While I prefer this approach, won't it break kexec ?
Break it how? Particularly given that kexec doesn't work on 4xx (yet).
> I don't understand why we don't just have a bit of code in the kernel
> itself that reserve that page on 44x at boot time and be done with it.
>
> It's like we are trying to be too smart and over-engineer the solution.
I don't think that's it. I think it's more that we're opportunistic and
the wrapper is the easiest place to do this, given that U-Boot itself
will be doing the reserve for platforms that don't require the
wrapper.
So we could do the fixup in-kernel, but how do you do that
deterministically given that U-Boot might have already done it?
josh
next prev parent reply other threads:[~2008-11-12 11:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 0:06 [PATCH] [v3] powerpc/4xx: work around CHIP11 errata in a more PAGE_SIZE-friendly way Hollis Blanchard
2008-11-12 0:09 ` David Gibson
2008-11-12 4:37 ` Benjamin Herrenschmidt
2008-11-12 11:31 ` Josh Boyer [this message]
2008-11-12 11:52 ` Benjamin Herrenschmidt
2008-11-12 15:11 ` Hollis Blanchard
2008-11-12 20:44 ` Benjamin Herrenschmidt
2008-11-12 20:53 ` Josh Boyer
2008-11-13 19:54 ` Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 17:25 Milton Miller
2008-11-14 17:29 ` Milton Miller
2008-11-14 22:09 ` Hollis Blanchard
2008-11-18 20:33 ` Hollis Blanchard
2008-11-24 20:07 ` Hollis Blanchard
2008-11-25 0:10 ` Michael Ellerman
2008-11-25 17:10 ` Milton Miller
2008-11-25 21:17 ` Hollis Blanchard
2008-11-25 21:53 ` Hollis Blanchard
2008-11-25 23:43 ` Michael Ellerman
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=20081112063129.4d3ae18b@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dwg@au1.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=yanok@emcraft.com \
/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).