From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
platform-driver-x86@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops
Date: Thu, 29 Aug 2013 12:18:14 -0400 [thread overview]
Message-ID: <521F7446.7060002@canonical.com> (raw)
In-Reply-To: <CA+55aFy09OfUb_ENi6NgVWaNM7YBvLovcf5FvyHfpXXBUGsQkg@mail.gmail.com>
On 08/14/2013 05:11 PM, Linus Torvalds wrote:
> On Wed, Aug 14, 2013 at 9:38 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>> Linus, you may want to pick this up directly, as I'm not sure if
>> Matthew is still looking after the x86 drivers these days.
> Can't we make the simpler patch be to just not spam the logs? Do it
> once, and forget about it. Maybe make the timeouts long enough to make
> sure that there are no other downsides from having the driver
> occasionally testing if it's back?
>
> I *detest* hardware-specific blacklists. They are impossible to
> maintain, and we've had the situation more than once that we fixed the
> real bug that caused the blacklist in the first place, but the entry
> stays around because nobody knows/cares/tests it.
>
> Linus
Hi Jesse,
What are your thoughts on alternatives to using a blacklist? Is there a
bit we can read to determine if IPS is supported on a platform?
If not, can we do something like the following? Basically increase the
timeout to 30 seconds then return an error from the monitor if there was
no update in that time:
diff --git a/drivers/platform/x86/intel_ips.c
b/drivers/platform/x86/intel_ips.c
index 18dcb58..a2391f7 100644
--- a/drivers/platform/x86/intel_ips.c
+++ b/drivers/platform/x86/intel_ips.c
@@ -1095,8 +1095,15 @@ static int ips_monitor(void *data)
cur_seqno = (thm_readl(THM_ITV) & ITV_ME_SEQNO_MASK) >>
ITV_ME_SEQNO_SHIFT;
if (cur_seqno == last_seqno &&
- time_after(jiffies, seqno_timestamp + HZ)) {
- dev_warn(&ips->dev->dev, "ME failed to update
for more than 1s, likely hung\n");
+ time_after(jiffies, seqno_timestamp + (HZ*30))) {
+ /* It's been 30s. ME is likely hung. Print
message and return. */
+ dev_warn(&ips->dev->dev, "ME failed to update
for more than 30s, likely hung so exiting\n");
+ del_timer_sync(&timer);
+ destroy_timer_on_stack(&timer);
+
+ dev_dbg(&ips->dev->dev, "ips-monitor thread
stopped\n");
+ return -1;
+
} else {
seqno_timestamp = get_jiffies_64();
last_seqno = cur_seqno;
There may be more to include such as restarting the monitor later to see
if the ME ever came back, just looking for other ideas and/or suggestions.
Thanks,
Joe
next prev parent reply other threads:[~2013-08-29 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1376494861.git.joseph.salisbury@canonical.com>
2013-08-14 16:22 ` [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops Joseph Salisbury
2013-08-14 16:38 ` Jesse Barnes
2013-08-14 16:54 ` Matthew Garrett
2013-08-14 21:11 ` Linus Torvalds
2013-08-29 16:18 ` Joseph Salisbury [this message]
2013-08-29 16:32 ` Jesse Barnes
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=521F7446.7060002@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=torvalds@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