All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Simon Horman <horms@verge.net.au>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] kexec: crash: don't save swapper_pg_dir for !CONFIG_MMU configurations
Date: Mon, 27 Feb 2012 15:56:43 -0800	[thread overview]
Message-ID: <20120227155643.cafb1c6d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120227235235.GE24159@verge.net.au>

On Tue, 28 Feb 2012 08:52:35 +0900
Simon Horman <horms@verge.net.au> wrote:

> On Mon, Feb 27, 2012 at 07:30:54PM +0000, Will Deacon wrote:
> > On Mon, Feb 27, 2012 at 12:37:30AM +0000, Simon Horman wrote:
> > > On Sun, Feb 26, 2012 at 10:58:42PM +0000, Will Deacon wrote:
> > > > On Sat, Feb 25, 2012 at 02:37:49AM +0000, Simon Horman wrote:
> > > > 
> > > > > might this cover cases where swapper_pg_dir is interesting?
> > > > 
> > > > The only case where it's interesting is when you have CONFIG_MMU enabled -
> > > > otherwise it's always NULL. If it's #defined as NULL, the current code will
> > > > fail at build time so simply omitting it from the dump seems like the best
> > > > bet to me (the alternative being to add a NULL entry explicitly, but I don't
> > > > see what the gains us).
> > > 
> > > Hi Will,
> > > 
> > > thanks for the clarification. FWIW I am happy with your patch.
> > > 
> > > Reviewed-by: Simon Horman <horms@verge.net.au>
> > 
> > Cheers, Simon. What's the usual path for generic kexec code getting into
> > mainline? Do I need to get this queued somewhere?
> 
> I think that Andrew Morton often picks up these kind of patches.

I'll take anything, if I have any chance of vaguely understanding it ;)

> Andrew, can you pick this up if its reposted with you CCed?
> For reference the patch is as follows:
> 
> 
> From: Will Deacon <will.deacon@arm.com>
> 
> kexec: crash: don't save swapper_pg_dir for !CONFIG_MMU configurations
> 
> nommu platforms don't have very interesting swapper_pg_dir pointers and
> usually just #define them to NULL, meaning that we can't include them in
> the vmcoreinfo on the kexec crash path.
> 
> This patch only saves the swapper_pg_dir if we have an MMU.
> 
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> Reviewed-by: Simon Horman <horms@verge.net.au>
> 
> ---
>  kernel/kexec.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/kexec.c b/kernel/kexec.c
> index 7b08867..cb5d13c 100644
> --- a/kernel/kexec.c
> +++ b/kernel/kexec.c
> @@ -1462,7 +1462,9 @@ static int __init crash_save_vmcoreinfo_init(void)
>  
>  	VMCOREINFO_SYMBOL(init_uts_ns);
>  	VMCOREINFO_SYMBOL(node_online_map);
> +#ifdef CONFIG_MMU
>  	VMCOREINFO_SYMBOL(swapper_pg_dir);
> +#endif
>  	VMCOREINFO_SYMBOL(_stext);
>  	VMCOREINFO_SYMBOL(vmlist);

Well, what might be the effects of this patch?  nommu crashfiles will
no longer have the swapper_pg_dir string?  What are the chances that
someone's (badly written!) downstream tool will crash and burn if this
is absent?


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2012-02-27 23:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 14:40 [PATCH] kexec: crash: don't save swapper_pg_dir for !CONFIG_MMU configurations Will Deacon
2012-02-25  2:37 ` Simon Horman
2012-02-26 22:58   ` Will Deacon
2012-02-27  0:37     ` Simon Horman
2012-02-27 19:30       ` Will Deacon
2012-02-27 23:52         ` Simon Horman
2012-02-27 23:56           ` Andrew Morton [this message]
2012-02-28  0:19             ` Simon Horman
2012-02-28  0:26               ` Andrew Morton
2012-02-28  0:51                 ` Simon Horman
2012-02-28  1:25                   ` Andrew Morton
2012-02-28  1:35                     ` Simon Horman
2012-02-28  9:40                       ` Will Deacon
2012-02-28 20:45                         ` Andrew Morton
2012-02-29  1:32                           ` Simon Horman

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=20120227155643.cafb1c6d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.