From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhao Yakui <yakui.zhao@intel.com>,
linux-acpi@vger.kernel.org, lenb@kernel.org
Subject: Re: a problem about the two patches in bug 10724 & 11428
Date: Mon, 01 Sep 2008 16:52:40 +0400 [thread overview]
Message-ID: <48BBE598.3020700@suse.de> (raw)
In-Reply-To: <20080901122158.GB21970@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Mon, 01 Sep 2008, Zhao Yakui wrote:
>> Will the above two patches hit the upstream kernel? If the above two patches hits the upstream kernel, it
>> seems that the boot option of "ec_intr=" comes back again and EC can't be switched from interrupt mode to polling
>> mode if EC GPE interrupt is missing. In such case maybe the battery/AC/thermal driver can't work well if the info of
>> battery/AC/thermal is related with EC. Maybe there exists the regression on some laptops.
>
> Right now, the fact that it gives up on interrupt mode too easily IS causing
> regressions on ThinkPads (like the T43 I own). Since polling mode does
> work, it is just a performance regression, so you won't get many reports
> about it since most people don't look for such stuff in their kernel logs.
>
> Some ECs trigger the interrupt/poll-mode checks just on small windows
> (typically during resume -- might even be a bug somewhere in ACPICA or
> Linux, and not on the EC). We should not be giving up using interrupt mode
> on these so easily. Maybe retry enabling interrupt mode after some seconds
> a few times (like 3 or 5)? If it is a transient problem, that will avoid
> the permanent performance regression of polled mode.
Right, I am considering this option too.
Thanks,
Alex.
next prev parent reply other threads:[~2008-09-01 12:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 6:40 a problem about the two patches in bug 10724 & 11428 Zhao Yakui
2008-09-01 7:49 ` Alexey Starikovskiy
2008-09-01 9:55 ` Zhao Yakui
2008-09-01 12:18 ` Alexey Starikovskiy
2008-09-02 1:59 ` Zhao Yakui
2008-09-02 8:36 ` Alexey Starikovskiy
2008-09-02 9:31 ` Zhao Yakui
2008-09-02 9:26 ` Alan Jenkins
2008-09-02 9:30 ` Alexey Starikovskiy
2008-09-02 10:00 ` Zhao Yakui
2008-09-01 12:21 ` Henrique de Moraes Holschuh
2008-09-01 12:52 ` Alexey Starikovskiy [this message]
2008-09-01 20:35 ` Alexey Starikovskiy
2008-09-01 20:59 ` Alexey Starikovskiy
2008-09-02 1:03 ` Zhao Yakui
2008-09-02 2:03 ` Henrique de Moraes Holschuh
2008-09-02 3:39 ` Zhao Yakui
2008-09-02 9:19 ` Alan Jenkins
2008-09-02 8:05 ` Zhao Yakui
2008-09-03 6:02 ` Zhao Yakui
2008-09-03 6:46 ` Alexey Starikovskiy
2008-09-03 7:28 ` Zhao Yakui
2008-09-03 8:03 ` Zhao Yakui
2008-09-03 7:53 ` Alexey Starikovskiy
2008-09-03 8:34 ` Zhao Yakui
2008-09-03 21:55 ` RFC: fast transactions in EC [was: a problem about the two patches in bug 10724 & 11428] Alexey Starikovskiy
2008-09-04 2:58 ` Zhao Yakui
2008-09-04 3:06 ` Alexey Starikovskiy
2008-09-04 3:56 ` Alexey Starikovskiy
2008-09-04 4:51 ` Alexey Starikovskiy
2008-09-05 20:07 ` Andrew Morton
2008-09-08 8:19 ` Alexey Starikovskiy
2008-09-08 8:28 ` Andrew Morton
2008-09-08 8:30 ` Alexey Starikovskiy
2008-09-08 8:41 ` Andrew Morton
2008-09-03 22:28 ` a problem about the two patches in bug 10724 & 11428 Alexey Starikovskiy
2008-09-04 3:43 ` Zhao Yakui
2008-09-04 3:47 ` Alexey Starikovskiy
2008-09-04 6:00 ` Zhao Yakui
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=48BBE598.3020700@suse.de \
--to=astarikovskiy@suse.de \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=yakui.zhao@intel.com \
/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