[Bug translator/10796] thread-specific globals

[Bug translator/10796] thread-specific globals

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=10796

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fche at redhat dot com
         Resolution|---                         |WONTFIX

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
I SWAG that performance improvement from a second data structure that still
needs some locking and additional probes to maintain is unlikely to be large.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug translator/10796] thread-specific globals

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=10796

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|WONTFIX                     |---
     Ever confirmed|1                           |0

--- Comment #4 from Frank Ch. Eigler <fche at redhat dot com> ---
unSWAGing; we are encountering some high-performance-required stap jobs, where
the absence of this facility is a problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug translator/10796] thread-specific globals

[jkenisto at us dot ibm dot com]

------- Additional Comments From jkenisto at us dot ibm dot com  2009-10-26 16:02 -------
(In reply to comment #1)
> If we get this such that it performs better than plain "array[tid()]"
> mechanisms, then we should port the .return $target saving to use this feature.

If you're going to revise that feature, consider using
kretprobe_instance->data[] to store such data between call and return.  That's
what it was designed for.  See PR #5916 and section 1.3.2 of
Documentation/kprobes.txt.



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10796

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug translator/10796] thread-specific globals

[jistone at redhat dot com]

------- Additional Comments From jistone at redhat dot com  2009-10-23 23:42 -------
If we get this such that it performs better than plain "array[tid()]"
mechanisms, then we should port the .return $target saving to use this feature.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10796

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.