All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Illyas Mansoor <illyas.mansoor@intel.com>
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, josh@joshtriplett.org, "Kumar P,
	Mahesh" <mahesh.kumar.p@intel.com>,
	"Sil, Dyut K" <dyut.k.sil@intel.com>
Subject: Re: [PATCH] x86: fix idle notifier not being called in CONFIG_X86_32
Date: Wed, 6 Mar 2013 11:18:18 +0100	[thread overview]
Message-ID: <20130306101818.GA6587@gmail.com> (raw)
In-Reply-To: <1362375673-29287-1-git-send-email-illyas.mansoor@intel.com>


* 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?

Thanks,

	Ingo

  reply	other threads:[~2013-03-06 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  5:41 [PATCH] x86: fix idle notifier not being called in CONFIG_X86_32 Illyas Mansoor
2013-03-06 10:18 ` Ingo Molnar [this message]
2013-03-06 10:20   ` Mansoor, Illyas
2013-03-06 10:36     ` Ingo Molnar
2013-03-06 10:56       ` Mansoor, Illyas
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=20130306101818.GA6587@gmail.com \
    --to=mingo@kernel.org \
    --cc=dyut.k.sil@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=illyas.mansoor@intel.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@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 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.