The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Magnus Damm <magnus@valinux.co.jp>
Cc: fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kexec: Remove order
Date: Wed, 12 Apr 2006 22:18:23 -0600	[thread overview]
Message-ID: <m164le6rcg.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060413030040.20516.9231.sendpatchset@cherry.local> (Magnus Damm's message of "Thu, 13 Apr 2006 11:59:39 +0900 (JST)")

Magnus Damm <magnus@valinux.co.jp> writes:

> Kexec: Remove order
>
> This patch replaces kexec n-order allocation code with 0-order only.
>
> Almost all kexec allocations are 0-order pages already, with the exception of 
> some x86_64 specific code that requests two physically contiguous pages. 
>
> These two physically contiguous pages are easily replaced with two separate
> pages. The second page is kept in an architecture specific pointer that is
> added to struct kimage.
>
> Using 0-order allocations only greatly simplifies kexec porting work to
> the Xen hypervisor.

NACK.

It is a big intrusive patch that makes it impossible to
port to some architectures, and it obscures what you
are really trying to do which is fix x86_64.

Feel free to fix x86_64, to use only page sized allocates.

Until I see a reasonable argument that none of the architectures
currently supported by the linux kernel would need a multi order
allocation for a kexec port am I interested in removing support.

As I recall the alpha had an architectural need for a 32KB
allocation or something like that.

Eric

  reply	other threads:[~2006-04-13  4:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  2:59 [PATCH] Kexec: Remove order Magnus Damm
2006-04-13  4:18 ` Eric W. Biederman [this message]
2006-04-13  6:21   ` [Fastboot] " Magnus Damm
2006-04-13 10:01     ` Eric W. Biederman
2006-04-14  0:57       ` Magnus Damm
2006-04-13 19:53   ` Christoph Lameter
2006-04-14  1:01     ` 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=m164le6rcg.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    /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