From: "Mansoor, Illyas" <illyas.mansoor@intel.com>
To: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, X86 <x86@kernel.org>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Matthew Garrett <matthew.garrett@nebula.com>,
Tejun Heo <tj@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Rudramuni, Vishwesh M" <vishwesh.m.rudramuni@intel.com>,
"richard@nod.at" <richard@nod.at>,
"josh@joshtriplett.org" <josh@joshtriplett.org>,
"Kumar P, Mahesh" <mahesh.kumar.p@intel.com>,
"Sil, Dyut K" <dyut.k.sil@intel.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: RE: [PATCH] x86: fix idle notifier not being called in CONFIG_X86_32
Date: Wed, 6 Mar 2013 10:56:12 +0000 [thread overview]
Message-ID: <810586B7581CC8469141DADEBC37191224F773F0@BGSMSX102.gar.corp.intel.com> (raw)
In-Reply-To: <20130306103627.GC16827@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
> -----Original Message-----
> From: Ingo Molnar [mailto:mingo.kernel.org@gmail.com] On Behalf Of Ingo
> Molnar
> Sent: Wednesday, March 06, 2013 4:06 PM
> To: Mansoor, Illyas; Peter Zijlstra
> Cc: Linux Kernel; Linux PM; Frederic Weisbecker; Ingo Molnar; X86; Len Brown;
> Thomas Gleixner; Matthew Garrett; Tejun Heo; Paul E. McKenney; Rudramuni,
> Vishwesh M; richard@nod.at; josh@joshtriplett.org; Kumar P, Mahesh; Sil, Dyut
> K; Arjan van de Ven
> Subject: Re: [PATCH] x86: fix idle notifier not being called in CONFIG_X86_32
>
>
> * Mansoor, Illyas <illyas.mansoor@intel.com> wrote:
>
> > > * Illyas Mansoor <illyas.mansoor@intel.com> wrote:
> > >
> > > > Idle notifier not registered if CONFIG_X86_32 is defined, those
> > > > callbacks are empty for X86_32 platform.
> > > >
> > > > ifdef CONFIG_X86_64
> > > > void enter_idle(void);
> > > > void exit_idle(void);
> > > > else
> > > > static inline void enter_idle(void) { } static inline void
> > > > exit_idle(void) { } static inline void __exit_idle(void) { } endif
> > > >
> > > > Make this work on X86_32 platforms by removing the restriction for
> > > > X86_64
> > >
> > > What will they be used for?
> >
> > It's being used by interactive governor, and since the idle
> > notifications are not received It breaks the governor functionality on
> > X86_32
>
> But we never allowed idle notifiers on 32-bit and wanted to phase them out
even
> on
> x86-64 as well.
Support for Idle notifiers on 32-bit got broken from commit
90e240142bd31ff10aeda5a280a53153f4eff004
Before that they were getting registered from process_64.c since it was not
guarded using
CONFIG_X86_64
Commit 90e240142bd31ff10aeda5a280a53153f4eff004 merged x8_64 and x86_32 into
process.c and put
Restriction x86_64 on idle notifier which was correct since the notifier calls
were taken from process_64.c
>
> There's ongoing work to improve power saving in the scheduler - see Alex Shi's
> patchset on lkml: I think the two pieces of code should cooperate within the
> scheduler instead of going in two directions, duplicating effort and getting
in each
> other's way ...
Agree, it should not be conflicting each other.
Is there an alternative to idle notifications once those are deprecated.
Sorry couldn't find that from Alex Shi's patches on LKML
Thanks,
Illyas
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7212 bytes --]
next prev parent reply other threads:[~2013-03-06 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 5:41 Illyas Mansoor
2013-03-06 10:18 ` Ingo Molnar
2013-03-06 10:20 ` Mansoor, Illyas
2013-03-06 10:36 ` Ingo Molnar
2013-03-06 10:56 ` Mansoor, Illyas [this message]
2013-03-25 16:48 ` Len Brown
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=810586B7581CC8469141DADEBC37191224F773F0@BGSMSX102.gar.corp.intel.com \
--to=illyas.mansoor@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=dyut.k.sil@intel.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mahesh.kumar.p@intel.com \
--cc=matthew.garrett@nebula.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vishwesh.m.rudramuni@intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®