public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13078] investigate qemu virtio-serial channel for talking to stap-sh
Date: Tue, 24 Sep 2013 21:23:00 -0000	[thread overview]
Message-ID: <bug-13078-6586-j24KdcLNao@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13078-6586@http.sourceware.org/bugzilla/>

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

--- Comment #14 from Jonathan Lebon <jlebon at redhat dot com> ---
Much has been done since the last update. Almost everything has been
implemented. To try to keep this PR self-contained, here is roughly what has
been done:
- Added stapvirt.c (referred to previously as stap-vm)
- Added the libvirt:// scheme in remote.cxx
- Added stapvirt to the build system
- Added stapvirt.1 man page and cleared up the --remote section in stap.1
- Added sysvinit scripts for non-systemd based systems

Items that remain include:
1. Modifying systemtap.spec
   - To be discussed. E.g. we could have the 'guest' related files
(stapsh@.service, 99-stapsh.rules, sysvinit scripts) in a guest package, e.g.
'systemtap-runtime-virtguest', and the 'host' related files (which is just
stapvirt) in e.g. 'systemtap-runtime-virthost'
2. Testing the sysvinit script on a RHEL5 machine

If you'd like to take a look, I created the jlebon/cross-vm-clean branch which
contains larger diffs for your viewing pleasure. Any testing and feedback would
be welcome!

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

  parent reply	other threads:[~2013-09-24 21:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 18:21 [Bug runtime/13078] New: " fche at redhat dot com
2011-08-17  0:42 ` [Bug runtime/13078] " jistone at redhat dot com
2011-08-17  0:43 ` jistone at redhat dot com
2011-08-17 22:54 ` jistone at redhat dot com
2013-08-09 18:17 ` jlebon at redhat dot com
2013-08-20 21:40 ` jistone at redhat dot com
2013-08-21 13:29 ` fche at redhat dot com
2013-08-21 14:00 ` jlebon at redhat dot com
2013-08-21 17:32 ` jistone at redhat dot com
2013-08-26 18:07 ` jlebon at redhat dot com
2013-08-27 16:20 ` jlebon at redhat dot com
2013-08-28 16:21 ` jlebon at redhat dot com
2013-08-30 20:37 ` jlebon at redhat dot com
2013-09-04 16:18 ` jlebon at redhat dot com
2013-09-11 18:49 ` jlebon at redhat dot com
2013-09-24 21:23 ` jlebon at redhat dot com [this message]
2013-09-26 20:54 ` jlebon at redhat dot com
2013-10-18 14:26 ` jlebon 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-13078-6586-j24KdcLNao@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).