From: Greg KH <gregkh@suse.de>
To: Bernhard Walle <bwalle@suse.de>
Cc: akpm@linux-foundation.org, Bernhard Walle <bernhard.walle@gmx.de>,
kexec@lists.infradead.org, x86@kernel.org,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] x86: Move crashkernel reservation before dma32_reserve_bootmem()
Date: Thu, 17 Jul 2008 00:30:53 -0700 [thread overview]
Message-ID: <20080717073053.GD22343@suse.de> (raw)
In-Reply-To: <20080714153724.228b6dcb@halley.suse.de>
On Mon, Jul 14, 2008 at 03:37:24PM +0200, Bernhard Walle wrote:
> * Vivek Goyal [2008-07-14 09:30]:
> >
> > On Sun, Jul 13, 2008 at 08:49:44PM +0200, Bernhard Walle wrote:
> > > From: Bernhard Walle <bernhard.walle@gmx.de>
> > >
> > > On a x86-64 machine (nothing special I could encounter) I had the problem that
> > > crashkernel reservation with the usual "64M@16M" failed. While debugging that,
> > > I encountered that dma32_reserve_bootmem() reserves a memory region which is in
> > > that area.
> > >
> > > Because dma32_reserve_bootmem() does not rely on a specific offset but
> > > crashkernel does, it makes sense to move the crashkernel reservation up a bit.
> > > I tested that patch and it works without problems. I don't see any negative
> > > effects of that move, but maybe I oversaw something ...
> > >
> > > While the long-term solution is to make the crashkernel reservation dynamic
> > > (which is already done in -tip), this bug should be fixed also short-term for
> > > 2.6.26 (or 2.6.26-stable if it's too short), and that's why I made that patch.
> > >
> > >
> > > Signed-off-by: Bernhard Walle <bwalle@suse.de>
> > > Signed-off-by: Bernhard Walle <bernhard.walle@gmx.de>
> > > ---
> > > arch/x86/kernel/setup_64.c | 7 ++++++-
> > > 1 files changed, 6 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c
> > > index 6dff128..158cefe 100644
> > > --- a/arch/x86/kernel/setup_64.c
> > > +++ b/arch/x86/kernel/setup_64.c
> > > @@ -444,6 +444,12 @@ void __init setup_arch(char **cmdline_p)
> > > contig_initmem_init(0, end_pfn);
> > > #endif
> > >
> > > + /*
> > > + * dma32_reserve_bootmem() allocates bootmem which may conflict
> > > + * with the crashkernel command line, so do that before
> > > + */
> > > + reserve_crashkernel();
> > > +
> > > dma32_reserve_bootmem();
> > >
> > > #ifdef CONFIG_ACPI_SLEEP
> > > @@ -484,7 +490,6 @@ void __init setup_arch(char **cmdline_p)
> > > }
> > > }
> > > #endif
> > > - reserve_crashkernel();
> > >
> > > reserve_ibft_region();
> >
> > Looks good to me.
> >
> > Acked-by: Vivek Goyal <vgoyal@redhat.com>
>
> Greg,
>
> would that be something for -stable?
If it affects 2.6.25 or 2.6.26, yes, it would be. Just send it to
stable@kernel.org and we can take it from there as long as it is
accepted already into Linus's tree.
thanks,
greg k-h
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-17 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 18:49 [PATCH] x86: Move crashkernel reservation before dma32_reserve_bootmem() Bernhard Walle
2008-07-14 2:43 ` Ken'ichi Ohmichi
2008-07-14 13:30 ` Vivek Goyal
2008-07-14 13:37 ` Bernhard Walle
2008-07-17 7:30 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 22:15 Bernhard Walle
2008-07-17 22:50 ` Yinghai Lu
2008-07-18 9:52 ` Bernhard Walle
2008-07-18 16:22 ` Yinghai Lu
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=20080717073053.GD22343@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bernhard.walle@gmx.de \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/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