[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130919210037.GG2918@verge.net.au>
Date: Thu, 19 Sep 2013 14:00:37 -0700
From: Simon Horman <horms@...ge.net.au>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Anton Blanchard <anton@...ba.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
kexec@...ts.infradead.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Preliminary kexec support for Linux/m68k
On Thu, Sep 19, 2013 at 11:20:22AM +0200, Geert Uytterhoeven wrote:
> On Tue, Sep 17, 2013 at 12:01 PM, Geert Uytterhoeven
> <geert@...ux-m68k.org> wrote:
> > This is a preliminary set of patches to add kexec support for m68k.
>
> > - [PATCH 1/3] m68k: Add preliminary kexec support
> > - [PATCH 2/3] m68k: Add support to export bootinfo in procfs
> > - [PATCH 3/3] [RFC] m68k: Add System RAM to /proc/iomem
> >
> > Notes:
> > - The bootinfo is now saved and exported to /proc/bootinfo, so kexec-tools
> > can read it and pass it (possibly after modification) to the new kernel.
> > This is similar to /proc/atags on ARM.
>
> > - I based [PATCH 3/3] on the PowerPC version, but it's no longer needed as we
> > now get this information from the bootinfo.
> > Does anyone think this is nice to have anyway?
>
> It seems kexec/kdump on ppc don't use /proc/iomem anymore, and only rely on
> /proc/device-tree these days?
I think thats entirely a matter for the m68k kernel maintainers to decide.
But my personal opinion is that it is nice not to add it if it isn't needed.
--
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