All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: patch for bugs 9998 and 10724
Date: Mon, 08 Sep 2008 12:25:03 +0400	[thread overview]
Message-ID: <48C4E15F.2020701@suse.de> (raw)
In-Reply-To: <1220842582.3441.30.camel@rzhang-dt>


Zhang Rui wrote:
> On Fri, 2008-09-05 at 16:45 +0400, Alexey Starikovskiy wrote:
>> Zhang Rui wrote:
>>> On Thu, 2008-09-04 at 16:35 +0400, Alexey Starikovskiy wrote:
>>>> Here is the same patch as attachment for your convenience.
>>>> Alexey Starikovskiy wrote:
>>>>> Hi Andy,
>>>>>
>>>>> I just uploaded patch for bugs 9998 and 10724, which solves the problem 
>>>>> of interrupt storm more cleanly.
>>>>> Could you please add this patch to testing?
>>>>>
>>>>> Thanks,
>>>>> Alex.
>>>>>
>>>>>
>>> +       ec->t.command = 0;
>>> +       if (test_bit(EC_FLAGS_GPE_STORM, &ec->flags)) {
>>> +               /* check if we received SCI during transaction */
>>> +               ec_check_sci(ec, acpi_ec_read_status(ec));
>>> +               /* it is safe to enable GPE outside of transaction */
>>> +               acpi_enable_gpe(NULL, ec->gpe, ACPI_NOT_ISR);
>>> +       } else if (test_bit(EC_FLAGS_GPE_MODE, &ec->flags) &&
>>> +                  atomic_read(&ec->irq_count) >
>>> ACPI_EC_STORM_THRESHOLD)
> +	{
>>> +               pr_debug(PREFIX "GPE storm detected\n");
>>> +               set_bit(EC_FLAGS_GPE_STORM, &ec->flags);
> +	}
Thanks!
> 
> 
> thanks,
> rui
> 
>>> +       return 0;
>>> +}
>>>
>>> you will set the EC_FLAGS_GPE_STORM flag in every ec transaction.
>>> I don't think that's what you/we want. :)
>> please elaborate...
>> If EC_FLAGS_GPE_STORM is set once, I will not get there (else).
> 
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-09-08  8:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  5:57 [PATCH] ACPI : Avoid bogus timeout about SMbus check Zhao Yakui
2008-09-04 12:18 ` Andi Kleen
2008-09-04 12:33   ` patch for bugs 9998 and 10724 Alexey Starikovskiy
2008-09-04 12:35     ` Alexey Starikovskiy
2008-09-04 13:18       ` Andi Kleen
2008-09-05  2:26       ` Zhang Rui
2008-09-05  3:49         ` Zhao Yakui
2008-09-05 12:58           ` Alexey Starikovskiy
2008-09-08  1:18             ` Zhao Yakui
2008-09-05 12:45         ` Alexey Starikovskiy
2008-09-08  2:56           ` Zhang Rui
2008-09-08  8:25             ` Alexey Starikovskiy [this message]
2008-09-09  9:13               ` Zhao Yakui
2008-09-09  9:12                 ` Alexey Starikovskiy
2008-09-09  9:28                   ` Alexey Starikovskiy
2008-09-09  9:43                   ` Zhao Yakui
2008-09-09  9:36                     ` Alexey Starikovskiy
2008-09-10  1:15                       ` Zhao Yakui
2008-09-10  2:23                         ` Alexey Starikovskiy
2008-09-11 19:49   ` [PATCH] ACPI : Avoid bogus timeout about SMbus check Oldrich Jedlicka
2008-09-11 21:13     ` Alexey Starikovskiy
2008-09-14 20:06       ` Oldrich Jedlicka
2008-09-12  1:38     ` Zhao Yakui
2008-09-14 20:17       ` Oldrich Jedlicka

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=48C4E15F.2020701@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@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.