Suresh Siddha wrote:
quoted text >
> This issue of not-zeroing, is present in only 64bit kernels and for 64bit apps,
> right?
>
> 64bit app signal handling uses only rt_frame, so we can add an uc_flag for
> them and for 32bit apps, kernel was always zero'ing the reserved bits
> at the end of _fpstate.
>
> In short, for non-rt frames, they can check the reserved bits at the end
> of fpstate frame and for rt-frames (perhaps even for 32bit rt frame handling)
> apps can check for uc_flag aswell, for extended state presence. Is this
> good enough?
>
Are we sure about the "always" bit here (I suspect yes, but we may want
to double-check at least back to 2.2 or 2.4.)
Anyway, seems reasonable enough to me.
-hpa
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [RFC] x86: xsave/xrstor support, ucontext_t extensions , H. Peter Anvin , (Tue May 20, 10:59 am)