From: Matthew Auld <matthew.william.auld@gmail.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
Intel Graphics Development <Intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 3/3] tests/i915/gem_watchdog: Exercise long rendering chains
Date: Tue, 30 Mar 2021 16:40:04 +0100 [thread overview]
Message-ID: <CAM0jSHMw1UfU4RghdeWW16fXzbVu40QkAMip+RXMkQ-C9hXXxw@mail.gmail.com> (raw)
In-Reply-To: <20210318162400.2065097-4-tvrtko.ursulin@linux.intel.com>
On Thu, 18 Mar 2021 at 16:24, Tvrtko Ursulin
<tvrtko.ursulin@linux.intel.com> wrote:
>
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Test to demonstrate a problem with the proposed default fence expiry
> semantics where long rendering chain get silently broken.
>
> If we had fence error propagation (no clear agreement whether to do it or
> not) maybe userspace would see if, assuming fence status is looked at, but
> overall potential rendering corruption is the story in any case.
>
> Note that this is not a single long batch but just a long queue of work
> which. Could be viewed as heavy system load as well (like virtualisation
> or other types of resource sharing).
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-30 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 16:23 [Intel-gfx] [PATCH i-g-t 0/3] Default fence expiration test Tvrtko Ursulin
2021-03-18 16:23 ` [igt-dev] " Tvrtko Ursulin
2021-03-18 16:23 ` [Intel-gfx] [PATCH i-g-t 1/3] lib: Add helper for reading modparam values Tvrtko Ursulin
2021-03-18 16:23 ` [igt-dev] " Tvrtko Ursulin
2021-03-30 10:49 ` [Intel-gfx] " Matthew Auld
2021-03-30 10:49 ` Matthew Auld
2021-03-18 16:23 ` [Intel-gfx] [PATCH i-g-t 2/3] tests/i915: Default fence expiry test Tvrtko Ursulin
2021-03-30 12:53 ` Matthew Auld
2021-03-18 16:24 ` [Intel-gfx] [PATCH i-g-t 3/3] tests/i915/gem_watchdog: Exercise long rendering chains Tvrtko Ursulin
2021-03-18 16:24 ` [igt-dev] " Tvrtko Ursulin
2021-03-30 15:40 ` Matthew Auld [this message]
2021-03-18 17:57 ` [igt-dev] ✓ Fi.CI.BAT: success for Default fence expiration test (rev2) Patchwork
2021-03-18 22:44 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=CAM0jSHMw1UfU4RghdeWW16fXzbVu40QkAMip+RXMkQ-C9hXXxw@mail.gmail.com \
--to=matthew.william.auld@gmail.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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.