From: <Viktor.Rosendahl@bmw.de>
To: <rostedt@goodmis.org>
Cc: <mingo@redhat.com>, <joel@joelfernandes.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add the latency-collector to tools
Date: Mon, 15 Feb 2021 11:54:08 +0000 [thread overview]
Message-ID: <d68f3fca6e72e090b56d7097884ac1a3f50f4a18.camel@bmw.de> (raw)
In-Reply-To: <d2a434e4dfa012dcfdf6525f26ffaa04671fcab9.camel@bmw.de>
On Fri, 2021-02-12 at 13:16 +0100, Viktor Rosendahl wrote:
>
>
> However, for some reason I cannot reproduce the behavior now, allthough I use
> exactly the same kernel.
>
> Because humans are more often at fault than computers, I cannot deny the
> possibility that I would have misconfigured something and it was all the
> result
> of a faulty test.
>
Just a quick update: I was able to reproduce this weird behavior that I wrote
about but it turned out to be a problem with my testing.
The test was faulty because of a mistake that I had made.
Sorry for the extra noise.
best regards,
Viktor
> I will let you know if come up with a way of reproducing this behavior later.
> I
> cannot spend more time on it right now.
>
> >
next prev parent reply other threads:[~2021-02-15 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 16:43 [RFC PATCH 0/2] Tracing bursts of latencies Viktor Rosendahl
2021-01-19 16:43 ` [RFC PATCH 1/2] Use pause-on-trace with the latency tracers Viktor Rosendahl
2021-01-26 14:45 ` Steven Rostedt
2021-01-19 16:43 ` [RFC PATCH 2/2] Add the latency-collector to tools Viktor Rosendahl
2021-01-26 19:26 ` Steven Rostedt
2021-02-11 16:17 ` [PATCH] " Viktor Rosendahl
2021-02-11 19:56 ` Steven Rostedt
2021-02-12 12:16 ` Viktor.Rosendahl
2021-02-15 11:54 ` Viktor.Rosendahl [this message]
2021-02-15 14:59 ` 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=d68f3fca6e72e090b56d7097884ac1a3f50f4a18.camel@bmw.de \
--to=viktor.rosendahl@bmw.de \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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).