From: roychris <roychris-GANU6spQydw@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: SCI interrupt handler : spend too much time
Date: Thu, 04 Dec 2003 09:25:41 +0100 [thread overview]
Message-ID: <3FCEEF85.3050802@free.fr> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720BF7-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Personally, I think so.
Yu, Luming a écrit :
> Does it mean the overhead of SCI interrupt was not the root cause of
> this issue. --Luming
>
>
> -----Original Message-----
> *From:* roychris [mailto:roychris-GANU6spQydw@public.gmane.org]
> *Sent:* 2003?12?3? 20:49
> *To:* Pavel Machek
> *Cc:* Yu, Luming; acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> *Subject:* Re: [ACPI] SCI interrupt handler : spend too much time
>
> Just a precision,
> synaptic driver is not like the other mouses. psmouse call a
> specific fonction for this touchpad that is in an other module.
> The problem happens since 2.6, since psmouse and synaptic had been
> seperated....
>
> Pavel Machek wrote:
>
>>Hi!
>>
>>
>>
>>>It sound like serious one, if SCI interrupt handler was blamed for
>>>this issue. --Luming
>>>
>>>
>>
>>I investigated a bit, and interrupt latency alone is not enough to
>>break mouse. [Unfortunately, I do not have easy/sure way to reproduce
>>it.]
>>
>>Is it possible that SCI interrupt handler accesses keyboard controller
>>(and breaks mouse?)
>> Pavel
>>
>>
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2437 bytes --]
next prev parent reply other threads:[~2003-12-04 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 3:44 SCI interrupt handler : spend too much time Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720BF7-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-04 8:25 ` roychris [this message]
2003-12-04 9:53 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 3:35 Li, Shaohua
[not found] ` <571ACEFD467F7749BC50E0A98C17CDD8E84E1B-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-08 10:00 ` roychris
2003-12-08 3:21 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C04-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-08 9:19 ` Pavel Machek
[not found] ` <20031208091937.GB241-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-12-08 10:05 ` roychris
2003-12-03 3:36 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720BEF-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-03 12:41 ` roychris
2003-12-03 12:47 ` Pavel Machek
[not found] ` <20031203124720.GA11239-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-12-03 12:49 ` roychris
2003-11-23 20:47 roychris
[not found] ` <3FC11CEB.9040104-GANU6spQydw@public.gmane.org>
2003-12-01 18:28 ` Pavel Machek
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=3FCEEF85.3050802@free.fr \
--to=roychris-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.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