qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gadre Nayan <gadrenayan@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] Libvirt add ftrace option
Date: Tue, 16 Aug 2016 15:35:09 +0100	[thread overview]
Message-ID: <20160816143509.GK25115@redhat.com> (raw)
In-Reply-To: <CAKJ7aR6KBTZ4=3jUSw7A8BE=QvKSpobsi3faJBQpkaOKD=zdXQ@mail.gmail.com>

On Tue, Aug 16, 2016 at 07:54:50PM +0530, Gadre Nayan wrote:
> Hi,
> 
> I have setup the merging of traces from Guest QEMU and Host using the
> TSC_OFFSET. So I would like to work with ftrace backend of QEMU. So
> how can I add this option in libvirt tools to enable ftrace backends
> with my custom qemu source built using --enable-trace-backends=ftrace.
> 
> I would have to make changes to virt-install python script in the
> virt-manager tools for starters ( to parse the trace options :). Where
> else ?

The need to modify the downstream tools to statically configure
tracing parameters for VMs is exactly why we don't want to support
things like ftrace in libvirt and recommend use of fully dymamic
tracing like dtrace/systemd/ltt-ust.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-08-16 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 14:03 [Qemu-devel] Libvirt add ftrace option Gadre Nayan
2016-08-16 14:18 ` Daniel P. Berrange
2016-08-16 14:24   ` Gadre Nayan
2016-08-16 14:35     ` Daniel P. Berrange [this message]
2016-08-17  4:13       ` Gadre Nayan
2016-08-17  8:56         ` Daniel P. Berrange

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=20160816143509.GK25115@redhat.com \
    --to=berrange@redhat.com \
    --cc=gadrenayan@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.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 NNTP newsgroup(s).