[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EAD360D.6010004@gmail.com>
Date: Sun, 30 Oct 2011 12:33:33 +0100
From: Marco Stornelli <marco.stornelli@...il.com>
To: Bryan Freed <bfreed@...omium.org>
CC: linux-kernel@...r.kernel.org, sergiu@...omium.org,
akpm@...ux-foundation.org, msb@...omium.org, seiji.aguchi@....com
Subject: Re: [PATCH] ramoops appears geared to not support ARM
Il 30/10/2011 03:07, Bryan Freed ha scritto:
> Right, and that is what I do to get ARM working. The reserve() function
> calls memblock_reserve() to reserve the memory for RAMOOPS. Keeping it
> part of main memory (by not using memblock_remove()) gets the memory
> properly mapped.
>
According to Russell, it needs to use memblock_remove to exclude that
piece of memory.
> The problem I think we need to resolve is that this makes the ramoops
> driver messy.
I agree. Indeed I think we don't need to do anything in the driver. The
problem is only how to exclude a piece of memory from kernel main memory
view. For x86 it's trivial, for ARM it doesn't, but it's still possible.
Marco
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists