From: Luiz Capitulino <lcapitulino@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, riel@redhat.com,
rafael.j.wysocki@intel.com, mingo@kernel.org,
Linux PM list <linux-pm@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC 0/3] sched/idle: run-time support for setting idle polling
Date: Wed, 30 Sep 2015 14:01:43 -0400 [thread overview]
Message-ID: <20150930140143.7b187451@redhat.com> (raw)
In-Reply-To: <20150930172713.GV3816@twins.programming.kicks-ass.net>
On Wed, 30 Sep 2015 19:27:13 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Sep 30, 2015 at 01:16:10PM -0400, Luiz Capitulino wrote:
> > On Wed, 30 Sep 2015 17:48:35 +0200
> > Peter Zijlstra <peterz@infradead.org> wrote:
>
> > > Ideally every cpuidle driver would get 'polling' as a
> > > default state and the QoS constraints might select it if nothing else
> > > matches.
> >
> > So, I didn't know we had support for polling from the idle
> > thread via cpuidle. This solves the first part of the problem.
>
> I'm not sure we do; I'm saying that's what we should do ;-)
Yeah, but I think it's done already. Although I haven't tested it yet:
[root@localhost ~]# cat /sys/devices/system/cpu/cpu0/cpuidle/state0/name
POLL
[root@localhost ~]#
This is installed by drivers/cpuidle/driver.c:poll_idle_init().
prev parent reply other threads:[~2015-09-30 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1442954062-28578-1-git-send-email-lcapitulino@redhat.com>
2015-09-23 1:17 ` [RFC 0/3] sched/idle: run-time support for setting idle polling Rafael J. Wysocki
2015-09-23 13:21 ` Luiz Capitulino
2015-09-30 15:48 ` Peter Zijlstra
2015-09-30 17:16 ` Luiz Capitulino
2015-09-30 17:27 ` Peter Zijlstra
2015-09-30 18:01 ` Luiz Capitulino [this message]
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=20150930140143.7b187451@redhat.com \
--to=lcapitulino@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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).