All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Bhavesh Davda <bhavesh@vmware.com>
Cc: linux-rt-users@vger.kernel.org, frank rowand <frank.rowand@am.sony.com>
Subject: Re: [PATCH RT-TESTS] cyclictest: histogram overflow instance tracking
Date: Tue, 13 Nov 2012 18:53:29 -0500 (EST)	[thread overview]
Message-ID: <880517104.255767.1352850809690.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1982684838.49197680.1352850501878.JavaMail.root@vmware.com>



----- Original Message -----
> Hello Frank,
> 
> I apologize I didn't have a chance to review your proposed
> modifications to my patch.
> 
> I had looked at your proposal to introduce a '-g' option (for lack of
> a better letter) instead of piggy-backing on the '-h' option, and I
> completely agree with that approach.
> 
> It would be very handy to specify, for example, '-h 50 -g 1000' to
> capture and print the 1000 outliers beyond 50 us to get a good sense
> of any patterns hidden in the outliers.
> 
> If John has already accepted my proposed patches, do you want to
> propose your changes on top of that as a separate patch now?

Please pull the git tree, have a look at what I put in, and then think about
Frank's suggestions. Make sure you are "proactive" - (oh God, thinking about 
a Simpson's episode now), and see what you can do with it, instead of just
waiting for Frank to tell you his opinions.

Thanks!

> 
> Thanks for your review, and your excellent suggestion to make this
> feature even more useful.
> 
> --
> Bhavesh Davda
> 
> ----- Original Message -----
> > From: "Frank Rowand" <frank.rowand@am.sony.com>
> > To: "Bhavesh Davda" <bhavesh@vmware.com>, "John Kacur"
> > <jkacur@redhat.com>
> > Cc: linux-rt-users@vger.kernel.org
> > Sent: Tuesday, November 13, 2012 3:41:20 PM
> > Subject: Re: [PATCH RT-TESTS] cyclictest: histogram overflow
> > instance tracking
> > 
> > On 10/25/12 14:36, Frank Rowand wrote:
> > > On 10/16/12 10:02, Bhavesh Davda wrote:
> > >> From: Bhavesh Davda <bhavesh@vmware.com>
> > >>
> > >> Add feature to cyclictest histogram mode to track cycle counts
> > >> every time a
> > >> sample overflows the histogram limit. This should help identify
> > >> if
> > >> there is a
> > >> timing pattern to jitters in cyclictest runs.
> > >>
> > >> Example output (with -h 10):
> > >>  ...
> > >>  Histogram Overflows: 00001 00007 00000 00009 00004 00007 00000
> > >>  00001
> > >>  Histogram Overflow at cycle number:
> > >>  Thread 0: 09964
> > >>  Thread 1: 00000 00004 00006 00008 00010 09962 11594
> > >>  Thread 2:
> > >>  Thread 3: 01169 04698 06782 09033 10299 11561 21517 28734 29532
> > >>  Thread 4: 11574 11580 11583 11586
> > >>  Thread 5: 00020 09448 13954 14954 18954 20587 24973
> > >>  Thread 6:
> > >>  Thread 7: 18950
> > >>  ...
> > >>
> > >> Signed-off-by: Bhavesh Davda <bhavesh@vmware.com>
> > > 
> > > My comments up to "--" are not meant to be part of the header of
> > > the
> > > following patch.
> > > 
> > > I am including the following patch as my review of the patch I am
> > > replying to.  If the following patch is incorporated into the
> > > reviewed patch, then you can add my:
> > > 
> > >   Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
> > >   Tested-by: Frank Rowand <frank.rowand@am.sony.com>
> > > 
> > > to the combined patch.
> > 
> > < snip >
> > 
> > Bhavesh,
> > 
> > I never saw I reply to my suggestions.  Unfortunately John took my
> > reviewed-by for your white space patch and applied it to your
> > "cyclictest: histogram overflow instance tracking" patch, without
> > my suggestions, and released it in v0.85 rt-tests.
> > 
> > So...., any thoughts about the suggestions in the email that
> > this one is responding to?  And also any thoughts about my
> > second email in the series (I'll forward that one again to
> > you).
> > 
> > -Frank
> > 
> > 
> 

  reply	other threads:[~2012-11-13 23:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 17:02 [PATCH RT-TESTS] cyclictest: histogram overflow instance tracking Bhavesh Davda
2012-10-23  1:16 ` Frank Rowand
2012-10-23  1:41   ` Frank Rowand
2012-10-23 18:59     ` Bhavesh Davda
2012-10-23 19:25       ` John Kacur
2012-10-23 19:55         ` Frank Rowand
2012-10-23 19:59           ` Sven-Thorsten Dietrich
2012-10-25 21:36 ` Frank Rowand
2012-10-25 22:05   ` Frank Rowand
2012-11-13 23:41     ` Frank Rowand
2012-11-13 23:41   ` Frank Rowand
2012-11-13 23:48     ` Bhavesh Davda
2012-11-13 23:53       ` John Kacur [this message]
2012-11-14  0:02         ` Frank Rowand
2012-11-14  0:03         ` Bhavesh Davda
2012-11-14  0:04           ` Bhavesh Davda
2012-11-14  0:09             ` John Kacur
2012-11-14  0:17               ` Bhavesh Davda
2012-11-14  0:19                 ` 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=880517104.255767.1352850809690.JavaMail.root@redhat.com \
    --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 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.