From: Alexey Starikovskiy <aystarik@gmail.com>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Sitsofe Wheeler <sitsofe@yahoo.com>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
LenBrown <lenb@kernel.org>,
Linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: EC: do transaction from interrupt context
Date: Sat, 27 Sep 2008 09:37:59 +0400 [thread overview]
Message-ID: <48DDC6B7.8020208@gmail.com> (raw)
In-Reply-To: <1222486760.4023.266.camel@yakui_zhao.sh.intel.com>
Zhao Yakui wrote:
> Of course such laptops can still work well except that CPU
> interrupt will be disabled for some extra time after Alexey's patch is
> applied .(The some extra time depends on how many EC Inb/out operations
> are executed).
>
>
spinlock is released after each I/O, so by your own calculation
it is disabled for 1.5 usec.
You can then multiply this number by lifetime of the universe,
it does not mean anything.
Regards,
Alex.
> In my email the purpose that I point out 2000 EC I/O read/write
> operation doesn't indicate that 2000 EC I/O read/write will be executed
> per second. What I want to say is that EC I/O read/write is slow
> operation. If quite a lot of EC I/O read/write are accessed for some
> reasons in some time, the CPU interrupt will be disabled for a long
> time. In such case the normal laptop will be affected by this. (Of
> course maybe the affect will be very tiny).
> In fact in kernel source code if the race can be resolved by other
> synchronization protection mechanism, the spin_lock had better be
> avoided.
>
Please explain, I'd like to make poster of it :)
next prev parent reply other threads:[~2008-09-27 5:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 17:00 [PATCH] ACPI: EC: do transaction from interrupt context Alexey Starikovskiy
2008-09-25 17:52 ` Sitsofe Wheeler
2008-09-26 1:06 ` Zhao Yakui
2008-09-26 5:42 ` Sitsofe Wheeler
2008-09-26 6:01 ` Alexey Starikovskiy
2008-09-26 9:03 ` Alan Jenkins
2008-09-26 10:42 ` Alexey Starikovskiy
2008-09-26 11:17 ` Alan Jenkins
2008-09-26 6:04 ` Zhao Yakui
2008-09-26 12:33 ` Rafael J. Wysocki
2008-09-26 13:54 ` Zhao, Yakui
2008-09-26 14:15 ` Rafael J. Wysocki
2008-09-26 14:53 ` Alexey Starikovskiy
2008-09-26 15:18 ` Rafael J. Wysocki
2008-09-26 15:21 ` Alexey Starikovskiy
2008-09-26 15:48 ` Rafael J. Wysocki
2008-09-26 15:47 ` Alexey Starikovskiy
2008-09-26 15:57 ` Rafael J. Wysocki
2008-09-26 15:10 ` Zhao Yakui
2008-09-26 15:39 ` Rafael J. Wysocki
2008-09-27 3:39 ` Zhao Yakui
2008-09-27 5:37 ` Alexey Starikovskiy [this message]
2008-09-27 5:59 ` Zhao Yakui
2008-09-27 6:44 ` Alexey Starikovskiy
2008-09-25 20:10 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 6:16 Sitsofe Wheeler
2008-09-25 11:24 Alexey Starikovskiy
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=48DDC6B7.8020208@gmail.com \
--to=aystarik@gmail.com \
--cc=Linux-acpi@vger.kernel.org \
--cc=astarikovskiy@suse.de \
--cc=lenb@kernel.org \
--cc=rjw@sisk.pl \
--cc=sitsofe@yahoo.com \
--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 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.