From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@nokia.com>
Subject: [Qemu-devel] [PATCH 0/5] linux-user for-usptream patches
Date: Tue, 26 Jan 2010 15:59:59 +0000 [thread overview]
Message-ID: <1264521604-2020-1-git-send-email-riku.voipio@iki.fi> (raw)
From: Riku Voipio <riku.voipio@nokia.com>
Some fixes to avoid hanging, make arm uname match selected
cpu, and fixes to cp15.c13 registers for linux-user tls register
access.
Loïc Minier (1):
linux-user: adapt uname machine to emulated CPU
Riku Voipio (4):
fix locking error with current_tb
linux-user: remove signal handler before calling abort()
linux-user: Add access to TLS registers
target-arm: Thread ID Registers are ARMv6K +
Makefile.target | 2 +-
exec.c | 13 +++++++-
linux-user/cpu-uname.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++
linux-user/cpu-uname.h | 1 +
linux-user/syscall.c | 3 +-
target-arm/helper.c | 39 +++++++++++++++++++++++++-
6 files changed, 125 insertions(+), 5 deletions(-)
create mode 100644 linux-user/cpu-uname.c
create mode 100644 linux-user/cpu-uname.
next reply other threads:[~2010-01-26 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 15:59 Riku Voipio [this message]
2010-01-26 16:00 ` [Qemu-devel] [PATCH 1/5] linux-user: adapt uname machine to emulated CPU Riku Voipio
2010-01-26 16:00 ` [Qemu-devel] [PATCH 2/5] fix locking error with current_tb Riku Voipio
2010-01-26 16:00 ` [Qemu-devel] [PATCH 3/5] linux-user: remove signal handler before calling abort() Riku Voipio
2010-01-26 16:00 ` [Qemu-devel] [PATCH 4/5] linux-user: Add access to TLS registers Riku Voipio
2010-01-26 16:27 ` Laurent Desnogues
2010-01-26 20:00 ` Riku Voipio
2010-01-26 16:00 ` [Qemu-devel] [PATCH 5/5] target-arm: Thread ID Registers are ARMv6K + Riku Voipio
2010-01-26 16:28 ` Laurent Desnogues
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=1264521604-2020-1-git-send-email-riku.voipio@iki.fi \
--to=riku.voipio@iki.fi \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@nokia.com \
/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).