From: Ingo Molnar <mingo@elte.hu>
To: Bernhard Walle <bwalle@suse.de>
Cc: x86@kernel.org, kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation automatically
Date: Thu, 3 Jul 2008 15:14:56 +0200 [thread overview]
Message-ID: <20080703131456.GA12102@elte.hu> (raw)
In-Reply-To: <20080627202932.16634031@kopernikus.site>
* Bernhard Walle <bwalle@suse.de> wrote:
> > > But in general policy should go in userspace (if possible), so I
> > > agree with you that kexec-tools can handle that.
> >
> > At a quick skim the patch looks good. I thought I had initially
> > implemented the code to work this way but apparently in all of the
> > churn that aspect of it got lost.
> >
> > Let's start with trying to allocate the memory as low as possible
> > for a crash kernel (I think you are already doing that).
>
> Yes, in 95 % of the cases the crashkernel still gets reserved at 16M.
ok - i've applied it to tip/x86/crashdump - thanks Bernhard.
Ingo
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-03 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 19:54 [PATCH] x86: Find offset for crashkernel reservation automatically Bernhard Walle
2008-06-27 13:32 ` Vivek Goyal
2008-06-27 13:42 ` Vivek Goyal
2008-06-27 14:06 ` Bernhard Walle
2008-06-27 14:19 ` Vivek Goyal
2008-06-27 14:22 ` Bernhard Walle
2008-06-27 18:00 ` Eric W. Biederman
2008-06-27 18:29 ` Bernhard Walle
2008-07-03 13:14 ` Ingo Molnar [this message]
2008-07-14 7:11 ` Yinghai Lu
2008-07-14 9:24 ` Bernhard Walle
2008-07-14 9:44 ` Eric W. Biederman
2008-07-14 17:06 ` Yinghai Lu
2008-07-14 17:30 ` Eric W. Biederman
2008-07-14 18:17 ` Yinghai Lu
2008-07-14 18:41 ` Eric W. Biederman
2008-07-14 18:47 ` Bernhard Walle
2008-07-14 18:55 ` Eric W. Biederman
2008-07-14 19:08 ` 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=20080703131456.GA12102@elte.hu \
--to=mingo@elte.hu \
--cc=bwalle@suse.de \
--cc=ebiederm@xmission.com \
--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