From: Nathan Froyd <froydnj@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] ARM: linux-user: Expose VFP registers to signal handlers
Date: Mon, 29 Nov 2010 11:16:50 -0800 [thread overview]
Message-ID: <20101129191650.GM8544@codesourcery.com> (raw)
In-Reply-To: <1290612008-18693-4-git-send-email-peter.maydell@linaro.org>
On Wed, Nov 24, 2010 at 03:20:05PM +0000, Peter Maydell wrote:
> For ARM linux-user mode signal handlers, fill in the ucontext with
> VFP register contents in the same way that the kernel does. We only
> do this for v2 format sigframe (2.6.12 and above); this is actually
> bug-for-bug compatible with the older kernels, which don't save and
> restore VFP registers either.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Nathan Froyd <froydnj@codesourcery.com>
-Nathan
next prev parent reply other threads:[~2010-11-29 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 15:20 [Qemu-devel] [PATCH 0/6] ARM: linux-user: save/restore fpu regs to signal context Peter Maydell
2010-11-24 15:20 ` [Qemu-devel] [PATCH 1/6] ARM: linux-user: Correct size of padding in target_ucontext_v2 Peter Maydell
2010-11-29 19:06 ` Nathan Froyd
2010-11-24 15:20 ` [Qemu-devel] [PATCH 2/6] ARM: Expose vfp_get_fpscr() and vfp_set_fpscr() to C code Peter Maydell
2010-11-29 19:07 ` Nathan Froyd
2010-11-24 15:20 ` [Qemu-devel] [PATCH 3/6] ARM: linux-user: Expose VFP registers to signal handlers Peter Maydell
2010-11-29 19:16 ` Nathan Froyd [this message]
2010-11-24 15:20 ` [Qemu-devel] [PATCH 4/6] ARM: linux-user: Restore VFP state from ucontext on sigreturn Peter Maydell
2010-11-29 19:17 ` Nathan Froyd
2010-11-29 19:19 ` Nathan Froyd
2010-11-24 15:20 ` [Qemu-devel] [PATCH 5/6] ARM: linux-user: Expose iWMMXT registers to signal handlers Peter Maydell
2010-11-24 15:20 ` [Qemu-devel] [PATCH 6/6] ARM: linux-user: Restore iWMMXT state from ucontext on sigreturn Peter Maydell
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=20101129191650.GM8544@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=peter.maydell@linaro.org \
--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).