[RFC PATCH 2/2] ARM: VFP: preserve the HW context when callingsignal handlers

Catalin Marinas catalin.marinas at arm.com
Wed Jan 13 10:49:42 EST 2010


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.

-- 
Catalin




More information about the linux-arm-kernel mailing list