From: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Lyude <lyude@redhat.com>, Petri Latvala <petri.latvala@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Subject: [PATCH i-g-t 0/2] Unrelated hotplug uevent masking out actual test result
Date: Tue, 18 Jul 2017 18:16:25 +0300 [thread overview]
Message-ID: <20170718151627.29641-1-paul.kocialkowski@linux.intel.com> (raw)
This patch introduces a workaround for a case where a uevent is issued
by the kernel because of DP link training failing on a connector
unrelated to the current test. Since the test depends on receiving a
hotplug uevent, it previously passed even though it should not have.
False positives also occur due to the plug/unplug events being delayed
and issued at resume time. This is mitigated by catching and flushing
hotplugs everytime a change is made on connectors, but it is not enough
to ensure that all hotplug events were caught and not delayed.
The problem here is that it is not possible to find out the exact reason
why a uevent is issued by the kernel. A possible way to fix this would
be to introduce more fields (the connector name and some reason why the
event is triggered would probably be sufficient).
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-07-18 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 15:16 Paul Kocialkowski [this message]
2017-07-18 15:16 ` [PATCH i-g-t 1/2] tests/chamelium: Skip suspend/resume test with unreliable hotplug event Paul Kocialkowski
2017-07-18 21:21 ` Chris Wilson
2017-07-19 8:31 ` Paul Kocialkowski
2017-07-19 15:47 ` Lyude Paul
2017-07-18 15:16 ` [PATCH i-g-t 2/2] tests/chamelium: Catch and flush hotplug uevents after each plug Paul Kocialkowski
2017-07-18 20:12 ` [Intel-gfx] [PATCH i-g-t 0/2] Unrelated hotplug uevent masking out actual test result Lyude Paul
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=20170718151627.29641-1-paul.kocialkowski@linux.intel.com \
--to=paul.kocialkowski@linux.intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=petri.latvala@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;
as well as URLs for NNTP newsgroup(s).