public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-501-g5137a7a Date: Sun, 27 Nov 2011 22:33:00 -0000 [thread overview] Message-ID: <20111127223358.12098.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 5137a7a990ef7bc27022654775ce0aa86e0e9942 (commit) via 9c910acd0eddfb8ed0df5ac1fd4569fca7e8e7c6 (commit) via 78be4756cbb64f38086f10a162ba62efaf0df22b (commit) from 3c6dd54efb6de5b4d55e073c8d5884440aece135 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 5137a7a990ef7bc27022654775ce0aa86e0e9942 Author: Frank Ch. Eigler <fche@redhat.com> Date: Sun Nov 27 17:26:44 2011 -0500 PR13354: remote_id() and remote_uri() tapset functions This little thing required changes all through the stack! * main.cxx (main): Pass the explicit --remote option index to the remote::create invocations. * remote.cxx (remote::create): Pass incoming index/uri to build staprun_r_arg. (direct::start): Use value. (stapsh::start): Use value if remote end is believed to be >= v1.7. (ssh_legacy_remote::start): Don't use value, as remote end may not know staprun -r. * remote.h (remote): New field staprun_r_arg. * runtime/transport/transport_msgs.h: Define new STP_REMOTE_ID message type. * runtime/staprun/common.c (parse_args, usage): Support new -r option. * runtime/staprun/staprun.8: Document it. * runtime/staprun/staprun.c: Pass remote id/uri to runtime via new STP_REMOTE_URI message. * runtime/staprun/staprun.h: Declare new variables. * runtime/transport/control.c (_stp_ctl_write_cmd): Accept STP_REMOTE_ID message from euid=0. * runtime/transport/transport.c (_stp_handle_remote_id): Process it. * tapset/context.stp (remote_id, remote_uri): New functions. * testsuite/systemtap.base/remote.exp: Extend to print/check those functions' values. commit 9c910acd0eddfb8ed0df5ac1fd4569fca7e8e7c6 Author: Frank Ch. Eigler <fche@redhat.com> Date: Sun Nov 27 16:07:59 2011 -0500 PR13354: NEWS blurb for remote_id() and remote_uri() commit 78be4756cbb64f38086f10a162ba62efaf0df22b Author: Frank Ch. Eigler <fche@redhat.com> Date: Sun Nov 27 15:56:32 2011 -0500 PR13354: run remote.exp by default, even if $TESTREMOTES were unset Just run it with direct: and stapsh: ----------------------------------------------------------------------- Summary of changes: NEWS | 3 ++ main.cxx | 9 +++++- remote.cxx | 47 ++++++++++++++++++++++++++-------- remote.h | 5 ++- runtime/staprun/common.c | 20 +++++++++++++- runtime/staprun/staprun.8 | 4 +++ runtime/staprun/staprun.c | 13 +++++++++ runtime/staprun/staprun.h | 2 + runtime/transport/control.c | 15 +++++++++++ runtime/transport/transport.c | 9 ++++++ runtime/transport/transport_msgs.h | 11 ++++++++ tapset/context.stp | 30 ++++++++++++++++++++++ testsuite/systemtap.base/remote.exp | 15 ++++++---- testsuite/systemtap.base/remote.stp | 2 +- 14 files changed, 161 insertions(+), 24 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-27 22:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111127223358.12098.qmail@sourceware.org \ --to=fche@sourceware.org \ --cc=systemtap-cvs@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: 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).