From: Bernhard Walle <bwalle@suse.de>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "Vivek Goyal" <vgoyal@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] x86: only put e820 ram entries in resource tree
Date: Tue, 26 Aug 2008 10:20:23 +0200 [thread overview]
Message-ID: <20080826102023.2d7cd1c3@halley.suse.de> (raw)
In-Reply-To: <86802c440808251013u20533707w692b5ba94e32e9c9@mail.gmail.com>
* Yinghai Lu [2008-08-25 10:13]:
>
> On Mon, Aug 25, 2008 at 1:39 AM, Bernhard Walle <bwalle@suse.de> wrote:
> > * Yinghai Lu [2008-08-24 15:44]:
> >>
> >> may need user to have new kexec tools that could create e820 table
> >> from /sys/firmware/memmap instead of /proc/iomem for second kernel
> >
> > 2.0.0 has that implemented.
>
> Yes
>
> can you guys make kexec-tools 2.0.0 can be complied to static as one option?
See http://article.gmane.org/gmane.linux.kernel.kexec/2223.
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
next prev parent reply other threads:[~2008-08-26 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 22:44 [PATCH] x86: only put e820 ram entries in resource tree Yinghai Lu
2008-08-25 2:52 ` Eric W. Biederman
2008-08-25 3:43 ` Yinghai Lu
2008-08-25 7:17 ` Ingo Molnar
2008-08-25 13:30 ` Eric W. Biederman
2008-08-25 17:08 ` Yinghai Lu
2008-08-25 8:39 ` Bernhard Walle
2008-08-25 17:13 ` Yinghai Lu
2008-08-26 8:20 ` Bernhard Walle [this message]
2008-08-25 14:19 ` Vivek Goyal
2008-08-25 17:11 ` 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=20080826102023.2d7cd1c3@halley.suse.de \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=yhlu.kernel@gmail.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.