From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/11671] Allocate __stp_tf_vma_entry dynamically
Date: Fri, 09 Dec 2011 16:58:00 -0000 [thread overview]
Message-ID: <bug-11671-6586-D0utviPYnn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11671-6586@http.sourceware.org/bugzilla/>
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.
next parent reply other threads:[~2011-12-09 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11671-6586@http.sourceware.org/bugzilla/>
2011-12-09 16:58 ` mjw at redhat dot com [this message]
[not found] <bug-11671-1110@http.sourceware.org/bugzilla/>
2010-10-17 21:49 ` jan.kratochvil at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11671-6586-D0utviPYnn@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).