[Bug 51996] aarch64: NtGetContextThread/NtSetContextThread on another thread ignores FPU state due to buggy SIGUSR1 handler

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51996

Zebediah Figura <z.figura12 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |z.figura12 at gmail.com

--- Comment #2 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Jinoh Kang from comment #1)
> IMHO a dedicated signal handler on SIGUSR2 to restore full context (used in
> NtContinue etc.) seems excessive to me. Is there any state on AArch64 that
> cannot be restored in user mode and may only be modified kernel side?

Yes. As far as we're aware, it's impossible to restore the *whole* context
simultaneously, without using privileged instructions like ERET. You need to
scratch a register to set the instruction pointer.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.