All of lore.kernel.org
 help / color / mirror / Atom feed
From: imre.deak@nokia.com (Imre Deak)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ARM: VFP: preserve the HW context when callingsignal handlers
Date: Wed, 13 Jan 2010 18:01:42 +0200	[thread overview]
Message-ID: <20100113160142.GB11726@localhost> (raw)
In-Reply-To: <1263397782.32612.56.camel@pc1117.cambridge.arm.com>

On Wed, Jan 13, 2010 at 04:49:42PM +0100, ext Catalin Marinas wrote:
> On Wed, 2010-01-06 at 17:47 +0000, Imre Deak wrote:
> > On Mon, Jan 04, 2010 at 04:18:54PM +0100, Siamashka Siarhei (Nokia-D/Helsinki) wrote:
> > > On Monday 04 January 2010 16:25:49 ext Russell King - ARM Linux wrote:
> > > > On Mon, Jan 04, 2010 at 04:15:26PM +0200, Siarhei Siamashka wrote:
> > > > > On Saturday 13 June 2009 20:04:06 ext Russell King - ARM Linux wrote:
> > > > > > - wait for a new patch which includes these other registers and not
> > > > > > have any ABI visible changes to contend with
> > > > >
> > > > > Sorry for bumping this old thread, but what is the current status of
> > > > > these patches?
> > > >
> > > > What happened was that the 2nd option was decided upon, and then the
> > > > thread died, and probably everyone forgot about it.
> > > >
> > > > So, I'm doing exactly what I said I'd do in the second option.  I'm just
> > > > still waiting some six months on...
> > >
> > > OK, it's understandable. The issue just got a bit more popular now than it
> > > used to be six months ago.
> > >
> > > > If someone comes up with a tested patch, then its something we should
> > > > sort out.
> > >
> > > Thanks for clarifying the situation.
> > 
> > Jamie, you raised the question of FP emulation in user space; could you
> > provide the VFP registers needed for that in addition to the already saved
> > ones? With that info I could update the patch so it's acceptable for everyone.
> 
> I think you need to save all of FPSCR, FPEXC, FPINST, FPINST2. The
> information in the latter 2 registers is only relevant if corresponding
> bits in FPEXC are set (like EX and FP2V). A signal handler could decide
> whether to use them or not.

Thanks for the info, I'll try to update my patches based on this.

--Imre

  reply	other threads:[~2010-01-13 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c70d85c1a0b20b5f227f34b32db674c7b362d72d.1242734510.git.imre.deak@nokia.com>
     [not found] ` <201001041615.26490.siarhei.siamashka@nokia.com>
     [not found]   ` <20100104142549.GF9107@n2100.arm.linux.org.uk>
2010-01-04 15:18     ` [RFC PATCH 2/2] ARM: VFP: preserve the HW context when calling signal handlers Siarhei Siamashka
2010-01-06 17:47       ` Imre Deak
2010-01-13 15:49         ` [RFC PATCH 2/2] ARM: VFP: preserve the HW context when callingsignal handlers Catalin Marinas
2010-01-13 16:01           ` Imre Deak [this message]
     [not found] ` <20090613164035.GE16220@shareable.org>
     [not found]   ` <20090613170406.GA6926@n2100.arm.linux.org.uk>
2010-01-04 15:36     ` [RFC PATCH 2/2] ARM: VFP: preserve the HW context when calling signal handlers Siarhei Siamashka

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=20100113160142.GB11726@localhost \
    --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 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.