This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [Bug translator/1276] support more timer varieties
- From: Roland McGrath <roland at redhat dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>, systemtap at sources dot redhat dot com
- Date: Tue, 6 Dec 2005 10:47:33 -0800 (PST)
- Subject: Re: [Bug translator/1276] support more timer varieties
> Places that come to mind are those routines that change the "current"
> pointers, and routines (if any) involved in computing the "current"
> macro, to test for reentrancy problems.
The macro is inlined into a little bit of assembly. The pointer is stored
on the stack and never changed (you just switch stacks). The only current
pointer that gets changed is the one on interrupt stacks, which is set up
before switching to the interrupt stack. So the closest to "dangerous"
places would be inside context switching and inside interrupt handling.