From: "Mrozek, Michal" <michal.mrozek@intel.com>
To: "Antognolli, Rafael" <rafael.antognolli@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: "Zdunowski, Piotr" <piotr.zdunowski@intel.com>,
"Intel-gfx@lists.freedesktop.org"
<Intel-gfx@lists.freedesktop.org>,
"Ekstrand, Jason" <jason.ekstrand@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/tgl: WaDisableGPGPUMidThreadPreemption
Date: Mon, 9 Mar 2020 17:02:33 +0000 [thread overview]
Message-ID: <299e1f69592d48a7a4e964b6a3d2e7d1@intel.com> (raw)
In-Reply-To: <20200304160245.ewy55e2iqtcey6vs@rantogno-mobl4.amr.corp.intel.com>
>>But he asked whether it's possible for Media and OpenCL drivers to also disable mid-thread preemption through the INTERFACE_DESCRIPTOR_DATA, instead of from the >>kernel side, so we could try to experiment with it in the future.
Interface Descriptor setting only switches the preemption from mid thread to thread group.
It doesn't allow to disable it completely and there are cases where this is required (i.e. VME).
For that we need mmio whitelist.
Michal
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-09 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 15:31 [Intel-gfx] [PATCH] drm/i915/tgl: WaDisableGPGPUMidThreadPreemption Tvrtko Ursulin
2020-03-04 16:02 ` Rafael Antognolli
2020-03-04 16:24 ` Tvrtko Ursulin
2020-03-04 17:01 ` Rafael Antognolli
2020-03-04 17:04 ` Jason Ekstrand
2020-03-05 12:40 ` Ye, Tony
2020-03-09 17:02 ` Mrozek, Michal [this message]
2020-03-10 8:45 ` Tvrtko Ursulin
2020-03-10 8:50 ` Mrozek, Michal
2020-03-04 18:54 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2020-03-04 19:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-05 13:37 ` Tvrtko Ursulin
2020-03-05 12:38 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-03-05 16:46 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=299e1f69592d48a7a4e964b6a3d2e7d1@intel.com \
--to=michal.mrozek@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=jason.ekstrand@intel.com \
--cc=piotr.zdunowski@intel.com \
--cc=rafael.antognolli@intel.com \
--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.