From: Andi Kleen <ak@suse.de>
To: Dmitriy Zavin <dmitriyz@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: therm_throt: Refactor and improve thermal throttle processing
Date: Wed, 20 Sep 2006 09:43:59 +0200 [thread overview]
Message-ID: <200609200943.59550.ak@suse.de> (raw)
In-Reply-To: <11587201623432-git-send-email-dmitriyz@google.com>
On Wednesday 20 September 2006 04:42, Dmitriy Zavin wrote:
> This patch-set factors out the thermal throttle processing code
> from i386 and x86_64 into a separate file (therm_throt.c).
> This allows consistent reporting of CPU thermal throttle events.
> Furthermore, a counter is added to /sys that keeps track of the
> number of thermal events, such that the user knows how bad the
> thermal problem might be (since the logging to syslog and mcelog
> is rate limited).
Can you put this blurb into the description of the main patch that implements
the code please too?
-Andi
prev parent reply other threads:[~2006-09-20 7:45 UTC|newest]
Thread overview: 12+ 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 ` [PATCH 3/4] therm_throt: Make the jiffies compares use the 64bit safe macros Dmitriy Zavin
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 ` Andi Kleen [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=200609200943.59550.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dmitriyz@google.com \
--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.