From: ebiederm@xmission.com (Eric W. Biederman)
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
khalid.aziz@hp.com, "Randy.Dunlap" <rddunlap@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
fastboot@osdl.org
Subject: Re: [Fastboot] RE: [BROKEN PATCH] kexec for ia64
Date: Thu, 05 Aug 2004 17:05:01 +0000 [thread overview]
Message-ID: <m1vffxh5xe.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F01CB2705@scsmsx401.amr.corp.intel.com>
Hmm. Your mailer did not add any references lines.
"Luck, Tony" <tony.luck@intel.com> writes:
> Jesse Barnes wrote:
> >With the addition of some ACPI tables and such. I don't think
> >those are freed by the kernel right now though, so it should
> >be pretty easy to point at the originals from the newly kexec'd
> >kernel, or make copies.
>
> The "trim_bottom" and "trim_top" functions currently modify
> the memory map in place. But this would only make a difference
> if you tried to kexec a kernel with a smaller granule size than
> the originally running kernel, and even then would only
> result in missing seeing some memory that you might have been
> able to use.
On x86 and x86-64 we can recover the memory map from /proc/iomem.
Does that work on ia64? Can that be fixed to work on ia64?
All of that information needs to get exported to user space so
/sbin/kexec can pass it to the new kernel.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Jesse Barnes" <jbarnes@engr.sgi.com>, <khalid.aziz@hp.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
fastboot@osdl.org
Subject: Re: [Fastboot] RE: [BROKEN PATCH] kexec for ia64
Date: 05 Aug 2004 11:05:01 -0600 [thread overview]
Message-ID: <m1vffxh5xe.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F01CB2705@scsmsx401.amr.corp.intel.com>
Hmm. Your mailer did not add any references lines.
"Luck, Tony" <tony.luck@intel.com> writes:
> Jesse Barnes wrote:
> >With the addition of some ACPI tables and such. I don't think
> >those are freed by the kernel right now though, so it should
> >be pretty easy to point at the originals from the newly kexec'd
> >kernel, or make copies.
>
> The "trim_bottom" and "trim_top" functions currently modify
> the memory map in place. But this would only make a difference
> if you tried to kexec a kernel with a smaller granule size than
> the originally running kernel, and even then would only
> result in missing seeing some memory that you might have been
> able to use.
On x86 and x86-64 we can recover the memory map from /proc/iomem.
Does that work on ia64? Can that be fixed to work on ia64?
All of that information needs to get exported to user space so
/sbin/kexec can pass it to the new kernel.
Eric
next prev parent reply other threads:[~2004-08-05 17:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 22:24 [BROKEN PATCH] kexec for ia64 Jesse Barnes
2004-07-26 22:36 ` Jesse Barnes
2004-07-26 23:09 ` David Mosberger
2004-07-26 23:30 ` David Mosberger
2004-07-26 23:34 ` Jesse Barnes
2004-07-26 23:42 ` David Mosberger
2004-07-27 8:24 ` Christian Hildner
2004-07-27 14:49 ` Jesse Barnes
2004-07-27 16:50 ` Luck, Tony
2004-07-30 22:55 ` Randy.Dunlap
2004-08-04 13:07 ` Eric W. Biederman
2004-08-04 13:07 ` Eric W. Biederman
2004-08-04 16:24 ` Jesse Barnes
2004-08-04 16:24 ` Jesse Barnes
2004-08-04 23:33 ` Grant Grundler
2004-08-04 23:33 ` Grant Grundler
2004-08-05 2:14 ` [Fastboot] " Eric W. Biederman
2004-08-05 2:14 ` Eric W. Biederman
2004-08-05 15:39 ` Grant Grundler
2004-08-05 15:39 ` Grant Grundler
2004-08-05 16:44 ` Eric W. Biederman
2004-08-05 16:44 ` Eric W. Biederman
2004-08-05 19:44 ` Tolentino, Matthew E
2004-08-05 19:44 ` Tolentino, Matthew E
2004-08-05 21:29 ` Eric W. Biederman
2004-08-05 21:29 ` Eric W. Biederman
2004-08-05 22:15 ` Eric W. Biederman
2004-08-05 16:45 ` Luck, Tony
2004-08-05 16:45 ` Luck, Tony
2004-08-05 17:05 ` Eric W. Biederman [this message]
2004-08-05 17:05 ` [Fastboot] " Eric W. Biederman
2004-08-05 19:18 ` Khalid Aziz
2004-08-05 19:18 ` Khalid Aziz
2004-08-05 18:28 ` Grant Grundler
2004-08-05 18:56 ` Eric W. Biederman
2004-08-05 21:24 ` Grant Grundler
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=m1vffxh5xe.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=jbarnes@engr.sgi.com \
--cc=khalid.aziz@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=tony.luck@intel.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.