From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] Support NPTL support for ColdFire and related fixes
Date: Mon, 01 Mar 2010 22:19:25 +0300 [thread overview]
Message-ID: <4B8C133D.2030900@codesourcery.com> (raw)
The following series of 4 patches adds NPTL support for ColdFire
user-mode emulation and fixes several related issues, mainly in signal
handling.
0001-Add-NPTL-support-for-ColdFire.patch
Implement new kernel syscalls to support TLS storage and synchronization
(merged to 2.6.34 kernel)
0002-Handle-SIGKILL-and-SIGCHLD.patch
Target-independent improvement to add SIGKILL and SIGCHLD to the list of
handled signals.
0003-Fix-signal-handling-for-ColdFire.patch
Fix and improve signal handling support for ColdFire.
0004-Define-MMAP_SHIFT-for-ColdFire.patch
Follow kernel behavior.
The patches were tested on GCC and GLIBC testsuites. All signal
handling and frame unwinding GCC tests pass. GLIBC testsuite now has
more tests passing with no regressions.
Any comments?
Thanks,
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
next reply other threads:[~2010-03-01 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:19 Maxim Kuvyrkov [this message]
2010-03-01 19:31 ` [Qemu-devel] [PATCH 1/4] Add NPTL support for ColdFire Maxim Kuvyrkov
2010-03-01 19:32 ` [Qemu-devel] [PATCH 2/4] Handle SIGKILL and SIGCHLD Maxim Kuvyrkov
2010-03-01 19:32 ` [Qemu-devel] [PATCH 3/4] Fix signal handling for ColdFire Maxim Kuvyrkov
2010-03-03 13:17 ` Richard Henderson
2010-03-03 13:36 ` Maxim Kuvyrkov
2010-03-01 19:33 ` [Qemu-devel] [PATCH 4/4] Define MMAP_SHIFT " Maxim Kuvyrkov
2010-05-21 9:45 ` [Qemu-devel] {PING}[PATCH 0/4] Support NPTL support for ColdFire and related fixes Maxim Kuvyrkov
2010-07-15 8:51 ` [Qemu-devel] {PING^2} [PATCH " Maxim Kuvyrkov
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=4B8C133D.2030900@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).