From: Julia Lawall <julia.lawall@lip6.fr>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Remington Furman <remicles2@gmail.com>,
backports@vger.kernel.org, cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Parse error with genl-const.cocci
Date: Fri, 1 Dec 2017 19:57:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1712011954500.2825@hadrien> (raw)
In-Reply-To: <1512151378.25588.20.camel@sipsolutions.net>
On Fri, 1 Dec 2017, Johannes Berg wrote:
> On Fri, 2017-12-01 at 09:57 -0800, Remington Furman wrote:
> >
> > Ok, I've rebuilt with 1.0.4, and it applied genl-const.cocci just
> > fine. But, later on my CPU was held at 100% for 29 minutes:
>
> Yeah, known issue. Give it more time - that particular patch is
> *really* slow. Yes, more than 29 minutes, on my system as well.
>
> What I can recommend is that you remove things from copy-list that you
> don't care about, e.g. bluetooth drivers if you don't need them,
> certain wifi drivers you don't need, etc. (before running gentree.py)
You can also set a timeout, for example --timeout 120 (120 seconds). It
will report on the files that timed out and you can check on them
manually. Some other useful options are:
--profile: see how long it spends in each rule or various parts of the
OCaml code
--show-trying: see what function it is working on
--debug see what rule and with what inputs it is working on
It may work better to put --debug before the others.
julia
>
> johannes
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-12-01 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 5:43 Parse error with genl-const.cocci Remington Furman
2017-12-01 8:27 ` Johannes Berg
2017-12-01 9:18 ` [Cocci] " Julia Lawall
2017-12-01 9:29 ` Johannes Berg
2017-12-01 10:00 ` Julia Lawall
2017-12-12 15:19 ` Remington Furman
2017-12-14 15:16 ` Julia Lawall
2017-12-19 9:41 ` Johannes Berg
2018-06-25 20:33 ` Johannes Berg
2017-12-01 17:57 ` Remington Furman
2017-12-01 18:02 ` Johannes Berg
2017-12-01 18:09 ` Remington Furman
2017-12-01 23:48 ` Remington Furman
2017-12-02 7:47 ` Johannes Berg
2017-12-01 18:57 ` Julia Lawall [this message]
2017-12-01 19:39 ` [Cocci] " Johannes Berg
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=alpine.DEB.2.20.1712011954500.2825@hadrien \
--to=julia.lawall@lip6.fr \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=johannes@sipsolutions.net \
--cc=remicles2@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).