All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitriy Zavin <dmitriyz@google.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de, akpm@osdl.org
Subject: [PATCH 3/4] therm_throt: Make the jiffies compares use the 64bit safe macros.
Date: Tue, 19 Sep 2006 19:42:41 -0700	[thread overview]
Message-ID: <1158720162574-git-send-email-dmitriyz@google.com> (raw)
In-Reply-To: <11587201621900-git-send-email-dmitriyz@google.com>

Signed-off-by: Dmitriy Zavin <dmitriyz@google.com>
---
 arch/i386/kernel/cpu/mcheck/therm_throt.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/i386/kernel/cpu/mcheck/therm_throt.c b/arch/i386/kernel/cpu/mcheck/therm_throt.c
index 342750e..3d6f217 100644
--- a/arch/i386/kernel/cpu/mcheck/therm_throt.c
+++ b/arch/i386/kernel/cpu/mcheck/therm_throt.c
@@ -22,7 +22,7 @@ #endif /* CONFIG_X86_64 */
 /* How long to wait between reporting thermal events */
 #define CHECK_INTERVAL              (300 * HZ)
 
-static DEFINE_PER_CPU(unsigned long, next_check);
+static DEFINE_PER_CPU(__u64, next_check) = INITIAL_JIFFIES;
 
 #ifdef CONFIG_X86_64
 static void therm_throt_log_mce(unsigned int cpu, __u64 status)
@@ -58,10 +58,10 @@ void therm_throt_process(int curr, __u64
 {
 	unsigned int cpu = smp_processor_id();
 
-	if (time_before(jiffies, __get_cpu_var(next_check)))
+	if (time_before64(get_jiffies_64(), __get_cpu_var(next_check)))
 		return;
 
-	__get_cpu_var(next_check) = jiffies + CHECK_INTERVAL;
+	__get_cpu_var(next_check) = get_jiffies_64() + CHECK_INTERVAL;
 
 	/* if we just entered the thermal event */
 	if (curr) {
-- 
1.4.2


  reply	other threads:[~2006-09-20  2:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20  2:42 therm_throt: Refactor and improve thermal throttle processing Dmitriy Zavin
2006-09-20  2:42 ` [PATCH 1/4] x86_64/i386 thermal mce: Refactor thermal throttle reporting Dmitriy Zavin
2006-09-20  2:42   ` [PATCH 2/4] jiffies: Add 64bit jiffies compares (needed when long < 64bit) Dmitriy Zavin
2006-09-20  2:42     ` Dmitriy Zavin [this message]
2006-09-20  2:42       ` [PATCH 4/4] therm_throt: Add a cumulative event counter and export it to /sys Dmitriy Zavin
2006-09-20  7:42         ` Andi Kleen
2006-09-20  7:43       ` [PATCH 3/4] therm_throt: Make the jiffies compares use the 64bit safe macros Andi Kleen
2006-09-20  7:40     ` [PATCH 2/4] jiffies: Add 64bit jiffies compares (needed when long < 64bit) Andi Kleen
2006-09-20 23:08       ` Dmitriy Zavin
2006-09-20  7:38   ` [PATCH 1/4] x86_64/i386 thermal mce: Refactor thermal throttle reporting Andi Kleen
2006-09-20 20:54     ` Dmitriy Zavin
2006-09-20  7:43 ` therm_throt: Refactor and improve thermal throttle processing Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-09-22  0:48 [PATCH 0/4 v2] therm_throt: Refactor thermal throttle processing, and keep a total count of events Dmitriy Zavin
2006-09-22  0:48 ` [PATCH 1/4] x86_64/i386 therm mce: Refactor thermal throttle processing Dmitriy Zavin
2006-09-22  0:48   ` [PATCH 2/4] jiffies: Add 64bit jiffies compares (for use with get_jiffies_64) Dmitriy Zavin
2006-09-22  0:48     ` [PATCH 3/4] therm_throt: Make the jiffies compares use the 64bit safe macros Dmitriy Zavin

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=1158720162574-git-send-email-dmitriyz@google.com \
    --to=dmitriyz@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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.