From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Starikovskiy Subject: Re: Reading EeePC900 battery info causes stalls Date: Thu, 25 Sep 2008 16:01:21 +0400 Message-ID: <48DB7D91.4000206@gmail.com> References: <48DB5032.8020604@gmail.com> <48DB5B90.9060607@yahoo.com> <48DB5FEE.4000404@gmail.com> <48DB710A.2060206@gmail.com> <48DB7C5A.6070900@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from ey-out-2122.google.com ([74.125.78.26]:46133 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755498AbYIYMBX (ORCPT ); Thu, 25 Sep 2008 08:01:23 -0400 Received: by ey-out-2122.google.com with SMTP id 6so121768eyi.37 for ; Thu, 25 Sep 2008 05:01:21 -0700 (PDT) In-Reply-To: <48DB7C5A.6070900@yahoo.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Sitsofe Wheeler Cc: linux-acpi@vger.kernel.org Sitsofe Wheeler wrote: > Alexey Starikovskiy wrote: >> acpi_ps_parse_aml() is called not so often (~10000usec), so maybe it >> is a "sweet spot" > > The latency is pretty bad with this patch (assuming you did not want > it applied on top of your previous patch) > > Here's the tail end of a full trace: > http://sucs.org/~sits/test/eeepc-debug/20080925/1250/latency_trace_all_tail.gz > (3.3Mbytes but close 100Mbytes when decompressed) > latency: 2912285 us, #1000038/5344107, CPU#0 | (M:desktop VP:0, KP:0, > SP:0 HP:0 > ) > > Here's a complete (but filtered) trace: > http://sucs.org/~sits/test/eeepc-debug/20080925/1250/latency_trace.gz > latency: 315814 us, #227600/227600, CPU#0 | (M:desktop VP:0, KP:0, > SP:0 HP:0) > Ok, let's stick with previous patch then. It will be somewhat difficult to push though, because the code we touched belongs to ACPICA (multi-platform code), so should not contain explicit Linux-only operands. If you agree that the place is right, I'll make proper patch with all needed redirections to make ACPICA happy.