From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: busy loops in kernel
Date: Wed, 18 Jan 2012 07:39:22 +0000 [thread overview]
Message-ID: <20120118073922.GH3294@mwanda> (raw)
In-Reply-To: <CAFTXME+fNAqqZjO4oRmbwt2cFbaDgbLW9gg94tzJvF4bwy7DtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
On Wed, Jan 18, 2012 at 10:37:30AM +0300, Dan Carpenter wrote:
> Interesting stuff. You guys are doing static analysis on the .o
> files? I'm looking at the first line.
>
> ticks 25 What does the ticks count mean?
I figured it out. Ticks is the number of infinite loops found in
the .o file.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-18 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 4:15 busy loops in kernel Asim
2012-01-18 4:55 ` Greg Dietsche
2012-01-18 7:37 ` Dan Carpenter
2012-01-18 7:39 ` Dan Carpenter [this message]
2012-01-18 17:45 ` Asim
2012-01-18 17:48 ` Asim
2012-01-21 17:33 ` Asim
2012-01-21 19:04 ` Julia Lawall
2012-01-21 20:46 ` Asim
2012-01-21 20:50 ` Julia Lawall
2012-01-21 22:32 ` Asim
2012-01-22 6:09 ` Julia Lawall
2012-01-22 12:17 ` Bernd Petrovitsch
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=20120118073922.GH3294@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
/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.