From: John Kacur <jkacur@redhat.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Punit Agrawal <punitagrawal@gmail.com>,
Clark Williams <williams@redhat.com>,
Pierre FICHEUX <pierre.ficheux@smile.fr>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Strange problem with PREEMPT_RT
Date: Thu, 30 Sep 2021 10:25:04 -0400 (EDT) [thread overview]
Message-ID: <6034cc70-fb69-d9d-ce31-673d4d42adc@redhat.com> (raw)
In-Reply-To: <87v92i9o5t.fsf@jogness.linutronix.de>
On Thu, 30 Sep 2021, John Ogness wrote:
> On 2021-09-30, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> >> With hackbench, the system is sufficiently busy to avoid the going
> >> into idle.
> >
> > Not just that. cyclictest's usage of /dev/cpu_dma_latency has the side
> > effect that it may disable some of the PM stuff in the system.
> > So your system appears good but then when cyclictest is gone, the
> > numbers go up.
> >
> > Maybe we should drop that so we observe a system without altering its
> > behaviour?
>
> +1
>
> Developers wanting to explicitly cause this behavior can use --latency=
> to enable it. Having it on as a default is misleading.
Where does this "--latency=" option apply to?
John
next prev parent reply other threads:[~2021-09-30 14:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 16:40 Strange problem with PREEMPT_RT Pierre FICHEUX
2021-09-30 0:13 ` Punit Agrawal
2021-09-30 8:21 ` Pierre FICHEUX
2021-09-30 13:17 ` Luis Goncalves
2021-09-30 13:18 ` Sebastian Andrzej Siewior
2021-09-30 13:23 ` Sebastian Andrzej Siewior
2021-09-30 13:26 ` Pierre FICHEUX
2021-09-30 13:51 ` Sebastian Andrzej Siewior
2021-09-30 14:31 ` Pierre FICHEUX
2021-09-30 23:40 ` Punit Agrawal
2021-10-03 11:11 ` Jack Winch
2021-10-04 12:54 ` John Kacur
2021-10-18 9:12 ` Sebastian Andrzej Siewior
2021-09-30 13:41 ` John Ogness
2021-09-30 14:25 ` John Kacur [this message]
2021-09-30 15:02 ` John Ogness
2021-09-30 15:49 ` Sebastian Andrzej Siewior
2021-09-30 16:16 ` John Kacur
2021-09-30 23:22 ` Punit Agrawal
2021-09-30 14:59 ` John Kacur
2021-09-30 23:01 ` Punit Agrawal
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=6034cc70-fb69-d9d-ce31-673d4d42adc@redhat.com \
--to=jkacur@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=pierre.ficheux@smile.fr \
--cc=punitagrawal@gmail.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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