Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
	Jurriaan <thunder7@xs4all.nl>,
	linux-kernel@vger.kernel.org,
	Helge Hafting <helgehaf@aitel.hist.no>,
	Horms <horms@verge.net.au>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] x86_64: Reflect the relocatability of the kernel in the ELF header.
Date: Mon, 30 Apr 2007 17:17:07 +0200	[thread overview]
Message-ID: <200704301717.08230.ak@suse.de> (raw)
In-Reply-To: <m1slah6gm0.fsf@ebiederm.dsl.xmission.com>

On Monday 30 April 2007 17:12:39 Eric W. Biederman wrote:
> 
> Currently because vmlinux does not reflect that the kernel is relocatable
> we still have to support CONFIG_PHYSICAL_START.  So this patch adds a small
> c program to do what we cannot do with a linker script set the elf header
> type to ET_DYN.
> 
> Since last time I have fixed the type to be in my code ET_DYN (oops),
> and verified this works with kexec.  I realized while testing that we
> don't have anyway of identifying a kernel vmlinux as linux so we
> probably want to add an ELF note but that will be another patch.

The patch is ok for me, but does it pass Vivek's usual testing?

-Andi

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2007-04-30 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 15:12 [PATCH 1/2] x86_64: Reflect the relocatability of the kernel in the ELF header Eric W. Biederman
2007-04-30 15:17 ` Andi Kleen [this message]
2007-05-01  3:55   ` Vivek Goyal
2007-05-01  4:20     ` Eric W. Biederman
2007-05-01  5:06       ` Vivek Goyal
2007-05-01  5:26         ` Eric W. Biederman
2007-05-01  6:25           ` Andi Kleen
2007-05-01  5:54             ` Eric W. Biederman
2007-05-01  6:44               ` Vivek Goyal
2007-05-28 10:54         ` Bernhard Walle
2007-05-28 11:09           ` Vivek Goyal
2007-05-28 14:39             ` Bernhard Walle
2007-06-01 12:26               ` Bernhard Walle
2007-05-28 14:57           ` Andi Kleen
     [not found] <20070331005303.354411f0.akpm@linux-foundation.org>
     [not found] ` <20070401052932.GA9894@amd64.of.nowhere>
     [not found]   ` <m1ircghb6w.fsf@ebiederm.dsl.xmission.com>
     [not found]     ` <20070331232957.e1c93f19.akpm@linux-foundation.org>
     [not found]       ` <20070402074159.GA13704@in.ibm.com>
     [not found]         ` <m1abxrf9o3.fsf@ebiederm.dsl.xmission.com>
     [not found]           ` <20070402094520.GC13704@in.ibm.com>
     [not found]             ` <m1648eg01d.fsf@ebiederm.dsl.xmission.com>
     [not found]               ` <20070403040152.GA5108@in.ibm.com>
     [not found]                 ` <m1zm5qc9q2.fsf@ebiederm.dsl.xmission.com>
     [not found]                   ` <20070403100349.GA21759@in.ibm.com>
2007-04-23  5:12                     ` Eric W. Biederman
2007-04-24  6:31                       ` Vivek Goyal
2007-04-24  7:21                         ` Eric W. Biederman

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=200704301717.08230.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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