== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev12)
URL : https://patchwork.freedesktop.org/series/48194/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/execlists: Move RPCS setup to context pin
Okay!
Commit:
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev12)
URL : https://patchwork.freedesktop.org/series/48194/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5379 -> Patchwork_11256
Summary
---
== Series Details ==
Series: series starting with [1/4] drm/edid: Pass connector to AVI infoframe
functions
URL : https://patchwork.freedesktop.org/series/54903/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5379 -> Patchwork_11257
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
On Tue, Jan 08, 2019 at 02:41:25PM +0530, Uma Shankar wrote:
> From: Ville Syrjälä
>
> ADD HLG EOTF to the list of EOTF transfer functions supported.
> Hybrid Log-Gamma (HLG) is a high dynamic range (HDR) standard.
> HLG defines a nonlinear transfer function in which the lower
> half of the
On Tuesday, January 8, 2019 7:53:05 AM PST Joonas Lahtinen wrote:
> + Ken/Jason for Mesa
> Quoting Matt Roper (2019-01-07 21:19:31)
> > On Mon, Jan 07, 2019 at 01:23:50PM +0100, Michał Winiarski wrote:
> > > On Mon, Jan 07, 2019 at 01:01:16PM +0200, Joonas Lahtinen wrote:
> > > > Quoting José
Quoting Michal Wajdeczko (2019-01-08 22:33:18)
> On Tue, 08 Jan 2019 16:02:46 +0100, Chris Wilson
> wrote:
>
> > If we haven't shipped and enabled firmware for a particular platform,
> > there is nothing the user can do about it. Don't scare the user with an
> > unactionable, unidentifiable
On 2019-01-04 7:14 p.m., Lyude Paul wrote:
> This is the series I've been working on for a while now to get all of
> the atomic DRM drivers in the tree to use the atomic MST helpers, and to
> make the atomic MST helpers actually idempotent. Turns out it's a lot
> more difficult to do that without
On Tue, 2019-01-08 at 19:57 +, Wentland, Harry wrote:
> On 2019-01-04 7:14 p.m., Lyude Paul wrote:
> > This is the series I've been working on for a while now to get all of
> > the atomic DRM drivers in the tree to use the atomic MST helpers, and to
> > make the atomic MST helpers actually
On 2018-12-19 7:19 p.m., Lyude Paul wrote:
> While this isn't a complete fix, this will improve the reliability of
> drm_dp_get_last_connected_port_and_mstb() pretty significantly during
> hotplug events, since there's a chance that the in-memory topology tree
> may not be fully updated when
== Series Details ==
Series: series starting with [1/2] drm/i915/gvt: give the cmd parser
decode_info a const treatment
URL : https://patchwork.freedesktop.org/series/54884/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378_full -> Patchwork_11252_full
== Series Details ==
Series: series starting with [1/4] drm/edid: Pass connector to AVI infoframe
functions
URL : https://patchwork.freedesktop.org/series/54903/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
fc4e6824a03c drm/edid: Pass connector to AVI infoframe functions
Hi all,
Commit e845f099f1c6 ("drm/i915/dsc: Add Per connector debugfs node for
DSC support/enable") causes a Clang warning:
drivers/gpu/drm/i915/i915_debugfs.c:4961:17: warning: address of array
'intel_dp->dsc_dpcd' will always evaluate to 'true' [-Wpointer-bool-conversion]
if
On 2018-12-19 7:19 p.m., Lyude Paul wrote:
> This has never actually worked, and isn't needed anyway: the driver's
> always going to try to deallocate VCPI when it tears down the display
> that the VCPI belongs to.
>
> Signed-off-by: Lyude Paul
> Reviewed-by: Daniel Vetter
> Cc: David Airlie
>
== Series Details ==
Series: drm/i915: Downgrade scare message for unknwown HuC firmware (rev4)
URL : https://patchwork.freedesktop.org/series/54868/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378_full -> Patchwork_11253_full
== Series Details ==
Series: series starting with [1/5] drm/i915/backlight: Restore backlight on
resume, v3.
URL : https://patchwork.freedesktop.org/series/54896/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378 -> Patchwork_11255
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev12)
URL : https://patchwork.freedesktop.org/series/48194/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c919f2ba4d24 drm/i915/execlists: Move RPCS setup to context pin
65954284c0af drm/i915: Record
On 2019-01-04 7:14 p.m., Lyude Paul wrote:
> The current way of handling refcounting in the DP MST helpers is really
> confusing and probably just plain wrong because it's been hacked up many
> times over the years without anyone actually going over the code and
> seeing if things could be
== Series Details ==
Series: series starting with [1/2] drm/i915: Enable render context support for
Ironlake (gen5)
URL : https://patchwork.freedesktop.org/series/54876/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378_full -> Patchwork_11249_full
On 2018-12-19 7:19 p.m., Lyude Paul wrote:
> Up until now, freeing payloads on remote MST hubs that just had ports
> removed has almost never worked because we've been relying on port
> validation in order to stop us from accessing ports that have already
> been freed from memory, but ports which
On 2018-12-19 7:19 p.m., Lyude Paul wrote:
> Just like i915 and nouveau, it's a good idea for us to hold a malloc
> reference to the port here so that we never pass a freed pointer to any
> of the DP MST helper functions.
>
> Also, we stop unsetting aconnector->port in
>
== Series Details ==
Series: series starting with [1/2] drm/i915/userptr: Avoid struct_mutex
recursion for mmu_invalidate_range_start (rev2)
URL : https://patchwork.freedesktop.org/series/54869/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378_full -> Patchwork_11251_full
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
On Tue, 08 Jan 2019 16:02:46 +0100, Chris Wilson
wrote:
If we haven't shipped and enabled firmware for a particular platform,
there is nothing the user can do about it. Don't scare the user with an
unactionable, unidentifiable warning!
<6> [310.769452] i915 :00:02.0: GuC: No firmware
== Series Details ==
Series: MST refcounting/atomic helpers cleanup (rev5)
URL : https://patchwork.freedesktop.org/series/54030/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5778d100cac7 drm/dp_mst: Fix some formatting in drm_dp_add_port()
2fd355b3a9aa drm/dp_mst: Fix some
Quoting Chris Wilson (2019-01-08 12:28:18)
> Broadwater and the rest of gen4 do support being able to saving and
> reloading context specific registers between contexts, providing isolation
> of the basic GPU state (as programmable by userspace). This allows
> userspace to assume that the GPU
Hi Daniel,
On Tue, 8 Jan 2019 09:37:22 +0100 Daniel Vetter wrote:
>
>
> https://cgit.freedesktop.org/drm-tip/tree/fixups/drm-misc-next.patch?h=rerere-cache
>
> is the fixup you want. Should get baked into drm-next any moment, since
> the first drm-misc-next pull is already out.
I added that
== Series Details ==
Series: series starting with [1/2] drm/i915: Enable render context support for
Ironlake (gen5) (rev2)
URL : https://patchwork.freedesktop.org/series/54876/
State : failure
== Summary ==
Applying: drm/i915: Enable render context support for Ironlake (gen5)
Applying:
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
== Series Details ==
Series: MST refcounting/atomic helpers cleanup (rev5)
URL : https://patchwork.freedesktop.org/series/54030/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5380 -> Patchwork_11258
Summary
---
== Series Details ==
Series: series starting with [1/5] drm/i915/backlight: Restore backlight on
resume, v3.
URL : https://patchwork.freedesktop.org/series/54896/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5378_full -> Patchwork_11255_full
Hi,
Here's one race fix for gvt to handle request properly
between pre-scan of workload and submission.
Thanks.
--
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
Reindent some stuff, and split some stuff across multiple lines so we
aren't going over the text width limit.
Signed-off-by: Lyude Paul
Reviewed-by: Harry Wentland
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 18
The current way of handling refcounting in the DP MST helpers is really
confusing and probably just plain wrong because it's been hacked up many
times over the years without anyone actually going over the code and
seeing if things could be simplified.
To the best of my understanding, the current
This is the series I've been working on for a while now to get all of
the atomic DRM drivers in the tree to use the atomic MST helpers, and to
make the atomic MST helpers actually idempotent. Turns out it's a lot
more difficult to do that without also fixing how port and branch device
refcounting
Split some stuff across multiple lines, remove some unnecessary braces
Signed-off-by: Lyude Paul
Reviewed-by: Harry Wentland
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 14 --
1 file changed, 8 insertions(+), 6
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
There has been a TODO waiting for quite a long time in
drm_dp_mst_topology.c:
/* We cannot rely on port->vcpi.num_slots to update
* topology_state->avail_slots as the port may not exist if the parent
* branch device was unplugged. This should be fixed by tracking
Up until now, freeing payloads on remote MST hubs that just had ports
removed has almost never worked because we've been relying on port
validation in order to stop us from accessing ports that have already
been freed from memory, but ports which need their payloads released due
to being removed
Changes since v6:
- Move EXPORT_SYMBOL() for drm_dp_mst_topology_state_funcs to this
commit
- Document __drm_dp_mst_state_iter_get() and note that it shouldn't be
called directly
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Harry Wentland
Just like i915 and nouveau, it's a good idea for us to hold a malloc
reference to the port here so that we never pass a freed pointer to any
of the DP MST helper functions.
Also, we stop unsetting aconnector->port in
dm_dp_destroy_mst_connector(). There's literally no point to that
assignment
Same as we did for i915, but for nouveau this time. Additionally, we
grab a malloc reference to the port that lasts for the entire lifetime
of nv50_mstc, which gives us the guarantee that mstc->port will always
point to valid memory for as long as the mstc stays around.
Signed-off-by: Lyude Paul
Now that we finally have a sane way to keep port allocations around, use
it to fix the potential unchecked ->port accesses that nouveau makes by
making sure we keep the mst port allocated for as long as it's
drm_connector is accessible.
Additionally, now that we've guaranteed that mstc->port is
This has never actually worked, and isn't needed anyway: the driver's
always going to try to deallocate VCPI when it tears down the display
that the VCPI belongs to.
Signed-off-by: Lyude Paul
Reviewed-by: Harry Wentland
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Juston Li
---
Currently, nouveau uses the yolo method of setting up MST displays: it
uses the old VCPI helpers (drm_dp_find_vcpi_slots()) for computing the
display configuration. These helpers don't take care to make sure they
take a reference to the mstb port that they're checking, and
additionally don't
Trying to destroy the connector using mstc->connector.funcs->destroy()
if connector initialization fails is wrong: there is no possible
codepath in nv50_mstc_new where nv50_mstm_add_connector() would return
<0 and mstc would be non-NULL.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
Cc: David
Fix some indenting, split some stuff across multiple lines.
Signed-off-by: Lyude Paul
Reviewed-by: Harry Wentland
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff
It occurred to me that we never actually check this! So let's start
doing that.
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Harry Wentland
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 8 +++-
1 file changed, 7 insertions(+), 1
Split some stuff across multiple lines
Signed-off-by: Lyude Paul
Reviewed-by: Harry Wentland
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
s/drm_dp_get_validated_port_ref/drm_dp_mst_topology_get_port_validated/
s/drm_dp_put_port/drm_dp_mst_topology_put_port/
s/drm_dp_get_validated_mstb_ref/drm_dp_mst_topology_get_mstb_validated/
s/drm_dp_put_mst_branch_device/drm_dp_mst_topology_put_mstb/
This is a much more consistent naming
So that the ports stay around until we've destroyed the connectors, in
order to ensure that we don't pass an invalid pointer to any MST helpers
once we introduce the new MST VCPI helpers.
Changes since v1:
* Move drm_dp_mst_get_port_malloc() to where we assign
intel_connector->port - danvet
Going through the currently programmed payloads isn't safe without
holding mgr->payload_lock, so actually do that and warn if anyone tries
calling nv50_msto_payload() in the future without grabbing the right
locks.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc:
There is no need to look at the port's VCPI allocation before calling
drm_dp_mst_deallocate_vcpi(), as we already have msto->disabled to let
us avoid cleaning up an msto more then once. The DP MST core will never
call drm_dp_mst_deallocate_vcpi() on it's own, which is presumably what
these checks
While this isn't a complete fix, this will improve the reliability of
drm_dp_get_last_connected_port_and_mstb() pretty significantly during
hotplug events, since there's a chance that the in-memory topology tree
may not be fully updated when drm_dp_get_last_connected_port_and_mstb()
is called and
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
== Series Details ==
Series: series starting with [1/2] drm/i915/userptr: Avoid struct_mutex
recursion for mmu_invalidate_range_start
URL : https://patchwork.freedesktop.org/series/54869/
State : failure
== Summary ==
Patch is empty.
When you have resolved this problem, run "git am
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev10)
URL : https://patchwork.freedesktop.org/series/48194/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/execlists: Move RPCS setup to context pin
Okay!
Commit:
Hi,
On 07-01-19 16:46, Andy Shevchenko wrote:
On Mon, Jan 07, 2019 at 12:15:55PM +0100, Hans de Goede wrote:
Most PMIC-s use only a single i2c-address, so after verifying the
i2c-address matches, we can simply pass the call to regmap_update_bits.
This commit adds support for this and hooks
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev10)
URL : https://patchwork.freedesktop.org/series/48194/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378 -> Patchwork_11247
Summary
---
Quoting Tvrtko Ursulin (2019-01-08 13:22:52)
> From: Tvrtko Ursulin
>
> Exercise the context image reconfiguration logic for idle and busy
> contexts, with the resets thrown into the mix as well.
>
> Free from the uAPI restrictions this test runs on all Gen9+ platforms
> with slice power
Quoting Patchwork (2019-01-08 14:17:13)
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915: Enable render context support
> for Ironlake (gen5)
> URL : https://patchwork.freedesktop.org/series/54876/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes from
Quoting Chris Wilson (2019-01-08 13:06:37)
> diff --git a/drivers/gpu/drm/i915/intel_uc_fw.c
> b/drivers/gpu/drm/i915/intel_uc_fw.c
> index fd496416087c..ace8853e81b2 100644
> --- a/drivers/gpu/drm/i915/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/intel_uc_fw.c
> @@ -46,12 +46,17 @@ void
On 08/01/2019 13:58, Joonas Lahtinen wrote:
Quoting Tvrtko Ursulin (2019-01-08 13:22:52)
From: Tvrtko Ursulin
Exercise the context image reconfiguration logic for idle and busy
contexts, with the resets thrown into the mix as well.
Free from the uAPI restrictions this test runs on all Gen9+
== Series Details ==
Series: series starting with [1/2] drm/i915/gvt: give the cmd parser
decode_info a const treatment
URL : https://patchwork.freedesktop.org/series/54884/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
52fd4ad1e302 drm/i915/gvt: give the cmd parser
Quoting Tvrtko Ursulin (2019-01-08 13:24:50)
> From: Tony Ye
>
> On Icelake we need to turn off subslices not containing the VME block or
> the VME kernel will hang.
>
> v2: (Tvrtko Ursulin)
> * Remove libdrm usage for setting context param.
> * Cleanup bitmask operation.
> * Only apply the
Quoting Tvrtko Ursulin (2019-01-08 13:24:49)
> From: Tony Ye
>
> Simple test which exercises the VME fixed function block.
>
> v2: (Tvrtko Ursulin)
> * Small cleanups like copyright date, tabs, remove unused bits.
>
> v3: (Tony Ye)
> * Added curbe data entry for dst surface.
> * Read the
== Series Details ==
Series: drm/i915: Downgrade scare message for unknwown HuC firmware (rev4)
URL : https://patchwork.freedesktop.org/series/54868/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
010a74bc116c drm/i915: Downgrade scare message for unknown HuC firmware
-:10:
== Series Details ==
Series: Per context dynamic (sub)slice power-gating (rev10)
URL : https://patchwork.freedesktop.org/series/48194/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a76b08127cd7 drm/i915/execlists: Move RPCS setup to context pin
db8cb3bf4b10 drm/i915: Record
To be squashed to patch 3. We don't want a broken tree for bisecting.
When squashed:
Reviewed-by: Joonas Lahtinen
Regards, Joonas
Quoting Tvrtko Ursulin (2019-01-08 13:22:51)
> From: Tvrtko Ursulin
>
> When OA is active we want to lock the powergating configuration, but on
> Icelake, users
== Series Details ==
Series: Add HDR Metadata Parsing and handling in DRM layer (rev4)
URL : https://patchwork.freedesktop.org/series/25091/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5374_full -> Patchwork_11208_full
Currently blt-vs-render runs for a fixed loop count, and exceeds 360s
on a slow Skylake-y. It really doesn't tell us anything useful about low
likelihood events after the first few seconds it takes to fill memory,
so limit it to 30s (and hope that repeated runs in CI is enough to
exercise the even
On Tue, Jan 08, 2019 at 02:45:39PM +0100, Hans de Goede wrote:
> On 07-01-19 16:46, Andy Shevchenko wrote:
> > On Mon, Jan 07, 2019 at 12:15:55PM +0100, Hans de Goede wrote:
> > > + } else if (d->pmic_i2c_address) {
> > > + if (i2c_address == d->pmic_i2c_address) {
> > > +
Quoting Tvrtko Ursulin (2019-01-08 14:35:45)
>
> On 08/01/2019 14:22, Joonas Lahtinen wrote:
> > Quoting Tvrtko Ursulin (2019-01-08 13:22:50)
> >> +++ b/include/uapi/drm/i915_drm.h
> >> @@ -1486,9 +1486,52 @@ struct drm_i915_gem_context_param {
> >> #define I915_CONTEXT_MAX_USER_PRIORITY
If we haven't shipped and enabled firmware for a particular platform,
there is nothing the user can do about it. Don't scare the user with an
unactionable, unidentifiable warning!
<6> [310.769452] i915 :00:02.0: GuC: No firmware known for this platform!
<4> [310.769458] [drm] HuC: No firmware
Quoting Tvrtko Ursulin (2019-01-08 13:22:48)
> From: Lionel Landwerlin
>
> If some of the contexts submitting workloads to the GPU have been
> configured to shutdown slices/subslices, we might loose the NOA
> configurations written in the NOA muxes.
>
> One possible solution to this problem is
Hi,
On 07-01-19 16:35, Andy Shevchenko wrote:
On Mon, Jan 07, 2019 at 12:15:53PM +0100, Hans de Goede wrote:
DSI LCD panels describe an initialization sequence in the Video BIOS
Tables using so called MIPI sequences. One possible element in these
sequences is a PMIC specific element of 15
Hi Uma,
On Thu, Dec 27, 2018 at 11:22:37PM +0530, Uma Shankar wrote:
> This patch adds a colorspace connector property, enabling
> userspace to switch to various supported colorspaces.
> This will help enable BT2020 along with other colorspaces.
>
> v2: Addressed Maarten and Ville's review
== Series Details ==
Series: series starting with [1/2] drm/i915/userptr: Avoid struct_mutex
recursion for mmu_invalidate_range_start (rev2)
URL : https://patchwork.freedesktop.org/series/54869/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9900081d5714 drm/i915/userptr:
Quoting Tvrtko Ursulin (2019-01-08 11:24:47)
> From: Tvrtko Ursulin
Preemptive ack for the final copy.
Acked-by: Chris Wilson
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Tvrtko Ursulin (2019-01-08 13:24:48)
> From: Lionel Landwerlin
>
> Verify that the per-context dynamic SSEU uAPI works as expected.
>
> v2: Add subslice tests (Lionel)
> Use MI_SET_PREDICATE for further verification when available (Lionel)
>
> v3: Rename to gem_ctx_rpcs (Lionel)
>
On 08/01/2019 14:22, Joonas Lahtinen wrote:
Quoting Tvrtko Ursulin (2019-01-08 13:22:50)
From: Tvrtko Ursulin
We want to allow userspace to reconfigure the subslice configuration on a
per context basis.
This is required for the functional requirement of shutting down non-VME
enabled
== Series Details ==
Series: series starting with [1/2] drm/i915/userptr: Avoid struct_mutex
recursion for mmu_invalidate_range_start (rev2)
URL : https://patchwork.freedesktop.org/series/54869/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5378 -> Patchwork_11251
From: Tvrtko Ursulin
We want to allow userspace to reconfigure the subslice configuration on a
per context basis.
This is required for the functional requirement of shutting down non-VME
enabled sub-slices on Gen11 parts.
To do so, we expose a context parameter to allow adjustment of the RPCS
From: Tony Ye
On Icelake we need to turn off subslices not containing the VME block or
the VME kernel will hang.
v2: (Tvrtko Ursulin)
* Remove libdrm usage for setting context param.
* Cleanup bitmask operation.
* Only apply the workaround for ICL.
v3: (Tvrtko Ursulin)
* Added hang
From: Tvrtko Ursulin
Configuring RPCS in context image just before pin is sufficient and will
come extra handy in one of the following patches.
v2:
* Split image setup a bit differently. (Chris Wilson)
v3:
* Update context image after reset as well - otherwise the application
of pinned
From: Tvrtko Ursulin
Changes since last version:
* Squashed OA interaction patches into a single patch.
* Small tidy in selftest.
Lionel Landwerlin (2):
drm/i915: Record the sseu configuration per-context & engine
drm/i915/perf: lock powergating configuration to default when active
From: Lionel Landwerlin
If some of the contexts submitting workloads to the GPU have been
configured to shutdown slices/subslices, we might loose the NOA
configurations written in the NOA muxes.
One possible solution to this problem is to reprogram the NOA muxes
when we switch to a new context.
From: Tvrtko Ursulin
New in this version:
* Final tweaks based on review feedback.
Lionel Landwerlin (1):
tests/gem_ctx_sseu: Dynamic (sub)slice programming tests
Tony Ye (2):
tests/gem_media_vme: Simple test to exercise the VME block
tests/gem_media_vme: Shut down half of subslices to
From: Tony Ye
Simple test which exercises the VME fixed function block.
v2: (Tvrtko Ursulin)
* Small cleanups like copyright date, tabs, remove unused bits.
v3: (Tony Ye)
* Added curbe data entry for dst surface.
* Read the dst surface after the VME kernel being executed.
v4: (Tony Ye)
*
From: Tvrtko Ursulin
Sync with latest drm headers from drm-tip.
Acked-by: Chris Wilson
---
include/drm-uapi/drm_fourcc.h | 2 +-
include/drm-uapi/drm_mode.h | 19
include/drm-uapi/i915_drm.h | 43 +++
include/drm-uapi/msm_drm.h| 25
From: Tvrtko Ursulin
Exercise the context image reconfiguration logic for idle and busy
contexts, with the resets thrown into the mix as well.
Free from the uAPI restrictions this test runs on all Gen9+ platforms
with slice power gating.
v2:
* Rename some helpers for clarity.
* Include
From: Lionel Landwerlin
Verify that the per-context dynamic SSEU uAPI works as expected.
v2: Add subslice tests (Lionel)
Use MI_SET_PREDICATE for further verification when available (Lionel)
v3: Rename to gem_ctx_rpcs (Lionel)
v4: Update kernel API (Lionel)
Add 0 value test (Lionel)
From: Lionel Landwerlin
We want to expose the ability to reconfigure the slices, subslice and
eu per context and per engine. To facilitate that, store the current
configuration on the context for each engine, which is initially set
to the device default upon creation.
v2: record sseu
From: Tvrtko Ursulin
Timeline barrier allows serialization between different timelines.
After calling i915_timeline_set_barrier with a request, all following
submissions on this timeline will be set up as depending on this request,
or barrier. Once the barrier has been completed it
== Series Details ==
Series: series starting with [01/46] drm/i915: Return immediately if trylock
fails for direct-reclaim (rev3)
URL : https://patchwork.freedesktop.org/series/54803/
State : failure
== Summary ==
Applying: drm/i915: Return immediately if trylock fails for direct-reclaim
On 1/8/19 3:37 AM, Daniel Vetter wrote:
> On Tue, Jan 08, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the drm-misc tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In
Hi Uma,
On Thu, Dec 27, 2018 at 11:22:36PM +0530, Uma Shankar wrote:
> This patch series creates a new connector property to program
> colorspace to sink devices. Modern sink devices support more
> than 1 type of colorspace like 601, 709, BT2020 etc. This helps
> to switch based on content type
It doesn't need to be changed, make it const. The string literals should
anyway be referred to as const data.
The following gets moved to rodata section:
0080 l O .rodata1c00 cmd_info
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/gvt/cmd_parser.c | 24
It doesn't need to be changed, make it const. The string literals should
anyway be referred to as const data.
The following gets moved to rodata section:
0410 l O .rodata0018 decode_info_mi
0390 l O .rodata0018
1 - 100 of 191 matches
Mail list logo
