From: Jeff Dike <jdike@addtoit.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
mingo@elte.hu
Subject: Re: [uml-devel] [PATCH] fix UML on x86-64
Date: Tue, 6 May 2008 23:26:11 -0400 [thread overview]
Message-ID: <20080507032611.GA15155@c2.user-mode-linux.org> (raw)
In-Reply-To: <4820EC0E.1030603@redhat.com>
On Tue, May 06, 2008 at 04:38:54PM -0700, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Linus Torvalds wrote:
> > It breaks things how?
>
> A crash on startup:
It seems that initcalls from the libc side of the house aren't being
called because they're not in the initcall section. The one that
matters here is init_syscall_regs in arch/um/os-Linux/skas/mem.c. If
you run with initcall_debug, you'll notice its absence. As to why,
and why it depends on -fno-unit-at-a-time, I have no idea.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-05-07 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 23:04 [uml-devel] [PATCH] fix UML on x86-64 Ulrich Drepper
2008-05-06 23:27 ` Linus Torvalds
2008-05-06 23:38 ` Ulrich Drepper
2008-05-07 0:06 ` Linus Torvalds
2008-05-07 0:15 ` Linus Torvalds
2008-05-07 1:48 ` Jeff Dike
2008-05-07 1:31 ` Jeff Dike
2008-05-07 3:26 ` Jeff Dike [this message]
2008-05-07 4:00 ` Jeff Dike
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=20080507032611.GA15155@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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