public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kselftest@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests: ftrace: Use md5sum to take less time of checking logs
Date: Thu, 29 Jun 2017 14:21:41 -0600	[thread overview]
Message-ID: <c83c6357-8836-7a52-84ff-fb66fa2c57f0@kernel.org> (raw)
In-Reply-To: <97100897-9bd4-11e0-79a5-faea8ba22a09@kernel.org>

On 06/28/2017 09:30 AM, Shuah Khan wrote:
> On 06/28/2017 08:59 AM, Steven Rostedt wrote:
>> On Wed, 28 Jun 2017 08:30:24 -0600
>> Shuah Khan <shuah@kernel.org> wrote:
>>
>>> On 06/28/2017 08:17 AM, Steven Rostedt wrote:
>>>> On Tue, 27 Jun 2017 19:28:32 +0900
>>>> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>>>>   
>>>>> Use md5sum so that it takes less time of checking
>>>>> trace logs update. Since busybox tail/cat takes too
>>>>> long time to read the trace log, this uses md5sum
>>>>> to check whether trace log is updated or not.  
>>>>
>>>> How much faster is md5sum? I can see this causing issues in other
>>>> environments.
>>>>
>>>> -- Steve  
>>>
>>> Sorry Steve. I pulled this into linux-ksefltest next. Are you concerned
>>> about any specific environments? I can try this out and see if it is a
>>> problem.
>>
>> Yes please. I should probably do some playing too. I would like to fix
>> that test anyway, as it is one of the longer ones as I do a lot of
>> "paranoid checks". That is, I may go overboard in testing if tracing is
>> off or not, by checking to make sure its off using different tactics.
>>
> 
> Please let me know how your trials go. I have a few things I have to get
> to before I get around to trying this patch.
> 
> thanks,
> -- Shuah

Hi Steve/Masami,

I tested this patch on my test system running 4.12-rc7 and didn't see any
problems. I am going to leave this in the linux-kselftest next for 4.13-rc1.
Please let me if you think I should drop it.

thanks,
-- Shuah

  reply	other threads:[~2017-06-29 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 10:28 [PATCH] selftests: ftrace: Use md5sum to take less time of checking logs Masami Hiramatsu
2017-06-28 14:00 ` Shuah Khan
2017-06-28 14:17 ` Steven Rostedt
2017-06-28 14:30   ` Shuah Khan
2017-06-28 14:59     ` Steven Rostedt
2017-06-28 15:30       ` Shuah Khan
2017-06-29 20:21         ` Shuah Khan [this message]
2017-06-30 14:49           ` Steven Rostedt
2017-06-30 16:53             ` Shuah Khan
2017-07-03  4:19               ` Masami Hiramatsu
2017-06-30 18:50 ` Denys Vlasenko
2017-06-30 19:03   ` 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=c83c6357-8836-7a52-84ff-fb66fa2c57f0@kernel.org \
    --to=shuah@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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