All of lore.kernel.org
 help / color / mirror / Atom feed
From: sasha.levin@oracle.com (Sasha Levin)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Out of tree instrumentation with coccinelle demo
Date: Sun, 8 May 2016 07:50:23 -0400	[thread overview]
Message-ID: <572F27FF.7040301@oracle.com> (raw)
In-Reply-To: <CAB=NE6XrFxvTJrJVVLvT-4ii-UU-tgAqB=AgzgFH20prR1DoUA@mail.gmail.com>

On 05/06/2016 07:26 PM, Luis R. Rodriguez wrote:
> Julia and I had discussed the possibility to instrument Linux code as
> an alternative to complex debugging strategies (lockdep is one) that
> often may be frowned upon due to how intrusive some changes may be or
> how much extra stuff would be needed upstream. It has been hard to
> explain the idea to folks who might make some use of it so I've gone
> ahead and created a demo tree for userspace code that shows some basic
> instrumentation ideas. You can fetch it here:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/cocci-tact.git

Thanks Luis! I haven't reviewed it yet, just Cc'ing Quentin and Vegard
who are also working on the lock poisoning patchset.


Thanks,
Sasha

  parent reply	other threads:[~2016-05-08 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 23:26 [Cocci] Out of tree instrumentation with coccinelle demo Luis R. Rodriguez
2016-05-07 10:49 ` SF Markus Elfring
2016-05-08 11:50 ` Sasha Levin [this message]
2016-05-08 19:23   ` Luis R. Rodriguez
2016-05-08 19:51     ` Julia Lawall
2016-05-09 21:10       ` Luis R. Rodriguez
2016-05-09 21:24         ` Julia Lawall
2016-05-11 20:55     ` Luis R. Rodriguez
2016-05-12  7:20       ` Julia Lawall

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=572F27FF.7040301@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=cocci@systeme.lip6.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.