From: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix, v4
Date: Sun, 18 May 2003 08:45:54 +0200 [thread overview]
Message-ID: <m3k7cohhwd.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20030516233013$140e@gated-at.bofh.it> (Andrew Morton's message of "Sat, 17 May 2003 01:30:13 +0200")
Andrew Morton <akpm@digeo.com> writes:
> arch/x86_64/
> ------------
> - time handling is broken. Need to move up 2.4 time.c code.
[...]
> - some fixes from 2.4 still need to be merged
This is done (except the time.c stuff)
> - 32bit vsyscalls seem to be broken
>
> - 32bit elf coredumps are broken
These two are fixed.
>
> - need to coredump 64bit vsyscall code with dwarf2
This has been started, but is stalled due to binutils/gcc issues.
>
> - move 64bit signal trampolines into vsyscall code and add dwarf2 for it.
First part of it has been done. Just need to add the dwarf2. Also requires
the previous item.
>
> - describe kernel assembly with dwarf2 annotations for kgdb (currently
> waiting on some binutils changes for this)
binutils patch for it exists now, still need to get the hands dirty on it.
But all hasn't been merged yet because Linus drops patches recently :-(
-Andi
next prev parent reply other threads:[~2003-05-18 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030516233011$3c2c@gated-at.bofh.it>
[not found] ` <20030516233013$140e@gated-at.bofh.it>
2003-05-18 6:45 ` 2.6 must-fix, v4 Andi Kleen
2003-05-18 18:56 ` Geert Uytterhoeven
2003-05-18 6:45 ` Andi Kleen [this message]
2003-05-16 23:17 Andrew Morton
2003-05-16 23:17 ` Andrew Morton
2003-05-17 1:31 ` William Lee Irwin III
2003-05-17 5:16 ` Joseph Fannin
2003-05-17 5:42 ` William Lee Irwin III
2003-05-17 12:34 ` Stuffed Crust
2003-05-17 19:29 ` Felipe Alfaro Solana
2003-05-17 8:05 ` Lars Marowsky-Bree
2003-05-19 23:33 ` Randy.Dunlap
2003-05-20 0:51 ` Chris Mason
2003-05-16 23:33 ` Greg KH
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=m3k7cohhwd.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/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