Please ignore this patch. Not sure why only one patch landed in the
mailing list. I will resend.
Umesh
On Sat, Oct 19, 2019 at 09:58:21PM -0700, Umesh Nerlige Ramappa wrote:
Add helper macros for range and equality comparisons and use them to
check with whitelisted registers in oa
Add helper macros for range and equality comparisons and use them to
check with whitelisted registers in oa configurations.
Signed-off-by: Umesh Nerlige Ramappa
Reviewed-by: Lionel Landwerlin
---
drivers/gpu/drm/i915/i915_perf.c | 54 +---
1 file changed, 28
== Series Details ==
Series: drm/i915: Extract GT ring management
URL : https://patchwork.freedesktop.org/series/68270/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7135_full -> Patchwork_14894_full
Summary
---
== Series Details ==
Series: drm/i915: Extract GT ring management
URL : https://patchwork.freedesktop.org/series/68270/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7135 -> Patchwork_14894
Summary
---
**SUCCESS**
== Series Details ==
Series: drm/i915: Extract GT ring management
URL : https://patchwork.freedesktop.org/series/68270/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
899278bfd3d3 drm/i915: Extract GT ring management
-:48: WARNING:FILE_PATH_CHANGES: added, moved or deleted
From: Andi Shyti
Although the ring management is much smaller compared to the other GT
power management functions, continue the theme of extracting it out of
the huge intel_pm.c for maintenance.
Based on a patch by Chris Wilson.
Signed-off-by: Andi Shyti
Cc: Chris Wilson
---
== Series Details ==
Series: drm/i915/perf: fix oa config reconfiguration
URL : https://patchwork.freedesktop.org/series/68261/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7134_full -> Patchwork_14893_full
Summary
== Series Details ==
Series: drm/i915/perf: fix oa config reconfiguration
URL : https://patchwork.freedesktop.org/series/68261/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7134 -> Patchwork_14893
Summary
---
The current logic just reapplies the same configuration already stored
into stream->oa_config instead of the newly selected one.
Signed-off-by: Lionel Landwerlin
Fixes: 7831e9a965ea ("drm/i915/perf: Allow dynamic reconfiguration of the OA
stream")
Cc: Chris Wilson
---
== Series Details ==
Series: drm/i915: Drop assertion that ce->pin_mutex guards state updates
URL : https://patchwork.freedesktop.org/series/68252/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7133_full -> Patchwork_14892_full
== Series Details ==
Series: drm/i915: Drop assertion that ce->pin_mutex guards state updates
URL : https://patchwork.freedesktop.org/series/68252/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7133 -> Patchwork_14892
On Sat, Oct 19, 2019 at 02:59:14AM +0300, Souza, Jose wrote:
> On Thu, 2019-10-03 at 17:50 +0300, Imre Deak wrote:
> > On Mon, Sep 30, 2019 at 05:55:36PM -0700, José Roberto de Souza
> > wrote:
> > > This is required for legacy/static TC ports as IOM is not aware of
> > > the connection and will
The actual conditions are that we know the GPU is not accessing the
context, and we hold a pin on the context image to allow CPU access. We
used a fake lock on ce->pin_mutex so that we could try and use lockdep
to assert that access is serialised, but the various different
hardirq/softirq contexts
== Series Details ==
Series: series starting with [1/3] i915: Exercise preemption timeout controls
in sysfs
URL : https://patchwork.freedesktop.org/series/68251/
State : warning
== Summary ==
Did not get list of undocumented tests for this run, something is wrong!
Other than that, pipeline
We [will] expose various per-engine scheduling controls. One of which,
'preempt_timeout_ms', defines how we wait for a preemption request to be
honoured by the currently executing context. If it fails to relieve the
GPU within the required timeout, the engine is reset and the miscreant
forcibly
We [will] expose various per-engine scheduling controls. One of which,
'timeslice_duration_ms', defines the scheduling quantum. If a context
exhausts its timeslice, it will be preempted in favour of running one of
its compatriots.
Signed-off-by: Chris Wilson
---
tests/Makefile.sources
We [will] expose various per-engine scheduling controls. One of which,
'heartbeat_duration_ms', defines how often we send a heartbeat down the
engine to check upon the health of the engine. If a heartbeat does not
complete within the interval (or two), the engine is declared hung.
Signed-off-by:
On 19/10/2019 02:22, Chris Wilson wrote:
Quoting Umesh Nerlige Ramappa (2019-10-18 01:50:27)
From: Lionel Landwerlin
We want this so we can preempt performance queries and keep the system
responsive even when long running queries are ongoing. We avoid doing
it for all contexts.
v2: use LRI
18 matches
Mail list logo
