public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid.aziz@hp.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	Randy Dunlap <rddunlap@osdl.org>,
	Linux ia64 <linux-ia64@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	fastboot@osdl.org
Subject: Re: [Fastboot] RE: [BROKEN PATCH] kexec for ia64
Date: Thu, 05 Aug 2004 13:18:32 -0600	[thread overview]
Message-ID: <1091733511.23589.86.camel@lyra.fc.hp.com> (raw)
In-Reply-To: <m1vffxh5xe.fsf@ebiederm.dsl.xmission.com>

On Thu, 2004-08-05 at 11:05, Eric W. Biederman wrote:
> 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?

No, it does not work on ia64. Once I have basic code in place to get
somewhat working kexec on ia64, I am considering looking into fixing
/proc/iomem.

> 
> All of that information needs to get exported to user space so
> /sbin/kexec can pass it to the new kernel.
> 
> Eric

-- 
Khalid

====================================================================
Khalid Aziz                                Linux and Open Source Lab
(970)898-9214                                        Hewlett-Packard
khalid_aziz@hp.com                                  Fort Collins, CO

"The Linux kernel is subject to relentless development" 
				- Alessandro Rubini



  reply	other threads:[~2004-08-05 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200407261524.40804.jbarnes@engr.sgi.com>
     [not found] ` <200407261536.05133.jbarnes@engr.sgi.com>
     [not found]   ` <20040730155504.2a51b1fa.rddunlap@osdl.org>
2004-08-04 13:07     ` [BROKEN PATCH] kexec for ia64 Eric W. Biederman
2004-08-04 16:24       ` Jesse Barnes
2004-08-04 23:33       ` Grant Grundler
2004-08-05  2:14         ` [Fastboot] " Eric W. Biederman
2004-08-05 15:39           ` Grant Grundler
2004-08-05 16:44             ` Eric W. Biederman
2004-08-05 16:45       ` Luck, Tony
2004-08-05 17:05         ` [Fastboot] " Eric W. Biederman
2004-08-05 19:18           ` Khalid Aziz [this message]
2004-08-05 19:44 [Fastboot] " Tolentino, Matthew E
2004-08-05 21:29 ` Eric W. Biederman

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=1091733511.23589.86.camel@lyra.fc.hp.com \
    --to=khalid.aziz@hp.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=jbarnes@engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox