From: Pierre FICHEUX <pierre.ficheux@smile.fr>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Punit Agrawal <punitagrawal@gmail.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Strange problem with PREEMPT_RT
Date: Thu, 30 Sep 2021 16:31:25 +0200 [thread overview]
Message-ID: <CAFc1U0sYdJQWkeLgPjiR1Y1CnafV22zgS4AW0Yf6+h7CO03u+g@mail.gmail.com> (raw)
In-Reply-To: <20210930135145.mdlzzwp64yykixhx@linutronix.de>
# cpupower -c all idle-info
CPUidle driver: none
CPUidle governor: menu
analyzing CPU 0:
CPU 0: No idle states
...
same for all cpus.
Le jeu. 30 sept. 2021 à 15:51, Sebastian Andrzej Siewior
<bigeasy@linutronix.de> a écrit :
>
> On 2021-09-30 15:26:32 [+0200], Pierre FICHEUX wrote:
> > I've just copied the set_latency_target() of cyclcitest.c to my code
> > but I got the same behaviour.
>
> What happens if you disable idle states > C1 with cpupower?
>
> Sebastian
--
Pierre FICHEUX -/- CTO Smile ECS, France -\- pierre.ficheux@smile.fr
http://www.smile.fr
https://smile.eu/fr/offres/embarque-iot
I would love to change the world, but they won't give me the source code
next prev parent reply other threads:[~2021-09-30 14:32 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 [this message]
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
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=CAFc1U0sYdJQWkeLgPjiR1Y1CnafV22zgS4AW0Yf6+h7CO03u+g@mail.gmail.com \
--to=pierre.ficheux@smile.fr \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--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 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.