public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Magnus Damm <magnus@valinux.co.jp>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	magnus.damm@gmail.com, fastboot@lists.osdl.org,
	ebiederm@xmission.com, Andrew Morton <akpm@osdl.org>,
	Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 00/02] kexec: Move segment code to assembly files
Date: Tue, 5 Dec 2006 09:02:52 -0500	[thread overview]
Message-ID: <20061205140252.GA7959@in.ibm.com> (raw)
In-Reply-To: <20061205133757.25725.96929.sendpatchset@localhost>

On Tue, Dec 05, 2006 at 10:37:57PM +0900, Magnus Damm wrote:
> 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.
> 

I don't think we should be doing this. I would rather prefer code to
keep in C for easier debugging, readability and maintenance. 

> 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.
> 

Is Xen going upstream now? I heard now lhype+KVM seems to be the way. 
Even if it is required, we should do it once Xen goes in.

You have already moved page table setup code to assembly and we should
be getting rid of that code too. 

I would rather live with duplicated code than moving more code in assembly
which can be written in C. Understanding and debugging assembly code
is such a big pain.

Thanks
Vivek

  parent reply	other threads:[~2006-12-05 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 13:37 [PATCH 00/02] kexec: Move segment code to assembly files Magnus Damm
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 ` Vivek Goyal [this message]
2006-12-05 15:08   ` [PATCH 00/02] kexec: Move segment code to assembly files 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=20061205140252.GA7959@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --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=magnus@valinux.co.jp \
    --cc=riel@redhat.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