From: Chris Wilson <chris@chris-wilson.co.uk>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Trim blitter block size
Date: Mon, 10 Feb 2020 23:02:41 +0000 [thread overview]
Message-ID: <158137576129.5235.4266099795221209912@skylake-alporthouse-com> (raw)
In-Reply-To: <158133914671.5235.14899451517100302990@skylake-alporthouse-com>
Quoting Chris Wilson (2020-02-10 12:52:26)
> Quoting Matthew Auld (2020-02-10 12:47:35)
> > On Thu, 6 Feb 2020 at 14:10, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > >
> > > Reduce the amount of work we do to verify client blt correctness as
> > > currently our 0.5s subtests takes about 15s on slower devices!
> > >
> > > v2: Grow the maximum block size until we run out of time
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Is that bsw-kefka issue(coherency?) something new?
>
> It's something to worry about.
Oh, it's just the vlv/chv clflush bug. Nothing to see here...
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-10 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 14:09 [Intel-gfx] [PATCH] drm/i915/selftests: Trim blitter block size Chris Wilson
2020-02-06 15:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Trim blitter block size (rev4) Patchwork
2020-02-06 15:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-02-10 12:47 ` [Intel-gfx] [PATCH] drm/i915/selftests: Trim blitter block size Matthew Auld
2020-02-10 12:52 ` Chris Wilson
2020-02-10 23:02 ` Chris Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-10 23:10 Chris Wilson
2020-02-06 3:33 [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-02-06 9:20 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-02-06 0:33 Chris Wilson
2020-02-06 12:52 ` Chris Wilson
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=158137576129.5235.4266099795221209912@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.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.