From: francis.giraldeau@gmail.com (Francis Giraldeau)
Subject: [lttng-dev] Sync instrumentation to today's linux 3.8
Date: Fri, 25 Jan 2013 17:10:26 -0500 [thread overview]
Message-ID: <CAC6yHM5Vd8zZc-1nmFuVfuxiH3yUwA+mNUd6cejZFfvFb4kURw@mail.gmail.com> (raw)
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?
Cheers,
Francis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20130125/35d5d659/attachment.html>
next reply other threads:[~2013-01-25 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 22:10 Francis Giraldeau [this message]
2013-01-28 16:15 ` Mathieu Desnoyers
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=CAC6yHM5Vd8zZc-1nmFuVfuxiH3yUwA+mNUd6cejZFfvFb4kURw@mail.gmail.com \
--to=francis.giraldeau@gmail.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