qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohamad Gebai <mohamad.gebai@polymtl.ca>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: lttng-dev@lists.lttng.org, "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>
Subject: Re: [Qemu-devel] [lttng-dev] [PATCH] trace: drop LTTng Userspace Tracer backend
Date: Mon, 30 Sep 2013 19:21:35 -0400	[thread overview]
Message-ID: <524A077F.6090307@polymtl.ca> (raw)
In-Reply-To: <20130926080121.GD24531@stefanha-thinkpad.redhat.com>

Hi Stefan,
Sorry for the delay but I rewrote all the patches to make the merge as
non-intrusive as possible, which wasn't the case in the patches I wrote 
for my
personal use.
I submitted them in a different thread on the mailing list.

Mohamad

On 13-09-26 04:01 AM, Stefan Hajnoczi wrote:
> On Wed, Sep 25, 2013 at 12:34:26PM -0400, Mohamad Gebai wrote:
>> I am actually using LTTng 2.x as a backend for UST to do some
>> performance analysis and latency investigation using Qemu/KVM. I
>> already have all the patches ready to replace the old 0.x interface,
>> and I am preparing them for the merge upstream.
> Excellent, I was hoping to find someone who wants to update the code.
>
> Do you need the old 0.x code for your patches or is it cleaner if we
> apply my patch to drop that first?  I guess you pretty much rewrote
> the ./configure and tracetool pieces...
>
> Stefan

  reply	other threads:[~2013-09-30 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  9:28 [Qemu-devel] [PATCH] trace: drop LTTng Userspace Tracer backend Stefan Hajnoczi
2013-09-25 16:34 ` [Qemu-devel] [lttng-dev] " Mohamad Gebai
2013-09-26  8:01   ` Stefan Hajnoczi
2013-09-30 23:21     ` Mohamad Gebai [this message]
2013-09-26  9:47 ` [Qemu-devel] " Alex Bennée

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=524A077F.6090307@polymtl.ca \
    --to=mohamad.gebai@polymtl.ca \
    --cc=alex.bennee@linaro.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=vilanova@ac.upc.edu \
    /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).