public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: src ./ChangeLog ./tapsets.cxx testsuite/Change ... Date: Sat, 26 Jan 2008 20:22:00 -0000 [thread overview] Message-ID: <20080126202209.23651.qmail@sourceware.org> (raw) CVSROOT: /cvs/systemtap Module name: src Changes by: fche@sourceware.org 2008-01-26 20:22:09 Modified files: . : ChangeLog tapsets.cxx testsuite : ChangeLog Added files: testsuite/semko: maxactive04.stp maxactive05.stp Log message: PR5673: reduce total size of generated .ko's from wildly wildcarded scripts 2008-01-26 Frank Ch. Eigler <fche@elastic.org> PR 5673. * tapsets.cxx (dwarf_derived_probe_group): Split stap_dwarf_probes[] into bss-carried kprobes structs. Tune embedded strings for minimizing relocation-vs-fixed-buffer wastage. * tapsets.cxx (dwarf_derived_probe): Impose .maxactive() limits. 2008-01-26 Frank Ch. Eigler <fche@elastic.org> PR 5673. * testsuite/parseko/maxactive{04,05}.stp: New tests. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/ChangeLog.diff?cvsroot=systemtap&r1=1.761&r2=1.762 http://sourceware.org/cgi-bin/cvsweb.cgi/src/tapsets.cxx.diff?cvsroot=systemtap&r1=1.235&r2=1.236 http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/ChangeLog.diff?cvsroot=systemtap&r1=1.196&r2=1.197 http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/semko/maxactive04.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/semko/maxactive05.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
next reply other threads:[~2008-01-26 20:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-26 20:22 fche [this message] -- strict thread matches above, loose matches on Subject: below -- 2007-09-06 18:08 hiramatu
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=20080126202209.23651.qmail@sourceware.org \ --to=fche@sourceware.org \ --cc=systemtap-cvs@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: linkBe 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).