From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Bernhard Walle" <bwalle@suse.de>
Cc: akpm@linux-foundation.org, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH] x86: Move crashkernel reservation before dma32_reserve_bootmem()
Date: Fri, 18 Jul 2008 09:22:26 -0700 [thread overview]
Message-ID: <86802c440807180922l3500082chf7dcf0a1bafc6629@mail.gmail.com> (raw)
In-Reply-To: <20080718115213.3c87f8f8@halley.suse.de>
On Fri, Jul 18, 2008 at 2:52 AM, Bernhard Walle <bwalle@suse.de> wrote:
> * Yinghai Lu [2008-07-17 15:50]:
>>
>> > + /*
>> > + * dma32_reserve_bootmem() allocates bootmem which may conflict
>> > + * with the crashkernel command line, so do that before
>> > + */
>> > + reserve_crashkernel();
>> > +
>> > #ifdef CONFIG_X86_64
>> > dma32_reserve_bootmem();
>> > #endif
>> > @@ -808,7 +814,6 @@ void __init setup_arch(char **cmdline_p)
>> > */
>> > find_smp_config();
>> > #endif
>> > - reserve_crashkernel();
>> >
>> > reserve_ibft_region();
>>
>> Joe Jin already had another one to move dma32_reserve_bootmem later
>
> Commit id? Current status?
it seems commit description from you is more good.
please create one version move dma32_reserve_boot_mem after
reserve_crashkernel and use your commit description.
YH
next prev parent reply other threads:[~2008-07-18 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2008-07-18 17:07 ` [PATCH] x86: Move dma32_reserve_bootmem() after reserve_crashkernel() Bernhard Walle
2008-07-18 21:36 ` Ingo Molnar
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=86802c440807180922l3500082chf7dcf0a1bafc6629@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®