mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Jeff Dike <jdike@addtoit.com>,
	akpm@linuxfoundation.org, linux-kernel@vger.kernel.org,
	Peter Oberparleiter <oberparleiter@googlemail.com>
Subject: Re: 2.6.26-rc5-mm1: uml link error
Date: Tue, 10 Jun 2008 19:21:50 +0200	[thread overview]
Message-ID: <20080610172150.GA4728@uranus.ravnborg.org> (raw)
In-Reply-To: <484E8DD2.5050603@de.ibm.com>

On Tue, Jun 10, 2008 at 04:21:06PM +0200, Peter Oberparleiter wrote:
> Peter 1 Oberparleiter wrote:
> > Jeff Dike <jdike@addtoit.com> wrote on 10.06.2008 15:57:29:
> > 
> >> On Tue, Jun 10, 2008 at 01:19:27PM +0200, Miklos Szeredi wrote:
> >> > Hmm, uml still doesn't boot with this patch, it dies while calling the
> >> > constructors.  So maybe that SORT contruct is still needed?
> >> > 
> >> > #17 0x08049793 in do_ctors () at init/main.c:706
> >> > #18 0x080499cc in do_basic_setup () at init/main.c:789
> >> > #19 0x08049a43 in kernel_init (unused=0x0) at init/main.c:897
> >> 
> >> This doesn't look like it's in do_initcalls.  What happens with
> >> "initcall_debug"?
> > 
> > Constructor calls inside the kernel happen just before any other
> > initcall. The problem here is that constructors are called from both
> > the host run-time environment as well as from the kernel. I'm
> > working on a patch that disables kernel constructor calling for UML.
> 
> New try: should be fixed with the patch below (applies on top of
> kernel-call-constructors.patch):
> 
> --
> Subject: kernel: disable constructor calling for uml
> 
> From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
> 
> Disable calling of constructor functions from within the kernel for uml
> as they are already called by the host run-time environment.

If this is the right fix then could we please have a less ugly patch.
First off there is no need for the ifdef in vmlinux.lds.h.
And we could get away with some flag or something where we 
call the constructors.

And a comment explaning why UML is different is also missing.

	Sam

  parent reply	other threads:[~2008-06-10 17:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 20:42 Miklos Szeredi
2008-06-10 10:51 ` Peter Oberparleiter
2008-06-10 11:19   ` Miklos Szeredi
2008-06-10 13:57     ` Jeff Dike
2008-06-10 14:08       ` Miklos Szeredi
2008-06-10 14:08       ` Peter 1 Oberparleiter
2008-06-10 14:21         ` Peter Oberparleiter
2008-06-10 15:27           ` Jeff Dike
2008-06-10 16:54           ` Jeff Dike
2008-06-10 17:21           ` Sam Ravnborg [this message]
2008-06-11 12:18             ` Peter Oberparleiter
2008-06-11 12:38               ` Miklos Szeredi

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=20080610172150.GA4728@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linuxfoundation.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=oberparleiter@googlemail.com \
    --cc=peter.oberparleiter@de.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

all inboxes | Powered by JetHome®