public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: ebiederm@xmission.com (Eric W. Biederman), khalid.aziz@hp.com
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	linux-ia64@vger.kernel.org, fastboot@osdl.org,
	<linux-kernel@vger.kernel.org>
Subject: Re: [BROKEN PATCH] kexec for ia64
Date: Wed, 4 Aug 2004 09:24:12 -0700	[thread overview]
Message-ID: <200408040924.12407.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <m18ycvhx1j.fsf@ebiederm.dsl.xmission.com>

On Wednesday, August 4, 2004 6:07 am, Eric W. Biederman wrote:
> "Randy.Dunlap" <rddunlap@osdl.org> writes:
> > On Mon, 26 Jul 2004 15:36:05 -0700 Jesse Barnes wrote:
> > | On Monday, July 26, 2004 3:24 pm, Jesse Barnes wrote:
> > | >   o userspace tools need ia64 support
>
> Correct.  But all they need are the ia64 bits of the ELF loader,
> plus ia64 specific goo.  The generic part of the ELF loader is already
> written.

I think Khalid might already have these bits done.

> Sort of fundamentally they are arch dependent.
>
> I believe that DMA FIXME is a red hearing.  Initially that patch
> was targeted for a kernel without device_shutdown(), so I was
> likely considering the old trick of running through all of the PCI
> devices and disabling their bus master bit.

Yeah, I added that bit to remind me to think about it.

> 1) What is the kernel's argument passing format, what arguments

Right, and that should be pretty straightforward.

> 2) The code itself in machine_kexec.c and relocate_kernel.S needs
>    to place the machine in a state where virtual and physical addresses
>    are identity mapped.  And the arch specific registers are in some
>    well defined state.  Usually the least setup you can guarantee to make
>    it work the better.
>
> (This is the kernel side)
>
> We should probably start capturing these pieces of information in
> a kexec.3 man page.  Volunteers?
>
> For ia64 in particular I believe the binary arguments are the
> FPSWA and EFI memory map, and the firmware entry points (PAL and SAL
> and EFI).

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.

Jesse

  reply	other threads:[~2004-08-04 16:27 UTC|newest]

Thread overview: 9+ 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 [this message]
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

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=200408040924.12407.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=khalid.aziz@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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