From: Nathan Froyd <froydnj@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] linux-user: add ppc signal handling
Date: Tue, 21 Apr 2009 19:32:12 -0700 [thread overview]
Message-ID: <1240367535-20081-1-git-send-email-froydnj@codesourcery.com> (raw)
This patch series adds signal handling support for 32-bit PPC linux-user
emulation. It requires a bit of shuffling of target-ppc code to ensure
that we know what the capabilities of our current CPU are so we know
which registers to save.
The signal handling code has been tested by an in-house NPTL
implementation for PPC linux-user emulation. The NPTL implementation
will be coming along shortly, but the signal handling bits are useful on
their own.
-Nathan
next reply other threads:[~2009-04-22 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 2:32 Nathan Froyd [this message]
2009-04-22 2:32 ` [Qemu-devel] [PATCH 1/3] target-ppc: expose cpu capability flags Nathan Froyd
2009-04-22 2:32 ` [Qemu-devel] [PATCH 2/3] linux-user: ppc signal handling Nathan Froyd
2009-04-23 1:22 ` malc
2009-04-23 1:55 ` Nathan Froyd
2009-04-23 14:44 ` malc
2009-04-23 16:11 ` Nathan Froyd
2009-04-23 23:18 ` malc
2009-04-22 2:32 ` [Qemu-devel] [PATCH 3/3] linux-user: support ELF_HWCAP for PPPC Nathan Froyd
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=1240367535-20081-1-git-send-email-froydnj@codesourcery.com \
--to=froydnj@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).