Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Sync instrumentation to today's linux 3.8
Date: Mon, 28 Jan 2013 11:15:55 -0500	[thread overview]
Message-ID: <20130128161555.GA23427@Krystal> (raw)
In-Reply-To: <CAC6yHM5Vd8zZc-1nmFuVfuxiH3yUwA+mNUd6cejZFfvFb4kURw@mail.gmail.com>

* Francis Giraldeau (francis.giraldeau at gmail.com) wrote:
> To prepare instrumentation for the next linux release, here is the ticket I
> was working on. It's mostly straight forward.
> 
> http://redmine.dorsal.polymtl.ca/issues/431
> 
> There is one issue with ext4 includes. I had to copy fs/ext4/ext4.h and
> ext4_extent.h for the function ext4_ext_get_actual_len(). I added them to
> instrumentation/mainline/fs/ext4 directory. I'm not sure if it's the best
> solution.
> 
> Still testing to do, thought. BTW, is there a test setup for regression? I
> would like to verify that it doesn't break any supported kernel and I don't
> have the required setup.
> 
> With this, maybe lttng-modules 2.1 can target linux 3.8?

Please send the patch by email.

3.8 is still in rc stage. Removing ext4_ext_get_actual_len() seems like
a bad move from upstream Linux if it is needed in the instrumentation
headers. This should be fixed upstream rather than duplicated within our
own code.

Thanks,

Mathieu

> 
> Cheers,
> 
> Francis

> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2013-01-28 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 22:10 Francis Giraldeau
2013-01-28 16:15 ` Mathieu Desnoyers [this message]
2013-01-28 16:19   ` Mathieu Desnoyers

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=20130128161555.GA23427@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    /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