Re: [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers

>>> Andi Kleen <[email protected]> 10.11.05 14:23:55 >>>
>On Wednesday 09 November 2005 15:14, Jan Beulich wrote:
>> This adds static information about the code regions where the stack
>> pointer cannot be relied upon. Kernel debuggers may then use this
>> information to determine which stack to switch to when having a need
>> to switch off of namely the NMI stack.
>
>Hmm - can't this be expressed in CFI somehow? 

Probably one could use .cfi_undefined, but the code needing the information (switching away from the NMI stack) shouldn't have to go through parsing the .eh_frame section contents in order to obtain that information.

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 18/39] NLKD/x86-64 - INT1/INT3 handling changes
    • From: "Jan Beulich" <[email protected]>
  • [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers
    • From: "Jan Beulich" <[email protected]>
  • Re: [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers
    • From: Andi Kleen <[email protected]>

• Prev by Date: [PATCH] blk: elv_latter/former_request update
• Next by Date: Re: [PATCH 18/39] NLKD/x86-64 - INT1/INT3 handling changes
• Previous by thread: Re: [PATCH 19/39] NLKD/x86-64 - stack-pointer-invalid markers
• Next by thread: Re: [PATCH 18/39] NLKD/x86-64 - INT1/INT3 handling changes
• 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]