From: Martin Peres <martin.peres@linux.intel.com>
To: "Ser, Simon" <simon.ser@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_chamelium: add test descriptions
Date: Wed, 11 Sep 2019 09:45:46 +0300 [thread overview]
Message-ID: <fb0939c3-5f96-1436-a060-46110405fd09@linux.intel.com> (raw)
In-Reply-To: <d6737f62ab23fe4a57b56e25ba6cf1160a0cfb56.camel@intel.com>
On 10/09/2019 15:27, Ser, Simon wrote:
> On Fri, 2019-09-06 at 17:23 +0300, Martin Peres wrote:
>>
>> On 05/09/2019 16:36, Simon Ser wrote:
>>>
>>> +static const char test_hpd_storm_detect_desc[] =
>>> + "Trigger a series of hotplugs in a very small timeframe to
>>> simulate a"
>>> + "bad cable, check the kernel falls back to polling";
>>
>> "falls back to polling to avoid an irq storm"
>
> irq → hotplug
I really meant IRQ storm. That was the bug we got (a machine was slow as
heck because the connector was lose and the HW was sending thousands of
hotplug IRQs per second).
If you want to say hotplug IRQ storm, that can work too :)
Martin
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-09-11 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:36 [igt-dev] [PATCH i-g-t] tests/kms_chamelium: add test descriptions Simon Ser
2019-09-05 14:09 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-09-05 18:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-09-06 14:23 ` [igt-dev] [PATCH i-g-t] " Martin Peres
2019-09-10 12:27 ` Ser, Simon
2019-09-11 6:45 ` Martin Peres [this message]
2019-09-11 10:02 ` Ser, Simon
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=fb0939c3-5f96-1436-a060-46110405fd09@linux.intel.com \
--to=martin.peres@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=simon.ser@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