This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/11671] Allocate __stp_tf_vma_entry dynamically


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

Mark Wielaard <mjw at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-12-09 15:08:14 UTC ---
commit c2537ee6d68b2358e8f74cc5413772915e5742d6
Author: Mark Wielaard <mjw@redhat.com>
Date:   Fri Dec 9 10:46:20 2011 +0100

    PR11671 Allocate __stp_tf_vma_entry dynamically.

    Get rid of TASK_FINDER_VMA_ENTRY_ITEMS and __stp_tf_vma_free_list_items
    array list completely. All __stp_tf_vma_entry are allocated dynamically
    now. This is possible since stap_add_vma_map_info() is only called
    through the task_finder from a user context.

    There is no more fixed maximum number of VMA pages that will be tracked
    at runtime. This reduces memory use for those scripts that don't need any,
    or only limited target process VMA tracking and allows easier system
    wide probes inspecting shared library variables and/or user backtraces.
    stap will now silently ignore -DTASK_FINDER_VMA_ENTRY_ITEMS.

Plus some follow up commits to fix some corner cases (3dde67, 972ea1 and
7fbefb)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]