From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: lenb@kernel.org
Cc: linux-pm@lists.linux-foundation.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org
Subject: [RFC 3/4] cpuidle : move tlb flag to the cpuidle header
Date: Fri, 8 Jun 2012 18:02:44 +0200 [thread overview]
Message-ID: <1339171365-4098-3-git-send-email-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <1339171365-4098-1-git-send-email-daniel.lezcano@linaro.org>
Move this specific flag to the header file.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
drivers/idle/intel_idle.c | 8 --------
include/linux/cpuidle.h | 7 +++++++
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
index d0f59c3..3456fc9 100644
--- a/drivers/idle/intel_idle.c
+++ b/drivers/idle/intel_idle.c
@@ -100,14 +100,6 @@ static int intel_idle(struct cpuidle_device *dev,
static struct cpuidle_state *cpuidle_state_table;
/*
- * Set this flag for states where the HW flushes the TLB for us
- * and so we don't need cross-calls to keep it consistent.
- * If this flag is set, SW flushes the TLB, so even if the
- * HW doesn't do the flushing, this flag is safe to use.
- */
-#define CPUIDLE_FLAG_TLB_FLUSHED 0x10000
-
-/*
* States are indexed by the cstate number,
* which is also the index into the MWAIT hint array.
* Thus C0 is a dummy.
diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h
index f5915e9..aafacd4 100644
--- a/include/linux/cpuidle.h
+++ b/include/linux/cpuidle.h
@@ -64,9 +64,16 @@ struct cpuidle_state {
* the cpuidle core the specified state can use the *
* enter_dead function. *
* *
+ * CPUIDLE_FLAG_TLB_FLUSHED : Set this flag for states where the HW flushes the *
+ * TLB for us and so we don't need cross-calls to *
+ * keep it consistent. If this flag is set, SW *
+ * flushes the TLB, so even if the HW doesn't do the *
+ * flushing, this flag is safe to use. *
+ * *
*******************************************************************************/
#define CPUIDLE_FLAG_TIME_VALID 0x01
#define CPUIDLE_FLAG_DEAD_VALID 0x02
+#define CPUIDLE_FLAG_TLB_FLUSHED 0x04
/**
* cpuidle_get_statedata - retrieves private driver state data
--
1.7.5.4
next prev parent reply other threads:[~2012-06-08 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 16:02 [RFC 1/4] cpuidle: define the enter function in the driver structure Daniel Lezcano
2012-06-08 16:02 ` [RFC 2/4] cpuidle: move enter_dead to " Daniel Lezcano
2012-06-08 16:02 ` Daniel Lezcano [this message]
[not found] ` <1339171365-4098-1-git-send-email-daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-06-08 16:02 ` [RFC 4/4] cpuidle: replace the 'disable' field by a flag Daniel Lezcano
2012-06-08 17:33 ` [linux-pm] [RFC 1/4] cpuidle: define the enter function in the driver structure Deepthi Dharwar
2012-06-08 21:34 ` Daniel Lezcano
[not found] ` <4FD27000.7000208-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-06-13 12:44 ` [linux-pm] " Jean Pihet
2012-06-13 13:10 ` Daniel Lezcano
2012-06-14 7:49 ` Namhyung Kim
2012-06-14 8:16 ` Daniel Lezcano
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=1339171365-4098-3-git-send-email-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=lenb@kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).