From: John Kacur <jkacur@redhat.com>
To: Frank Rowand <frank.rowand@am.sony.com>
Cc: John Kacur <jkacur@redhat.com>,
bhavesh@vmware.com, linux-rt-users@vger.kernel.org
Subject: Re: cyclictest overflow instance tracking -- irc continued
Date: Tue, 16 Oct 2012 12:56:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1210161251190.3137@tycho> (raw)
In-Reply-To: <507CAF63.7080703@am.sony.com>
On Mon, 15 Oct 2012, Frank Rowand wrote:
Thanks for your further review Frank. Bhavesh - I think the right thing to
do here, is to ask you to respin your patch. Can you make sure you are
applying and testing against the latest. (0.84). Also, please put any
white space clean-ups in a separate patch to make it easier to read the
important patch. Oh, and send these in a new thread. If people could
preface their mail with [PATCH RT-TESTS] that would also help.
Thank You.
John Kacur
>
> 16:13 jkacur frowand_bot: would you like a Reviewed-by: credit for the cyclictest histogram overflow instance tracking patch?
> 16:13 jkacur can I just add that or is the reviewer supposed to request it?
> 17:02 frowand jkacur: sure, you can add my reviewed-by (at least for the first version, i didn't really look at the second version in detail)
>
> For the first version, it was a drive-by review, just obvious stuff.
>
> Now that I look at the second version a little closer (but still not in detail), it
> looks like he did some white space clean up, which should probably be a separate patch.
>
> It also looks like he created his patch against an old version of cyclictest,
> because he has:
>
> @@ -154,6 +155,7 @@ struct thread_stat {
> long redmax;
> long cycleofmax;
> long hist_overflow;
> + long num_outliers;
> };
>
>
> but struct thread_stat currently has another field:
>
> long redmax;
> long cycleofmax;
> long hist_overflow;
> unsigned long now_after_next;
> };
>
> and also the line numbers in the patch are off.
>
> > from #linux-rt:
> >
> > 17:07 jkacur frowand: hmm, the patch doesn't appear to be working for me
> > 17:07 jkacur I'll look at it more tomorrow
> > 17:08 jkacur Thread 0: 18446744073709551615 00000 00001 00002 00003 00004 00005 00006 00007 00008 # 02841 others
> > 17:08 jkacur is an example of broken output
>
> 18446744073709551615 is 0xffffffffffffffff (or -1LL)
>
> It looks like in timerthread(), the line:
>
> + stat->outliers[stat->num_outliers++] = stat->cycles - 1;
>
> is picking up stat->cycles == zero. Looking at the current version of cyclictest, for the
> first event cycles should already be one at this point. But given that the line numbers in
> the patch are not consistent with the current cyclictest, I don't know where that chunk
> actually got inserted.
>
>
> -Frank
>
>
next parent reply other threads:[~2012-10-16 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <507CAF63.7080703@am.sony.com>
2012-10-16 10:56 ` John Kacur [this message]
2012-10-16 16:11 ` cyclictest overflow instance tracking -- irc continued Bhavesh Davda
2012-10-16 16:14 ` Bhavesh Davda
2012-10-16 16:23 ` John Kacur
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.LFD.2.02.1210161251190.3137@tycho \
--to=jkacur@redhat.com \
--cc=bhavesh@vmware.com \
--cc=frank.rowand@am.sony.com \
--cc=linux-rt-users@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 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 NNTP newsgroup(s).