All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: fastboot@osdl.org, Jon Steel <jon.steel@esentire.com>,
	Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [Fastboot] kexec cant load OpenBSD
Date: Fri, 20 Apr 2007 03:43:48 -0600	[thread overview]
Message-ID: <m1ejmfl6sr.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070420065451.GA14852@in.ibm.com> (Vivek Goyal's message of "Fri, 20 Apr 2007 12:24:51 +0530")

Vivek Goyal <vgoyal@in.ibm.com> writes:

> On Thu, Apr 19, 2007 at 03:49:46PM -0400, Jon Steel wrote:
>> Hi
>> 
>> Im running Gentoo and Im trying to use kexec to start up OpenBSD. I've
>> got it set up correct because I can do a boot into Gentoo. Here is what
>> happens:
>> 
>> base ~ # kexec -l /boot/bsd --type="elf-x86"
>> Base address: d0200120 is not page aligned
>> 
>
> Above address indicates that some loadable program segment is not
> page size(4K) aligned hence kexec is cribbing.
>
> A, "readelf -l /boot/bsd" should display the various program headers.
> I think you shall have to modify linker script of OpenBSD kernel to 
> generate page size aligned loadable segments.
>
> This does raise a question in my mind, why all the program headers
> should be loaded at page size boundaries? Just because ease of handling
> or there is some other reason too?
>
> Eric, you want to shed some light on this requirement?

A) The first problem is that we don't currently have support for OpenBSD
   and it does some weird things, and doesn't quite use the ELF fields
   generically.  So specific support will have to be written for at least
   part of it.

B) In the kernel side of the interface the page alignment restriction is
   important because of how our intermediate buffers work.  For user space
   ELF the page alignment of program segments is an important
   consideration to allow page sharing but for standalone executables we
   really shouldn't care and the restriction probably only exists 
   because we have a simple translation from ELF segment to the kernel
   segments.

Eric

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

      reply	other threads:[~2007-04-20  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4627C7DA.7010401@esentire.com>
2007-04-20  6:54 ` [Fastboot] kexec cant load OpenBSD Vivek Goyal
2007-04-20  9:43   ` Eric W. Biederman [this message]

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=m1ejmfl6sr.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=jon.steel@esentire.com \
    --cc=kexec@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.