On Thu, Apr 18, 2019 at 02:27:58PM +0530, Ramalingam C wrote:
> On every hdcp revocation check request SRM is read from fw file
> /lib/firmware/display_hdcp_srm.bin
>
> SRM table is parsed and stored at drm_hdcp.c, with functions exported
> for the services for revocation check from drivers (which
On Thu, Apr 18, 2019 at 02:27:59PM +0530, Ramalingam C wrote:
> DRM HDCP SRM revocation check services are used from I915 for HDCP1.4
> and 2.2 revocation check during the respective authentication flow.
>
> v2:
> Rebased.
>
> Signed-off-by: Ramalingam C
> ---
> drivers/gpu/drm/i915/intel_hdc
On Thu, Apr 18, 2019 at 02:28:02PM +0530, Ramalingam C wrote:
> drm function is defined and exported to update a connector's
> content protection property state and to generate a uevent along
> with it.
>
> v2:
> Update only when state is different from old one.
>
> Signed-off-by: Ramalingam C
On Thu, Apr 18, 2019 at 02:28:03PM +0530, Ramalingam C wrote:
> drm function to update the content protection property state and to
> generate a uevent is invoked from the intel hdcp property work.
>
> Hence whenever kernel changes the property state, userspace will be
> updated with a uevent.
>
On Mon, Apr 29, 2019 at 09:26:07AM +0200, Daniel Vetter wrote:
> On Thu, Apr 18, 2019 at 02:27:58PM +0530, Ramalingam C wrote:
> > On every hdcp revocation check request SRM is read from fw file
> > /lib/firmware/display_hdcp_srm.bin
> >
> > SRM table is parsed and stored at drm_hdcp.c, with funct
On Thu, Apr 18, 2019 at 02:28:00PM +0530, Ramalingam C wrote:
> Considering the significant size of hdcp related code in drm, all
> hdcp related codes are moved into separate file called drm_hdcp.c.
>
> v2:
> Rebased.
>
> Signed-off-by: Ramalingam C
> Suggested-by: Daniel Vetter
> ---
> driv
On Thu, Apr 18, 2019 at 02:28:01PM +0530, Ramalingam C wrote:
> DRM API for generating uevent for a status changes of connector's
> property.
>
> This uevent will have following details related to the status change:
>
> HOTPLUG=1, CONNECTOR= and PROPERTY=
> v2:
> Minor fixes at KDoc comments
On Thu, Apr 18, 2019 at 02:28:04PM +0530, Ramalingam C wrote:
> This patch adds a optional CP downstream info blob property to the
> connectors. This enables the Userspace to read the information of HDCP
> authenticated downstream topology.
>
> Driver will update this blob with all downstream info
Do not treat reset as a normal preemption event and avoid giving the
guilty request a priority boost for simply being active at the time of
reset.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --gi
Currently we submit the semaphore busywait as soon as the signaler is
submitted to HW. However, we may submit the signaler as the tail of a
batch of requests, and even not as the first context in the HW list,
i.e. the busywait may start spinning far in advance of the signaler even
starting.
If we
When the system is idling, contention for struct_mutex should be low and
so we will be more efficient to wait for a contended mutex than
reschedule.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_gem_pm.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drive
If we couple the scheduler more tightly with the execlists policy, we
can apply the preemption policy to the question of whether we need to
kick the tasklet at all for this priority bump.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_request.c | 2 --
drivers/g
On Thu, 25 Apr 2019, Aditya Swarup wrote:
> From: Clinton Taylor
>
> v2: Fix commit msg to reflect why issue occurs(Jani)
> Set GCP_COLOR_INDICATION only when we set 10/12 bit deep color.
>
> Changing settings from 10/12 bit deep color to 8 bit(& vice versa)
> doesn't work correctly using xrandr
If the context has not been used yet, it needs no barrier, and in the
process fix up the selftest in mock_contexts.
Testcase: igt/gem_ctx_clone/vm
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_gem_context.c | 6 +++---
drivers/gpu/drm/i915/selftests/i915
On 4/26/2019 11:46 PM, Ville Syrjälä wrote:
On Fri, Apr 26, 2019 at 11:31:50PM +0530, Shashank Sharma wrote:
From: Uma Shankar
Add macros to define multi segmented gamma registers
Cc: Ville Syrjälä
Cc: Maarten Lankhorst
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/i915_reg.h | 17
Quoting Jani Nikula (2019-04-26 15:12:49)
> On Thu, 25 Apr 2019, Chris Wilson wrote:
> > For convenience in avoiding inline spaghetti, keep the type definition
> > as a separate header.
> >
> > Signed-off-by: Chris Wilson
> > Reviewed-by: Matthew Auld
> > ---
> > drivers/gpu/drm/i915/Makefile
On 29/04/2019 10:07, Chris Wilson wrote:
If the context has not been used yet, it needs no barrier, and in the
process fix up the selftest in mock_contexts.
Testcase: igt/gem_ctx_clone/vm
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_gem_context.c |
Quoting Xiaolin Zhang (2019-04-29 04:10:54)
> +static void pv_submit(struct intel_engine_cs *engine)
> +{
> + struct intel_engine_execlists * const execlists = &engine->execlists;
> + struct execlist_port *port = execlists->port;
> + unsigned int n;
> + struct gvt_shared_pag
== Series Details ==
Series: drm/i915: Skip unused contexts for context_barrier_task()
URL : https://patchwork.freedesktop.org/series/60037/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6011 -> Patchwork_12890
Summary
On 4/26/2019 11:59 PM, Ville Syrjälä wrote:
On Fri, Apr 26, 2019 at 11:31:51PM +0530, Shashank Sharma wrote:
ICL introduces a new gamma correction mode in display engine, called
multi-segmented-gamma mode. This mode allows users to program the
darker region of the gamma curve with sueprfine pre
== Series Details ==
Series: series starting with [1/4] drm/i915: Wait for the struct_mutex on idling
URL : https://patchwork.freedesktop.org/series/60048/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Wait for the struct_mutex on idling
Oka
On Mon, Apr 29, 2019 at 05:00:21PM +0530, Sharma, Shashank wrote:
>
> On 4/26/2019 11:59 PM, Ville Syrjälä wrote:
> > On Fri, Apr 26, 2019 at 11:31:51PM +0530, Shashank Sharma wrote:
> >> ICL introduces a new gamma correction mode in display engine, called
> >> multi-segmented-gamma mode. This mod
>-Original Message-
>From: Ville Syrjala [mailto:ville.syrj...@linux.intel.com]
>Sent: Friday, April 26, 2019 12:54 AM
>To: intel-gfx@lists.freedesktop.org
>Cc: Shankar, Uma
>Subject: [PATCH] drm/i915: Fix ICL output CSC programming
>
>From: Ville Syrjälä
>
>When I refactored the code i
== Series Details ==
Series: series starting with [1/4] drm/i915: Wait for the struct_mutex on idling
URL : https://patchwork.freedesktop.org/series/60048/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12891
===
Add more headers to the header test list:
* i915_drv.h
* i915_params.h
* i915_reg.h
* intel_drv.h
* intel_uncore.h
Happily they already are self-contained, but keep them that way.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 5 +
1 file changed, 5 insertions(+
Keep the header self-contained. It'll need rework of its own in the
future, but gotta start somewhere.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 1 +
drivers/gpu/drm/i915/intel_drv.h | 5 -
drivers/gpu/drm/i915/intel_dsi.h | 4
3 files
Put the header more in line with the rest. No functional changes.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 1 +
drivers/gpu/drm/i915/dvo_ch7017.c | 3 ++-
drivers/gpu/drm/i915/dvo_ch7xxx.c | 3 ++-
drivers/gpu/drm/i915/dvo_iv
And ensure it stays that way.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 1 +
drivers/gpu/drm/i915/intel_dpll_mgr.c | 1 +
drivers/gpu/drm/i915/intel_dpll_mgr.h | 8 ++--
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i9
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
i915_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the header remains self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
Work on the principle that files should prefer not to expose platform
specific functions.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_combo_phy.c | 24
drivers/gpu/drm/i915/intel_combo_phy.h | 6 ++
drivers/gpu/drm/i915/intel_runtime_pm.c | 10 +-
It used to be handy that we only had a couple of headers, but over time
i915_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minima
Commit 696173b064c6 ("drm/i915: extract intel_pm.h from intel_drv.h")
missed the declarations in i915_drv.h.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/i915_drv.h | 13 -
drivers/gpu/drm/i915/i915_pmu.c | 3 ++-
drivers/gpu/drm/i915/i915_sysfs.c | 3 ++-
drivers/gpu/dr
Just a types include required.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 1 +
drivers/gpu/drm/i915/intel_bios.h | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/Makefile.header-test
b/drivers/gpu/drm/i915/Makefile.header-test
i
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
Continue the header refactoring started in part one [1].
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/59022/
Jani Nikula (21):
drm/i915: ensure more headers remain self-contained
drm/i915: make intel_bios.h self-contained
drm/i915/dvo: rename dvo.h to intel_dvo_dev.h and make se
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
== Series Details ==
Series: i915 vgpu PV to improve vgpu performance
URL : https://patchwork.freedesktop.org/series/60055/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e9d42b5a1769 drm/i915: introduced vgpu pv capability
-:89: CHECK:PARENTHESIS_ALIGNMENT: Alignment should mat
== Series Details ==
Series: i915 vgpu PV to improve vgpu performance
URL : https://patchwork.freedesktop.org/series/60055/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: introduced vgpu pv capability
-drivers/gpu/drm/i915/selftests/../i915_d
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
On 4/29/2019 5:19 PM, Ville Syrjälä wrote:
On Mon, Apr 29, 2019 at 05:00:21PM +0530, Sharma, Shashank wrote:
On 4/26/2019 11:59 PM, Ville Syrjälä wrote:
On Fri, Apr 26, 2019 at 11:31:51PM +0530, Shashank Sharma wrote:
ICL introduces a new gamma correction mode in display engine, called
multi-
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev2)
URL : https://patchwork.freedesktop.org/series/60060/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
486873c042de drm/i915: ensure more headers remain self-contained
9067550af88f drm/i915: make
Quoting Jani Nikula (2019-04-29 13:29:37)
> Commit 696173b064c6 ("drm/i915: extract intel_pm.h from intel_drv.h")
> missed the declarations in i915_drv.h.
Fwiw, I want to pull these along with gt powermanagement and rps into
gt/intel_gt_pm.c and a few friends.
Doesn't make much difference for thi
== Series Details ==
Series: i915 vgpu PV to improve vgpu performance
URL : https://patchwork.freedesktop.org/series/60055/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12892
Summary
---
**SUCCESS*
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with minim
On Mon, 29 Apr 2019, Chris Wilson wrote:
> Quoting Jani Nikula (2019-04-29 13:29:37)
>> Commit 696173b064c6 ("drm/i915: extract intel_pm.h from intel_drv.h")
>> missed the declarations in i915_drv.h.
>
> Fwiw, I want to pull these along with gt powermanagement and rps into
> gt/intel_gt_pm.c and a
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev2)
URL : https://patchwork.freedesktop.org/series/60060/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: ensure more headers remain self-contained
-
+./include/u
If we couple the scheduler more tightly with the execlists policy, we
can apply the preemption policy to the question of whether we need to
kick the tasklet at all for this priority bump.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/selftest_lrc.c | 5 +
drive
== Series Details ==
Series: drm/i915: Skip unused contexts for context_barrier_task()
URL : https://patchwork.freedesktop.org/series/60037/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6011_full -> Patchwork_12890_full
Su
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev2)
URL : https://patchwork.freedesktop.org/series/60060/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12893
Summary
--
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev3)
URL : https://patchwork.freedesktop.org/series/60060/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2505cc046d89 drm/i915: ensure more headers remain self-contained
2519e59bfa55 drm/i915: make
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev3)
URL : https://patchwork.freedesktop.org/series/60060/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: ensure more headers remain self-contained
-
+./include/u
On 25/04/2019 10:19, Chris Wilson wrote:
Having allowed the user to define a set of engines that they will want
to only use, we go one step further and allow them to bind those engines
into a single virtual instance. Submitting a batch to the virtual engine
will then forward it to any one of the
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev3)
URL : https://patchwork.freedesktop.org/series/60060/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12894
Summary
--
== Series Details ==
Series: series starting with [1/4] drm/i915: Wait for the struct_mutex on
idling (rev2)
URL : https://patchwork.freedesktop.org/series/60048/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Wait for the struct_mutex on id
On Fri, 26 Apr 2019, Shashank Sharma wrote:
> From: Uma Shankar
>
> Add macros to define multi segmented gamma registers
>
> Cc: Ville Syrjälä
> Cc: Maarten Lankhorst
> Signed-off-by: Uma Shankar
> ---
> drivers/gpu/drm/i915/i915_reg.h | 17 +
> 1 file changed, 17 insertions(+
On 25/04/2019 10:19, Chris Wilson wrote:
Allow the user to direct which physical engines of the virtual engine
they wish to execute one, as sometimes it is necessary to override the
load balancing algorithm.
v2: Only kick the virtual engines on context-out if required
Signed-off-by: Chris Wils
Debug logging should not be dependent on alpha support flag.
Cc: Rodrigo Vivi
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_csr.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
index f43c2a2563a5..4527b9662330
== Series Details ==
Series: series starting with [1/4] drm/i915: Wait for the struct_mutex on
idling (rev2)
URL : https://patchwork.freedesktop.org/series/60048/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12895
===
On 2019-04-29 at 09:38:32 +0200, Daniel Vetter wrote:
> On Thu, Apr 18, 2019 at 02:28:04PM +0530, Ramalingam C wrote:
> > This patch adds a optional CP downstream info blob property to the
> > connectors. This enables the Userspace to read the information of HDCP
> > authenticated downstream topolo
== Series Details ==
Series: drm/i915/csr: alpha_support doesn't depend on csr or vice versa
URL : https://patchwork.freedesktop.org/series/60062/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12896
Summar
When CDCLK is as low as 79200, picture gets
unstable, while DSI and DE pll values were
confirmed to be correct.
Limiting to 158400 as agreed with Ville.
Signed-off-by: Stanislav Lisovskiy
---
drivers/gpu/drm/i915/intel_cdclk.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/
== Series Details ==
Series: drm/i915: Fix bug for GeminiLake
URL : https://patchwork.freedesktop.org/series/60065/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Fix bug for GeminiLake
-O:drivers/gpu/drm/i915/intel_cdclk.c:2266:29: warning:
Currently, the subslice_mask runtime parameter is stored as an
array of subslices per slice. Expand the subslice mask array to
better match what is presented to userspace through the
I915_QUERY_TOPOLOGY_INFO ioctl. The index into this array is
then calculated:
slice * subslice stride + subslice i
Subslice stride and EU stride are calculated multiple times in
i915_query. Move this calculation to a macro to reduce code duplication.
v2: update headers in intel_sseu.h
Cc: Daniele Ceraolo Spurio
Signed-off-by: Stuart Summers
---
drivers/gpu/drm/i915/gt/intel_sseu.h | 2 ++
drivers/gpu/drm/
Add a new function to return the number of subslices per slice to
consolidate code usage.
v2: rebase on changes to move sseu struct to intel_sseu.h
Cc: Daniele Ceraolo Spurio
Signed-off-by: Stuart Summers
---
drivers/gpu/drm/i915/gt/intel_sseu.h | 6 ++
drivers/gpu/drm/i915/i915_debugf
This patch series contains a few code clean-up patches, followed
by a patch which changes the storage of the subslice mask to better
match the userspace access through the I915_QUERY_TOPOLOGY_INFO
ioctl. The index into the subslice_mask array is then calculated:
slice * subslice stride + subslice
In the GETPARAM ioctl handler, use a local variable to consolidate
usage of SSEU runtime info.
Cc: Daniele Ceraolo Spurio
Signed-off-by: Stuart Summers
---
drivers/gpu/drm/i915/i915_drv.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_d
Signed-off-by: Stuart Summers
---
drivers/gpu/drm/i915/gt/intel_sseu.h | 47
drivers/gpu/drm/i915/intel_device_info.h | 47
2 files changed, 47 insertions(+), 47 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_sseu.h
b/drivers/gpu/dr
On Mon, Apr 29, 2019 at 06:10:23PM +0300, Stanislav Lisovskiy wrote:
> "drm/i915: Fix bug for GeminiLake"
The patch subject is rather generic.
With that improved
Acked-by: Ville Syrjälä
since we didn't managed to come up with a good explanation
for the failure.
PS. you cc:ed me on the wrong ad
On 25/04/2019 10:19, Chris Wilson wrote:
Some users require that when a master batch is executed on one particular
engine, a companion batch is run simultaneously on a specific slave
engine. For this purpose, we introduce virtual engine bonding, allowing
maps of master:slaves to be constructed t
== Series Details ==
Series: Refactor to expand subslice mask (rev4)
URL : https://patchwork.freedesktop.org/series/59742/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
0cad53dc6dba drm/i915: Use local variable for SSEU info in GETPARAM ioctl
da46929baac9 drm/i915: Add macro fo
== Series Details ==
Series: Refactor to expand subslice mask (rev4)
URL : https://patchwork.freedesktop.org/series/59742/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Use local variable for SSEU info in GETPARAM ioctl
Okay!
Commit: drm/i9
On Mon, Apr 29, 2019 at 05:22:53PM +0300, Jani Nikula wrote:
> Debug logging should not be dependent on alpha support flag.
>
> Cc: Rodrigo Vivi
> Signed-off-by: Jani Nikula
I agree... this is not the right way to track dependencies.
Reviewed-by: Rodrigo Vivi
> ---
> drivers/gpu/drm/i915/in
== Series Details ==
Series: drm/i915: Fix bug for GeminiLake
URL : https://patchwork.freedesktop.org/series/60065/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12897
Summary
---
**SUCCESS**
No
== Series Details ==
Series: Refactor to expand subslice mask (rev4)
URL : https://patchwork.freedesktop.org/series/59742/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012 -> Patchwork_12898
Summary
---
**SUCCESS**
== Series Details ==
Series: i915 vgpu PV to improve vgpu performance
URL : https://patchwork.freedesktop.org/series/60055/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12892_full
Summary
---
On Fri, Apr 12, 2019 at 07:51:47AM +0100, Chris Wilson wrote:
> SSEU reprogramming of the context introduced the notion of engine class
> and instance for a forwards compatible method of describing any engine
> beyond the old execbuf interface. We wish to adopt this class:instance
> description for
On Sun, Apr 28, 2019 at 10:57 PM Tvrtko Ursulin
wrote:
>
>
> On 26/04/2019 17:58, Anuj Phogat wrote:
> >
> > Joonas,
> >
> > Mesa now applies this WA on ICL and we're not seeing any regressions in CI.
> > I tested Mesa with and without this patch applied to kernel. I don't see
> > any
> > performa
== Series Details ==
Series: drm/i915: the great header refactoring, part two (rev3)
URL : https://patchwork.freedesktop.org/series/60060/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12894_full
Summ
On Mon, Apr 29, 2019 at 12:36:30PM +0300, Joonas Lahtinen wrote:
> Quoting Jani Nikula (2019-04-26 15:12:49)
> > On Thu, 25 Apr 2019, Chris Wilson wrote:
> > > For convenience in avoiding inline spaghetti, keep the type definition
> > > as a separate header.
> > >
> > > Signed-off-by: Chris Wilson
Do not treat reset as a normal preemption event and avoid giving the
guilty request a priority boost for simply being active at the time of
reset.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --gi
When the system is idling, contention for struct_mutex should be low and
so we will be more efficient to wait for a contended mutex than
reschedule.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_gem_pm.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drive
If we couple the scheduler more tightly with the execlists policy, we
can apply the preemption policy to the question of whether we need to
kick the tasklet at all for this priority bump.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/selftest_lrc.c | 7 ++-
dri
Currently we submit the semaphore busywait as soon as the signaler is
submitted to HW. However, we may submit the signaler as the tail of a
batch of requests, and even not as the first context in the HW list,
i.e. the busywait may start spinning far in advance of the signaler even
starting.
If we
Asking the GPU to busywait on a memory address, perhaps not unexpectedly
in hindsight for a shared system, leads to bus contention that affects
CPU programs trying to concurrently access memory. This can manifest as
a drop in transcode throughput on highly over-saturated workloads.
The only clue o
== Series Details ==
Series: series starting with [1/5] drm/i915: Wait for the struct_mutex on idling
URL : https://patchwork.freedesktop.org/series/60072/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Wait for the struct_mutex on idling
Oka
== Series Details ==
Series: series starting with [1/4] drm/i915: Wait for the struct_mutex on
idling (rev2)
URL : https://patchwork.freedesktop.org/series/60048/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12895_full
=
== Series Details ==
Series: drm/i915/csr: alpha_support doesn't depend on csr or vice versa
URL : https://patchwork.freedesktop.org/series/60062/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12896_full
==
== Series Details ==
Series: drm/i915: Fix bug for GeminiLake
URL : https://patchwork.freedesktop.org/series/60065/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12897_full
Summary
---
**FAILUR
== Series Details ==
Series: Refactor to expand subslice mask (rev4)
URL : https://patchwork.freedesktop.org/series/59742/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6012_full -> Patchwork_12898_full
Summary
---
*
1 - 100 of 111 matches
Mail list logo
