linux-um archives
 help / color / mirror / Atom feed
From: Paolo Giarrusso <blaisorblade_personal@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Gerd Knorr <kraxel@bytesex.org>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Managing 2.6 merge - url for the patches sent to merge
Date: Tue, 21 Sep 2004 19:55:41 +0200	[thread overview]
Message-ID: <200409211955.41103.blaisorblade_personal@yahoo.it> (raw)
In-Reply-To: <20040921123704.GA20191@bytesex>

On Tuesday 21 September 2004 14:37, Gerd Knorr wrote:
> On Mon, Sep 20, 2004 at 08:30:49PM +0200, Paolo Giarrusso wrote:
> > On Monday 20 September 2004 11:38, Gerd Knorr wrote:
> > > kbuild wishlist item #1: working parallel builds aka "make -j" for UML.
> >
> > Done and posted to Jeff - the complete set of patches which I posted him
> > is now available at this URL (no link in the page, sorry):

> Works great, thanks.

> It took some time to figure that the kernel binary 
> is vmlinux now and not linux any more through, guess that will surprise
> a few other people as well.  Is there some good reason for that change?
Making kallsyms work, since that does a post-processing on vmlinux which 
results become invalid if you later relink it - adding a "mv vmlinux linux" 
is not a problem to avoid surprising people, I've just been waiting for "what 
to do here".

In fact, now, when UML outputs a stack trace, it also outputs the function 
names, as 2.6 i386 (and other archs) do. Check also uml-use-kallsyms about 
this. It should help bug reporters, too.

Finally, this also fixes the "empty /proc/kallsyms" problem.

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2004-09-21 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 17:44 [uml-devel] Managing 2.6 merge Paolo Giarrusso
2004-09-18 20:52 ` Jeff Dike
2004-09-19  9:43   ` Paolo Giarrusso
2004-09-19 11:38   ` Paolo Giarrusso
2004-09-20  9:38     ` Gerd Knorr
2004-09-20 18:30       ` [uml-devel] Managing 2.6 merge - url for the patches sent to merge Paolo Giarrusso
2004-09-21  3:21         ` Jeff Dike
2004-09-21 18:01           ` Paolo Giarrusso
2004-09-21 19:11             ` Henrik Nordstrom
2004-09-21 12:37         ` Gerd Knorr
2004-09-21 17:55           ` Paolo Giarrusso [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=200409211955.41103.blaisorblade_personal@yahoo.it \
    --to=blaisorblade_personal@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=kraxel@bytesex.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