From: Magnus Damm <magnus@valinux.co.jp>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
magnus.damm@gmail.com, fastboot@lists.osdl.org,
Magnus Damm <magnus@valinux.co.jp>,
ebiederm@xmission.com, Andrew Morton <akpm@osdl.org>,
Rik van Riel <riel@redhat.com>
Subject: [PATCH 00/02] kexec: Move segment code to assembly files
Date: Tue, 05 Dec 2006 22:37:57 +0900 [thread overview]
Message-ID: <20061205133757.25725.96929.sendpatchset@localhost> (raw)
kexec: Move segment code to assembly files
The following patches rearrange the lowlevel kexec code to perform idt,
gdt and segment setup code in assembly on the code page instead of doing
it in inline assembly in the C files.
Our dom0 Xen port of kexec and kdump executes the code page from the
hypervisor when kexec:ing into a new kernel. Putting as much code as
possible on the code page allows us to keep the amount of duplicated
code low.
These patches are part of the Xen port of kexec and kdump which recently
has been accepted into the xen-unstable.hg tree. Sending them upstream
now is an attempt to simplify future porting work.
Signed-off-by: Magnus Damm <magnus@valinux.co.jp>
---
Applies to 2.6.19.
arch/i386/kernel/machine_kexec.c | 59 ----------------------------------
arch/i386/kernel/relocate_kernel.S | 58 ++++++++++++++++++++++++++++++---
arch/x86_64/kernel/machine_kexec.c | 58 ---------------------------------
arch/x86_64/kernel/relocate_kernel.S | 50 +++++++++++++++++++++++++---
4 files changed, 98 insertions(+), 127 deletions(-)
next reply other threads:[~2006-12-05 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 13:37 Magnus Damm [this message]
2006-12-05 13:38 ` [PATCH 01/02] kexec: Move segment code to assembly file (i386) Magnus Damm
2006-12-05 13:38 ` [PATCH 02/02] kexec: Move segment code to assembly file (x86_64) Magnus Damm
2006-12-05 14:02 ` [PATCH 00/02] kexec: Move segment code to assembly files Vivek Goyal
2006-12-05 15:08 ` Magnus Damm
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=20061205133757.25725.96929.sendpatchset@localhost \
--to=magnus@valinux.co.jp \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=riel@redhat.com \
--cc=vgoyal@in.ibm.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