From: imre.deak@nokia.com (imre.deak at nokia.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3 0/3] ARM: VFP: Save / restore VFP state on the signal handler path
Date: Mon, 29 Mar 2010 19:17:37 +0300 [thread overview]
Message-ID: <1269879460-1038-1-git-send-email-imre.deak@nokia.com> (raw)
In-Reply-To: <b8a1d37c5f981cdd2e83c9fd98198832324cd57c.1265315249.git.imre.deak@nokia.com>
This fixes a VFP corruption problem in a process's main thread, when
both the main thread and a signal handler triggered for the process
uses floating point ops.
Changes since v2 according to Russell's comments and patches:
- refactor vfp_sync_state to make it clearer
- break vfp_sync_state into vfp_{save/restore}_hwstate for efficiency
- Keep the additional VFP exception registers in a separate struct. This
way we'll keep the existing ABI intact.
--Imre
next prev parent reply other threads:[~2010-03-29 16:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1242744292-23776-1-git-send-email-imre.deak@nokia.com>
2010-02-04 21:37 ` [RFC PATCH v2 0/2] ARM: VFP: Save / restore VFP state on the signal handler path Imre Deak
2010-02-04 21:38 ` [RFC PATCH v2 1/2] ARM: VFP: add support to sync the VFP state of the current thread Imre Deak
2010-02-06 10:32 ` Russell King - ARM Linux
2010-02-06 11:20 ` Russell King - ARM Linux
2010-02-06 11:32 ` Russell King - ARM Linux
2010-02-06 11:41 ` Russell King - ARM Linux
2010-02-06 15:55 ` Imre Deak
2010-02-04 21:38 ` [RFC PATCH v2 2/2] ARM: VFP: preserve the HW context when calling signal handlers Imre Deak
2010-02-06 9:25 ` Russell King - ARM Linux
2010-02-06 10:02 ` Imre Deak
2010-02-06 12:12 ` Russell King - ARM Linux
2010-02-06 16:23 ` Imre Deak
2010-03-29 16:17 ` imre.deak at nokia.com [this message]
2010-03-31 21:23 ` [RFC PATCH v4 0/3] ARM: VFP: Save / restore VFP state on the signal handler path imre.deak at nokia.com
2010-04-02 14:36 ` [RFC PATCH v5 0/2] " imre.deak at nokia.com
2010-04-02 14:36 ` [RFC PATCH v5 1/2] ARM: VFP: fix the SMP versions of vfp_{sync, flush}_hwstate imre.deak at nokia.com
2010-04-12 18:39 ` [RFC PATCH v5 1/2] ARM: VFP: fix the SMP versions of vfp_{sync,flush}_hwstate Russell King - ARM Linux
2010-04-02 14:36 ` [RFC PATCH v5 2/2] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
2010-04-12 18:41 ` Russell King - ARM Linux
2010-04-12 22:04 ` [RFC PATCH v5 0/2] ARM: VFP: Save / restore VFP state on the signal handler path Jamie Lokier
2010-04-13 11:42 ` Imre Deak
2010-04-13 11:59 ` Nicolas Pitre
2010-04-07 16:24 ` [RFC PATCH v4 0/3] " Dirk Behme
2010-04-07 16:39 ` Imre Deak
2010-04-07 17:31 ` Jason McMullan
2010-03-31 21:23 ` [RFC PATCH v4 1/3] ARM: VFP: fix the SMP versions of vfp_{sync, flush}_hwstate imre.deak at nokia.com
2010-03-31 21:23 ` [RFC PATCH v4 2/3] ARM: VFP: make user_vfp struct packed imre.deak at nokia.com
2010-03-31 21:23 ` [RFC PATCH v4 3/3] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 1/3] ARM: VFP: add support to sync the VFP state of the current thread imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 2/3] ARM: VFP: make user_vfp struct packed imre.deak at nokia.com
2010-03-29 16:17 ` [RFC PATCH v3 3/3] ARM: VFP: preserve the HW context when calling signal handlers imre.deak at nokia.com
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=1269879460-1038-1-git-send-email-imre.deak@nokia.com \
--to=imre.deak@nokia.com \
--cc=linux-arm-kernel@lists.infradead.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).