Re: [PATCH 20/39] NLKD/x86-64 - switch_to() floating point adjustment

>>> Andi Kleen <[email protected]> 10.11.05 14:24:53 >>>
>On Wednesday 09 November 2005 15:15, Jan Beulich wrote:
>> Touching of the floating point state in a kernel debugger must be
>> NMI-safe, specifically math_state_restore() must be able to deal with
>> being called out of an NMI context. In order to do that reliably, the
>> context switch code must take care to not leave a window open where
>> the current task's TS_USEDFPU flag and CR0.TS could get out of sync.
>
>Didn't we agree earlier on moving unlazy_fpu() down instead? 

I wasn't sure about that, and hence I submitted it the way I had coded it.

Jan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 0/39] NLKD - Novell Linux Kernel Debugger
    • From: "Jan Beulich" <[email protected]>
  • [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers
    • From: "Jan Beulich" <[email protected]>
  • [PATCH 20/39] NLKD/x86-64 - switch_to() floating point adjustment
    • From: "Jan Beulich" <[email protected]>
  • Re: [PATCH 20/39] NLKD/x86-64 - switch_to() floating point adjustment
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: [PATCH 18/39] NLKD/x86-64 - INT1/INT3 handling changes
• Next by Date: Re: Nick's core remove PageReserved broke vmware...
• Previous by thread: Re: [PATCH 20/39] NLKD/x86-64 - switch_to() floating point adjustment
• Next by thread: Re: [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]