From: Khalid Aziz <khalid.aziz@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] kexec on ia64
Date: Tue, 16 Nov 2004 03:46:49 +0000 [thread overview]
Message-ID: <1100576808.2371.0.camel@minuet.fc.hp.com> (raw)
In-Reply-To: <1100551268.26287.35.camel@lyra.fc.hp.com>
Another limitation I forgot to mention. I have not added support for
compressed kernel to kexec-tools yet. It is on my list of things to do
next.
--
Khalid
On Mon, 2004-11-15 at 13:32, Khalid Aziz wrote:
> I have been able to get kexec working on ia64. I am attaching the kernel
> patch and kexec-tools patch. For the kernel patch, start with 2.6.8
> kernel from kernel.org, apply ia64 patch
> <http://www.kernel.org/pub/linux/kernel/ports/ia64/v2.6/linux-2.6.8-ia64-040901.diff.bz2>, apply Eric' 2.6.8.1-kexec3 patch <http://www.xmission.com/~ebiederm/files/kexec/2.6.8.1-kexec3> and apply attached 2.6.8.1-kexec3-ia64.diff patch. For kexec-tools, apply attached kexec-tools-1.98-ia64.diff patch to Eric's kexec-tools 1.98 sources <http://www.xmission.com/~ebiederm/files/kexec/kexec-tools-1.98.tgz>.
>
> At this point, I have done minimal testing. Here is what I know does not
> work currently:
>
> 1. No support for initrd for kexec'd kernel
>
> 2. No support for new kernel parameters for kexec'd kernel.
>
> 3. If a kernel is booted up with "mem=" or "max_addr=" to restrict the
> amount of memory, a kernel kexec'd from this kernel will only see the
> same amount of memory as this one. This is not only due to the new
> kernel being kexec'd with the same parameter, but also becuase the EFI
> memory map as passed to the kernel by ELILO gets trimmed very early on
> by the kernel. I have tried adding code to save the memory map early on
> and then pass this saved memory map to kexec'd kernel, but apparently I
> still am not saving it early enough. I wait until bootmem allocator has
> been initailized so I can allocate memory to save unmolested EFI memory
> map in. In the process of initializing bootmem allocator, kernel calls
> efi-Memory_map_walk() which in turn trims the memory map. I am looking
> into allocating memory out of the EFI memory map before the first
> efi_mem_map_walk() happens, so I can save pristine EFI memmap for use
> later by kexec.
>
> Here is what I have not tested yet:
>
> 1. I am not sure if ACPI subsystem is happy in kexec'd kernel. I have
> not seen any problems, but I have not tested it enough either.
>
> 2. Stability of kexec'd kernel over long term. It ran fine for an hour
> not doing much :)
>
> Here is what I am working on next:
>
> 1. Save EFI memory map before it is trimmed.
>
> 2. Fix up /proc/iomem on ia64 so we can enable validating memory range
> in kexec tools.
>
> 3. Add a /proc interface to enable reboots on panic and INIT (and
> possibly MCA) to be kexec reboots.
>
> 4. Add initrd support.
>
> Any feedback on these patches is welcome. Any patch to fix problems in
> these patches is very much appreciated :)
--
Khalid Aziz Linux and Open Source Lab
(970)898-9214 Hewlett-Packard
khalid_aziz@hp.com Fort Collins, CO
next prev parent reply other threads:[~2004-11-16 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:41 [Fastboot] [PATCH] kexec on ia64 Khalid Aziz
2004-11-16 3:46 ` Khalid Aziz [this message]
2006-04-05 0:36 ` Zou, Nanhai
[not found] ` <20060405101243.e3e4f772.kamezawa.hiroyu@jp.fujitsu.com>
2006-04-05 2:49 ` Eric W. Biederman
2006-04-05 4:31 ` KAMEZAWA Hiroyuki
2006-04-05 1:13 ` Zou, Nanhai
2006-04-05 1:27 ` KAMEZAWA Hiroyuki
2006-04-05 1:34 ` Zou, Nanhai
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:20 Khalid Aziz
2006-04-04 18:13 ` [Fastboot] " Eric W. Biederman
2006-04-05 16:34 ` 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=1100576808.2371.0.camel@minuet.fc.hp.com \
--to=khalid.aziz@hp.com \
--cc=linux-ia64@vger.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