Since the PWM framework is switching struct pwm_state.duty_cycle's
datatype to u64, prepare for this transition by using DIV_ROUND_UP_ULL
to handle a 64-bit dividend.
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: David Airlie
Cc: Daniel Vetter
Cc: Chris Wilson
Cc: "Ville Syrjälä"
Cc:
Because period and duty cycle are defined in the PWM framework structs as ints
with units of nanoseconds, the maximum time duration that can be set is limited
to ~2.147 seconds. Consequently, applications desiring to set greater time
periods via the PWM framework are not be able to do so - like,
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev5)
URL : https://patchwork.freedesktop.org/series/74759/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8144_full -> Patchwork_17001_full
== Series Details ==
Series: drm/i915/tgl: Add new PCI IDs to TGL
URL : https://patchwork.freedesktop.org/series/74795/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8144_full -> Patchwork_17000_full
Summary
---
== Series Details ==
Series: drm/i915/gt: Always reschedule the new heartbeat
URL : https://patchwork.freedesktop.org/series/74791/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8143_full -> Patchwork_16998_full
Summary
On 16/03/2020 21:23, Dixit, Ashutosh wrote:
On Thu, 12 Mar 2020 16:04:59 -0700, Umesh Nerlige Ramappa wrote:
From: Lionel Landwerlin
We're about to introduce an options to open the perf stream, giving
the user ability to configure how often it wants the kernel to poll
the OA registers for
On Tue, 2020-03-10 at 14:42 -0700, Francisco Jerez wrote:
> This implements a simple variably low-pass-filtering governor in
> control of the HWP MIN/MAX PERF range based on the previously
> introduced get_vlp_target_range(). See "cpufreq: intel_pstate:
> Implement VLP controller target P-state
== Series Details ==
Series: drm/i915: Fix up documentation paths after file moving
URL : https://patchwork.freedesktop.org/series/74778/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8142_full -> Patchwork_16997_full
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev3)
URL : https://patchwork.freedesktop.org/series/74759/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8142_full -> Patchwork_16996_full
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev5)
URL : https://patchwork.freedesktop.org/series/74759/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8144 -> Patchwork_17001
== Series Details ==
Series: drm/i915/tgl: Add new PCI IDs to TGL
URL : https://patchwork.freedesktop.org/series/74795/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8144 -> Patchwork_17000
Summary
---
**SUCCESS**
== Series Details ==
Series: drm/i915/color: Extract icl_read_luts()
URL : https://patchwork.freedesktop.org/series/74777/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8142_full -> Patchwork_16995_full
Summary
---
As we store the handle lookup inside a radix tree, we do not need the
gem_context->mutex except until we need to insert our lookup into the
common radix tree. This takes a small bit of rearranging to ensure that
the lut we insert into the tree is ready prior to actually inserting it
(as soon as it
Adding 4 new PCI IDs to TGL
Bspec: 44455
Signed-off-by: Swathi Dhanavanthri
---
include/drm/i915_pciids.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
index 1d2c12219f44..c299e26c99c5 100644
---
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev4)
URL : https://patchwork.freedesktop.org/series/74759/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8144 -> Patchwork_16999
As we store the handle lookup inside a radix tree, we do not need the
gem_context->mutex except until we need to insert our lookup into the
common radix tree. This takes a small bit of rearranging to ensure that
the lut we insert into the tree is ready prior to actually inserting it
(as soon as it
Hi
Please test with drm-tip and file a bug attaching more information
and logs:
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
On Tue, 2020-03-17 at 18:56 +, Damian Hischier wrote:
> Hello
>
> I installed opensuse Tumbleweed linux on a brand new Dell XPS-13-
> 7390.
Hello
I installed opensuse Tumbleweed linux on a brand new Dell XPS-13-7390. Already
during the installation, the screen started to flicker. Then I installed
opensuse 15.1 on the same laptop and it worked without screen flickering. But
after I run the online update it started to flicker again.
== Series Details ==
Series: Revert "drm/i915/gem: Drop relocation slowpath"
URL : https://patchwork.freedesktop.org/series/74771/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8141_full -> Patchwork_16993_full
Summary
== Series Details ==
Series: drm/i915/gt: Always reschedule the new heartbeat
URL : https://patchwork.freedesktop.org/series/74791/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8143 -> Patchwork_16998
Summary
---
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev2)
URL : https://patchwork.freedesktop.org/series/74759/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8141_full -> Patchwork_16991_full
On Sat, 14 Mar 2020, Anshuman Gupta wrote:
> Few edp panels like Sharp is triggering short and long
> hpd pulse after panel is getting powered off.
> Currently driver is already ignoring long pulse for eDP
> panel but in order to process the short pulse, it turns on
> the VDD which requires panel
== Series Details ==
Series: series starting with [v7,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74767/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8141_full -> Patchwork_16990_full
Quoting Tvrtko Ursulin (2020-03-17 16:50:02)
>
> On 17/03/2020 16:32, Chris Wilson wrote:
> > In order to better respond to new heartbeat intervals given via sysfs,
> > always reprogramme an active heartbeat upon change (i.e. use
> > mod_delayed_work to reschedule rather than queue_delayed_work
On 17/03/2020 16:32, Chris Wilson wrote:
In order to better respond to new heartbeat intervals given via sysfs,
always reprogramme an active heartbeat upon change (i.e. use
mod_delayed_work to reschedule rather than queue_delayed_work which
ignores an already active work.)
Signed-off-by:
In order to better respond to new heartbeat intervals given via sysfs,
always reprogramme an active heartbeat upon change (i.e. use
mod_delayed_work to reschedule rather than queue_delayed_work which
ignores an already active work.)
Signed-off-by: Chris Wilson
---
On Tue, 2020-03-17 at 13:59 +, Vudum, Lakshminarayana wrote:
> I had to re-report more than once as there were many issues. All good now.
Thank you :-)
Janusz
>
> Thanks,
> Lakshmi.
> -Original Message-
> From: Latvala, Petri
> Sent: Tuesday, March 17, 2020 12:40 PM
> To: Janusz
== Series Details ==
Series: drm/i915: Fix up documentation paths after file moving
URL : https://patchwork.freedesktop.org/series/74778/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8142 -> Patchwork_16997
Summary
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev3)
URL : https://patchwork.freedesktop.org/series/74759/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8142 -> Patchwork_16996
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev3)
URL : https://patchwork.freedesktop.org/series/74759/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
== Series Details ==
Series: drm/i915/color: Extract icl_read_luts()
URL : https://patchwork.freedesktop.org/series/74777/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8142 -> Patchwork_16995
Summary
---
== Series Details ==
Series: drm/i915/color: Extract icl_read_luts()
URL : https://patchwork.freedesktop.org/series/74777/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
Error: Cannot open file
>-Original Message-
>From: Intel-gfx On Behalf Of Chris
>Wilson
>Sent: Tuesday, March 17, 2020 8:27 AM
>To: intel-gfx@lists.freedesktop.org
>Subject: [Intel-gfx] [PATCH 02/12] drm/i915: Wrap i915_active in a simple
>kreffed struct
>
>For conveniences of callers that just want to use an
Hi,
Here is what should be the final drm-misc-next PR for 5.7.
Maxime
drm-misc-next-2020-03-17:
drm-misc-next for 5.7:
UAPI Changes:
Cross-subsystem Changes:
Core Changes:
- dp-mst: Remove register_connector callback, add drm_dp_destroy_connector
- Changes to scnprintf on multiple
== Series Details ==
Series: drm/i915/color: Extract icl_read_luts()
URL : https://patchwork.freedesktop.org/series/74777/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
af4d857eacf3 drm/i915/color: Extract icl_read_luts()
-:29: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped
>Something like?
>for_each_plane_id() {
> for_each_dbuf_slice() {
> skl_ddb_entry_for_slices(BIT(slice), _slice);
>
>if (skl_ddb_entries_overlap(_slice, [plane_id])))
> bw[slice] += data_rate;
>}
>}
In fact even in your example
== Series Details ==
Series: series starting with [v8,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74773/
State : failure
== Summary ==
Applying: drm/i915/perf: remove generated code
Using index info to reconstruct a base tree...
M
Redirect references to i915_gem_fence_reg.c to gt/intel_ggtt_fencing.c
Fixes: dec9cf9ee8cb ("drm/i915/gt: Pull restoration of GGTT fences underneath
the GT")
Signed-off-by: Chris Wilson
Reviewed-by: Mika Kuoppala
---
Documentation/gpu/i915.rst | 6 +++---
1 file changed, 3 insertions(+), 3
As we store the handle lookup inside a radix tree, we do not need the
gem_context->mutex except until we need to insert our lookup into the
common radix tree. This takes a small bit of rearranging to ensure that
the lut we insert into the tree is ready prior to actually inserting it
(as soon as it
== Series Details ==
Series: Revert "drm/i915/gem: Drop relocation slowpath"
URL : https://patchwork.freedesktop.org/series/74771/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8141 -> Patchwork_16993
Summary
---
I had to re-report more than once as there were many issues. All good now.
Thanks,
Lakshmi.
-Original Message-
From: Latvala, Petri
Sent: Tuesday, March 17, 2020 12:40 PM
To: Janusz Krzysztofik ; Vudum,
Lakshminarayana
Cc: igt-...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
== Series Details ==
Series: Revert "drm/i915/gem: Drop relocation slowpath"
URL : https://patchwork.freedesktop.org/series/74771/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
Error: Cannot open
the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-gem-Avoid-gem_context-mutex-for-simple-vma-lookup/20200317-110430
base: git
For icl+, have hw read out to create hw blob of gamma
lut values. icl+ platforms supports multi segmented gamma
mode by default, add hw lut creation for this mode.
This will be used to validate gamma programming using dsb
(display state buffer) which is a tgl specific feature.
v2: -readout code
On Tue, Mar 17, 2020 at 12:43:38AM +0200, Stanislav Lisovskiy wrote:
> According to BSpec max BW per slice is calculated using formula
> Max BW = CDCLK * 64. Currently when calculating min CDCLK we
> account only per plane requirements, however in order to avoid
> FIFO underruns we need to
== Series Details ==
Series: Revert "drm/i915/gem: Drop relocation slowpath"
URL : https://patchwork.freedesktop.org/series/74771/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d42d74d4a36d Revert "drm/i915/gem: Drop relocation slowpath"
-:78: WARNING:LINE_SPACING: Missing a
== Series Details ==
Series: series starting with [01/12] drm/i915/selftests: Add request throughput
measurement to perf
URL : https://patchwork.freedesktop.org/series/74769/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8141 -> Patchwork_16992
== Series Details ==
Series: series starting with [01/12] drm/i915/selftests: Add request throughput
measurement to perf
URL : https://patchwork.freedesktop.org/series/74769/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file
The caller of i915_oa_init_reg_state() already sets this.
Signed-off-by: Lionel Landwerlin
Reviewed-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_perf.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index
A little bit of history :
Back when i915-perf was introduced (4.13), there was no way to
dynamically add new OA configurations to i915. Only the generated
configs baked in at build time were allowed.
It quickly became obvious that we would need to allow applications
to upload
On Gen11 powergating half the execution units is a functional
requirement when using the VME samplers. Not fullfilling this
requirement can lead to hangs.
This unfortunately plays fairly poorly with the NOA requirements. NOA
requires a stable power configuration to maintain its configuration.
As
On Mon, Mar 16, 2020 at 01:37:42PM +0200, Stanislav Lisovskiy wrote:
> We need to calculate cdclk after watermarks/ddb has been calculated
> as with recent hw CDCLK needs to be adjusted accordingly to DBuf
> requirements, which is not possible with current code organization.
>
> Setting CDCLK
== Series Details ==
Series: series starting with [01/12] drm/i915/selftests: Add request throughput
measurement to perf
URL : https://patchwork.freedesktop.org/series/74769/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
0d574449054f drm/i915/selftests: Add request throughput
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev2)
URL : https://patchwork.freedesktop.org/series/74759/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8141 -> Patchwork_16991
Op 17-03-2020 om 13:38 schreef Chris Wilson:
> Quoting Maarten Lankhorst (2020-03-17 12:35:46)
>> This reverts commit 7dc8f1143778 ("drm/i915/gem: Drop relocation
>> slowpath"). We need the slowpath relocation for taking ww-mutex
>> inside the page fault handler, and we will take this mutex when
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup (rev2)
URL : https://patchwork.freedesktop.org/series/74759/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
Quoting Maarten Lankhorst (2020-03-17 12:35:46)
> This reverts commit 7dc8f1143778 ("drm/i915/gem: Drop relocation
> slowpath"). We need the slowpath relocation for taking ww-mutex
> inside the page fault handler, and we will take this mutex when
> pinning all objects.
Don't hold an exclusive
This reverts commit 7dc8f1143778 ("drm/i915/gem: Drop relocation
slowpath"). We need the slowpath relocation for taking ww-mutex
inside the page fault handler, and we will take this mutex when
pinning all objects.
Cc: Chris Wilson
Cc: Matthew Auld
Signed-off-by: Maarten Lankhorst
---
== Series Details ==
Series: series starting with [v7,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74767/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8141 -> Patchwork_16990
Allow the callers to supply a dma-fence-proxy for asynchronous waiting on
future fences.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/drm_syncobj.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
index
Often we need to create a fence for a future event that has not yet been
associated with a fence. We can store a proxy fence, a placeholder, in
the timeline and replace it later when the real fence is known. Any
listeners that attach to the proxy fence will automatically be signaled
when the real
Fixes: a88b6e4cbafd ("drm/i915: Allow specification of parallel execbuf")
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Lionel Landwerlin
---
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 10 +++---
include/uapi/drm/i915_drm.h| 7 ---
2 files changed, 11
For conveniences of callers that just want to use an i915_active to
track a wide array of concurrent timelines, wrap the base i915_active
struct inside a kref. This i915_active will self-destruct after use.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
Reviewed-by: Mika Kuoppala
---
Inside dma-fence-chain, we use a cmpxchg on an RCU-protected pointer. To
avoid the sparse warning for using the RCU pointer directly, we have to
cast away the __rcu annotation. However, we don't need to use void*
everywhere and can stick to the dma_fence*.
Signed-off-by: Chris Wilson
A few very simple testcases to exercise the dma-fence-chain API.
Signed-off-by: Chris Wilson
---
drivers/dma-buf/Makefile | 3 +-
drivers/dma-buf/selftests.h | 1 +
drivers/dma-buf/st-dma-fence-chain.c | 713 +++
3 files changed, 716
Let userspace know if they can trust timeslicing by including it as part
of the I915_PARAM_HAS_SCHEDULER::I915_SCHEDULER_CAP_TIMESLICING
v2: Only declare timeslicing if we can safely preempt userspace.
Fixes: 8ee36e048c98 ("drm/i915/execlists: Minimalistic timeslicing")
Signed-off-by: Chris
If we find ourselves waiting on a MI_SEMAPHORE_WAIT, either within the
user batch or in our own preamble, the engine raises a
GT_WAIT_ON_SEMAPHORE interrupt. We can unmask that interrupt and so
respond to a semaphore wait by yielding the timeslice, if we have
another context to yield to!
The only
Under ideal circumstances, the driver should be able to keep the GPU
fully saturated with work. Measure how close to ideal we get under the
harshest of conditions with no user payload.
v2: Also measure throughput using only one thread.
Signed-off-by: Chris Wilson
---
Whenever we walk along the dma-fence-chain, we prune signaled links to
keep the chain nice and tidy. This leads to situations where we can
prune a link and report the earlier fence as the target seqno --
violating our own consistency checks that the seqno is not more advanced
than the last element
We wish that the scheduler emit the context modification commands prior
to enabling the oa_config, for which we must explicitly inform it of the
ordering constraints. This is especially important as we now wait for
the final oa_config setup to be completed and as this wait may be on a
distinct
If a syncobj has not yet been assigned, treat it as a future fence and
install and wait upon a dma-fence-proxy. The proxy will be replace by
the real fence later, and that fence will be responsible for signaling
our waiter.
Signed-off-by: Chris Wilson
---
As we store the handle lookup inside a radix tree, we do not need the
gem_context->mutex except until we need to insert our lookup into the
common radix tree. This takes a small bit of rearranging to ensure that
the lut we insert into the tree is ready prior to actually inserting it
(as soon as it
== Series Details ==
Series: series starting with [v7,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74767/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
== Series Details ==
Series: series starting with [v7,1/3] drm/i915/perf: remove generated code
URL : https://patchwork.freedesktop.org/series/74767/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
dfa8113ae277 drm/i915/perf: remove generated code
-:24:
On Gen11 powergating half the execution units is a functional
requirement when using the VME samplers. Not fullfilling this
requirement can lead to hangs.
This unfortunately plays fairly poorly with the NOA requirements. NOA
requires a stable power configuration to maintain its configuration.
As
The caller of i915_oa_init_reg_state() already sets this.
Signed-off-by: Lionel Landwerlin
Reviewed-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_perf.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index
A little bit of history :
Back when i915-perf was introduced (4.13), there was no way to
dynamically add new OA configurations to i915. Only the generated
configs baked in at build time were allowed.
It quickly became obvious that we would need to allow applications
to upload
== Series Details ==
Series: Dynamic EU configuration of Slice/Sub-slice/EU (rev8)
URL : https://patchwork.freedesktop.org/series/69980/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
Error: Cannot open file ./drivers/gpu/drm/i915/i915_gem_fence_reg.c
Error: Cannot
== Series Details ==
Series: Dynamic EU configuration of Slice/Sub-slice/EU (rev8)
URL : https://patchwork.freedesktop.org/series/69980/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8141 -> Patchwork_16989
Summary
---
== Series Details ==
Series: Dynamic EU configuration of Slice/Sub-slice/EU (rev8)
URL : https://patchwork.freedesktop.org/series/69980/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.6.0
Commit: drm/i915: Get active pending request for given context
Okay!
== Series Details ==
Series: Dynamic EU configuration of Slice/Sub-slice/EU (rev8)
URL : https://patchwork.freedesktop.org/series/69980/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
bb031637fc75 drm/i915: Get active pending request for given context
-:95:
== Series Details ==
Series: drm/i915/gem: Avoid gem_context->mutex for simple vma lookup
URL : https://patchwork.freedesktop.org/series/74759/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8139_full -> Patchwork_16988_full
What is this weird DOC warning about? "Error: Cannot open file
./drivers/gpu/drm/i915/i915_gem_fence_reg.c"
- wondering, how is that related to this patch.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Lakshmi, see below.
On Tue, Mar 17, 2020 at 09:53:51AM +0100, Janusz Krzysztofik wrote:
> Hi,
>
> On Mon, 2020-03-16 at 19:25 +, Patchwork wrote:
> > == Series Details ==
> >
> > Series: tests/gem_userptr_blits: Refresh other now MMAP_GTT dependent
> > subtests (rev2)
> > URL :
On 16/03/2020 20:46, Umesh Nerlige Ramappa wrote:
Looks good. Thanks for cleaning this up.
With s/mutex_lock/mutex_unlock/ below:
Reviewed-by: Umesh Nerlige Ramappa
Thanks,
Umesh
On Sat, Mar 14, 2020 at 12:33:29PM +0200, Lionel Landwerlin wrote:
A little bit of history :
Back when
On 17/03/2020 00:16, Dixit, Ashutosh wrote:
On Thu, 12 Mar 2020 16:05:01 -0700, Umesh Nerlige Ramappa wrote:
From: Lionel Landwerlin
The only bit of the status register we currently report in the
i915-perf stream is the "report loss" bit. Only report this when we
have some data to report with
Load classification is used for predictive governor to control
eu/slice/subslice based on workloads.
sysfs is provided to enable/disable the feature
V2:
* Fix code style.
* Move predictive_load_timer into a drm_i915_private
structure.
* Make generic function to set optimum config. (Tvrtko
This patch gives us the active pending request count which is yet
to be submitted to the GPU.
V2:
* Change 64-bit to atomic for request count. (Tvrtko Ursulin)
V3:
* Remove mutex for request count.
* Rebase.
* Fixes hitting underflow for predictive request. (Tvrtko Ursulin)
V4:
* Rebase.
This patch will select optimum eu/slice/sub-slice configuration based on
type of load (low, medium, high) as input.
Based on our readings and experiments we have predefined set of optimum
configuration for each platform(CHT, KBL).
i915_gem_context_set_load_type will select optimum configuration
drm/i915: Context aware user agnostic EU/Slice/Sub-slice control within kernel
This patch sets improves GPU power consumption on Linux kernel based OS such as
Chromium OS, Ubuntu, etc. Following are the power savings.
Power savings on GLK-GT1 Bobba platform running on Chrome OS.
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev2)
URL : https://patchwork.freedesktop.org/series/74739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8138_full -> Patchwork_16987_full
Hi,
On Mon, 2020-03-16 at 19:25 +, Patchwork wrote:
> == Series Details ==
>
> Series: tests/gem_userptr_blits: Refresh other now MMAP_GTT dependent
> subtests (rev2)
> URL : https://patchwork.freedesktop.org/series/74201/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes
== Series Details ==
Series: drm/i915/gt: Restore check for invalid vma for fencing
URL : https://patchwork.freedesktop.org/series/74758/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8138_full -> Patchwork_16985_full
On 16/03/2020 16:14, Chris Wilson wrote:
Beware that the context may already be closed as we try to lookup an
engine.
Closes: https://gitlab.freedesktop.org/drm/intel/issues/1389
Fixes: 130a95e9098e ("drm/i915/gem: Consolidate ctx->engines[] release")
Signed-off-by: Chris Wilson
Cc: Tvrtko
== Series Details ==
Series: drm/i915/gem: Check for a closed context when looking up an engine
URL : https://patchwork.freedesktop.org/series/74750/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8138_full -> Patchwork_16984_full
== Series Details ==
Series: Add support for mipi dsi cmd mode (rev8)
URL : https://patchwork.freedesktop.org/series/69290/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8138_full -> Patchwork_16982_full
Summary
---
96 matches
Mail list logo
