All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] Remaining VFP fixes
Date: Wed,  1 Feb 2012 14:03:10 +0000	[thread overview]
Message-ID: <1328104992-8016-1-git-send-email-will.deacon@arm.com> (raw)

Hello,

This is v3 of the patches originally posted here:

v1: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082168.html
v2: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082383.html

Patches 1-3 from v2 of the series are now in the patch system, so this
posting is a rework of what was previously patch 4/4.

The main change is that the VFP save/restore code is now moved out of
signal.c and into vfpmodule.c, since that is where the low-level
knowledge belongs.

I tested the changes with the `risu' tool for 24 hours on my (A9)
vexpress without any issues.

Cheers,

Will


Will Deacon (2):
  ARM: vfp: move user vfp state save/restore code out of signal.c
  ARM: vfp: clear fpscr length and stride bits on entry to sig handler

 arch/arm/include/asm/thread_info.h |    7 +++
 arch/arm/kernel/signal.c           |   57 ++-------------------
 arch/arm/vfp/vfpmodule.c           |   99 ++++++++++++++++++++++++++++++++++++
 3 files changed, 111 insertions(+), 52 deletions(-)

-- 
1.7.4.1

             reply	other threads:[~2012-02-01 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 14:03 Will Deacon [this message]
2012-02-01 14:03 ` [PATCH v3 1/2] ARM: vfp: move user vfp state save/restore code out of signal.c Will Deacon
2012-02-01 14:03 ` [PATCH v3 2/2] ARM: vfp: clear fpscr length and stride bits on entry to sig handler Will Deacon
2012-02-03 11:12   ` Dave Martin
2012-02-03 11:58     ` Will Deacon

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=1328104992-8016-1-git-send-email-will.deacon@arm.com \
    --to=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.