public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest
Date: Wed, 14 Jun 2017 13:53:13 +0900	[thread overview]
Message-ID: <20170614135313.04e2f0b0596bbb9057ce557b@kernel.org> (raw)
In-Reply-To: <20170614111217.46825d2caf31eae9edb72162@kernel.org>

On Wed, 14 Jun 2017 11:12:17 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Hi Shuah and Steve,
> 
> Sorry for replying so late...
> 
> On Thu, 8 Jun 2017 17:51:44 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > On Thu, 8 Jun 2017 15:44:08 -0600
> > Shuah Khan <shuahkh@osg.samsung.com> wrote:
> > 
> > > > Also, did you see my reply about having the right config? You have
> > > > HIST_TRIGGERS undefined but yet the histogram trigger tests all pass in
> > > > your report.  
> > > 
> > > I did see that one. Didn't get a chance to look at that yet. Do you expect
> > > the tests to be skipped in this case? Could it be that tests aren't run?
> > > I will look at this and let you know what I find on my test system.
> > 
> > Your first email showed that they passed, which would be hard to do
> > since the feature is not even enabled. ftracetest is very much set up
> > to look at the existing pseudo files to determine if a feature exists
> > or not, and if it does not, it returns "UNSUPPORTED". If it returned
> > PASSED when the feature is not enabled, that would be a big time bug in
> > the test.
> 
> As far as I can see, what Steve you saw was my result on the 4.9 stable
> kernel, which had been compiled with fully ftrace enabled :).
> 
> > > 
> > > > 
> > > > One more thing, is this 100% reproducible. That is, does it always fail?
> > > >   
> > > Failed the two times I tried.
> 
> I've also tried to test the latest linus tree with this series with Shuah's
> config on qemu, and could not reproduced it. (I attached the log)
> As you can see, with Shuah's config, histogram tests are marked UNSUPPORTED.
> 
> Of course, that is 4.12.0-rc5+ and kconfig is a bit tweaked(attached).
> I'll try kselftest tree too.

I've tried it on linux-kselftest/next, but not able to reproduce it...

Thank you,

> 
> Thank you,
> 
> > 
> > Great to hear. I like reproducibility :-)
> > 
> > -- Steve
> > 
> 
> 
> -- 
> Masami Hiramatsu <mhiramat@kernel.org>


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2017-06-14  4:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  6:02 [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest Masami Hiramatsu
2017-05-23  6:03 ` [PATCH 1/7] selftests/ftrace: Skip full-glob-matching filter test on older kernel Masami Hiramatsu
2017-05-23  6:04 ` [PATCH 2/7] selftests/ftrace: Reduce trace buffer checking overhead Masami Hiramatsu
2017-05-23  6:05 ` [PATCH 3/7] ftrace/kprobes: selftests: Check kretprobe maxactive is supported Masami Hiramatsu
2017-05-23  6:06 ` [PATCH 4/7] selftests/ftrace: Reset ftrace filter on older kernel Masami Hiramatsu
2017-05-23  6:07 ` [PATCH 5/7] selftests/ftrace: Add instance indication in test log Masami Hiramatsu
2017-05-23  6:09 ` [PATCH 6/7] selftests/ftrace: Use top-level available_filter_function Masami Hiramatsu
2017-05-23  6:10 ` [PATCH 7/7] selftests/ftrace: Return unsupported if it detects older kernel Masami Hiramatsu
2017-06-07 22:42 ` [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest Shuah Khan
2017-06-07 22:56   ` Steven Rostedt
2017-06-07 23:01     ` Shuah Khan
2017-06-08 17:37       ` Steven Rostedt
2017-06-08 20:06         ` Shuah Khan
2017-06-08 21:08           ` Steven Rostedt
2017-06-08 21:14             ` Shuah Khan
2017-06-08 21:26               ` Steven Rostedt
2017-06-08 21:33                 ` Shuah Khan
2017-06-08 21:39                   ` Steven Rostedt
2017-06-08 21:44                     ` Shuah Khan
2017-06-08 21:51                       ` Steven Rostedt
2017-06-14  2:12                         ` Masami Hiramatsu
2017-06-14  4:53                           ` Masami Hiramatsu [this message]
2017-06-14 14:17                             ` Shuah Khan
2017-06-30 14:18                               ` Shuah Khan
2017-06-08 21:11       ` Steven Rostedt

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=20170614135313.04e2f0b0596bbb9057ce557b@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=shuahkh@osg.samsung.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