On 26/03/2019 18:57, Chris Wilson wrote:
Even with 128MiB reserved for other use, a single pass of gem_exec_big
runs out of memory. Give in and halve our batch size, that has to be
enough slack! As to why it keeps on failing, is left as an exercise to
the reader -- we have to solve the mm/ myste
== Series Details ==
Series: drm/i915: Update size upon return from GEM_CREATE (rev2)
URL : https://patchwork.freedesktop.org/series/58592/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5818_full -> Patchwork_12604_full
Sum
== Series Details ==
Series: drm/i915: Only reset the pinned kernel contexts on resume
URL : https://patchwork.freedesktop.org/series/58589/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5818_full -> Patchwork_12603_full
Su
== Series Details ==
Series: series starting with [1/2] drm/i915: Do not enable FEC without DSC
URL : https://patchwork.freedesktop.org/series/58588/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818_full -> Patchwork_12602_full
===
Hi all,
After merging the drm-intel tree, today's linux-next build (i386
defconfig) failed like this:
In file included from drivers/gpu/drm/i915/intel_guc.h:28:0,
from drivers/gpu/drm/i915/intel_uc.h:27,
from drivers/gpu/drm/i915/intel_uc.c:25:
drivers/gpu/drm/i9
== Series Details ==
Series: series starting with [v2,1/6] drm/i915: Add broadcast RGB property for
DP MST
URL : https://patchwork.freedesktop.org/series/58585/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818_full -> Patchwork_12601_full
===
On Mon, 2019-03-25 at 10:00 +, Tvrtko Ursulin wrote:
> On 22/03/2019 23:41, Carlos Santa wrote:
> > From: Michel Thierry
> >
> > *** General ***
> >
> > Watchdog timeout (or "media engine reset") is a feature that allows
> > userland applications to enable hang detection on individual batch
== Series Details ==
Series: series starting with [01/21] drm/fb-helper: Add fill_info() functions
URL : https://patchwork.freedesktop.org/series/58578/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818_full -> Patchwork_12600_full
== Series Details ==
Series: drm/i915: fix i386 build of 64b raw_uncore functions
URL : https://patchwork.freedesktop.org/series/58611/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5819 -> Patchwork_12610
Summary
---
Quoting Daniele Ceraolo Spurio (2019-03-26 23:38:17)
> When building with ARCH=i386, readq and writeq are not defined,
> resulting in:
>
> intel_uncore.h: In function ‘__raw_uncore_read64’:
> intel_uncore.h:257:9: error: implicit declaration of function ‘readq’;
> did you mean ‘readl’? [-W
== Series Details ==
Series: drm/i915/icl: Fix VEBOX mismatch BUG_ON()
URL : https://patchwork.freedesktop.org/series/58609/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5819 -> Patchwork_12609
Summary
---
**SUCCESS
When building with ARCH=i386, readq and writeq are not defined,
resulting in:
intel_uncore.h: In function ‘__raw_uncore_read64’:
intel_uncore.h:257:9: error: implicit declaration of function ‘readq’;
did you mean ‘readl’? [-Werror=implicit-function-declaration]
return read##s__(uncore->r
Quoting José Roberto de Souza (2019-03-26 23:02:23)
> GT VEBOX DISABLE is only 4 bits wide but it was using a 8 bits wide
> mask, the remaning reserved bits is set to 0 causing 4 more
> nonexistent VEBOX engines being detected as enabled, triggering the
> BUG_ON() because of mismatch between vebox_
== Series Details ==
Series: Device id consolidation
URL : https://patchwork.freedesktop.org/series/58561/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5817_full -> Patchwork_12599_full
Summary
---
**FAILURE**
Se
GT VEBOX DISABLE is only 4 bits wide but it was using a 8 bits wide
mask, the remaning reserved bits is set to 0 causing 4 more
nonexistent VEBOX engines being detected as enabled, triggering the
BUG_ON() because of mismatch between vebox_mask and newly added
VEBOX_MASK().
[ 64.081621] [drm:inte
Hi Ville.
On Tue, Mar 26, 2019 at 07:34:00PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.name is only ever set by a few panel drveirs but
drivers
Nice clean-up!
Sam
__
Quoting Michal Wajdeczko (2019-03-26 12:47:00)
> On Mon, 25 Mar 2019 22:49:33 +0100, Daniele Ceraolo Spurio
> wrote:
>
> > We have several cases where we don't have forcewake (older gens, GVT and
> > planned display-only uncore), so, instead of checking every time against
> > the various condit
== Series Details ==
Series: series starting with [CI,1/9] drm/i915: rename raw reg access functions
URL : https://patchwork.freedesktop.org/series/58604/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12608
== Series Details ==
Series: series starting with [CI,1/9] drm/i915: rename raw reg access functions
URL : https://patchwork.freedesktop.org/series/58604/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: rename raw reg access functions
-drivers
== Series Details ==
Series: series starting with [CI,1/9] drm/i915: rename raw reg access functions
URL : https://patchwork.freedesktop.org/series/58604/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
518022b1d8c7 drm/i915: rename raw reg access functions
-:302: CHECK:LINE_SPAC
== Series Details ==
Series: drm/i915: Adding missing '; ' to ENGINE_INSTANCES
URL : https://patchwork.freedesktop.org/series/58599/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12606
Summary
---
*
== Series Details ==
Series: drm/fb-helper: Move modesetting code to drm_client
URL : https://patchwork.freedesktop.org/series/58597/
State : failure
== Summary ==
Applying: drm/fb-helper: Remove unused gamma_size variable
Applying: drm/fb-helper: dpms_legacy(): Only set on connectors in use
A
== Series Details ==
Series: drm/i915: Adding missing '; ' to ENGINE_INSTANCES
URL : https://patchwork.freedesktop.org/series/58599/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c8194aaa11bd drm/i915: Adding missing '; ' to ENGINE_INSTANCES
-:10: WARNING:BAD_SIGN_OFF: Use a si
On Tue, Mar 26, 2019 at 06:55:33PM +0100, Noralf Trønnes wrote:
> Prepare for moving drm_fb_helper modesetting code to drm_client.
> drm_client will be linked to drm.ko, so move
> __drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
> out of drm_kms_helper.ko.
>
> While at it,
On Fri, 2019-03-22 at 10:27 -0700, Dhinakaran Pandiyan wrote:
> On Fri, 2019-03-22 at 11:15 +0200, Jani Nikula wrote:
> > On Thu, 21 Mar 2019, José Roberto de Souza
> > wrote:
> > > Right now it have a mix of PSR registers that are relative to PSR
> > > mmio base and other register with a hardcode
== Series Details ==
Series: series starting with [1/4] drm: Nuke unused drm_display_info.pixel_clock
URL : https://patchwork.freedesktop.org/series/58595/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12605
===
On Tue, Mar 26, 2019 at 06:55:46PM +0100, Noralf Trønnes wrote:
> drm_dev_register() initializes internal clients like bootsplash as the
> last thing it does, so all setup needs to be done at this point.
>
> Fix by calling vc4_kms_load() before registering.
> Also check the error code returned fro
== Series Details ==
Series: drm/i915: Update size upon return from GEM_CREATE (rev2)
URL : https://patchwork.freedesktop.org/series/58592/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12604
Summary
-
From: Daniele Ceraolo Spurio
The full read/write ops can now work on the intel_uncore struct.
Introduce intel_uncore_read/write functions working on intel_uncore
and switch the I915_READ/WRITE macro to internally call those.
v2: no change
v3: add intel_uncore_read/write functions (Chris), update
From: Daniele Ceraolo Spurio
A few advantages:
- Prepares us for the planned split of display uncore from GT uncore
- Improves our engine-centric view of the world in the engine code
and allows us to avoid jumping back to dev_priv.
- Allows us to wrap accesses to engine register in nice macr
From: Daniele Ceraolo Spurio
Save the HW capabilities to avoid having to jump back to dev_priv
every time.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
Reviewed-by: Paulo Zanoni
Signed-off-by: Chris Wilson
Link:
https://patchwork.freedesktop.org/patch/msgid/20190
From: Daniele Ceraolo Spurio
The intel_uncore structure is the owner of FW, so subclass the
function to it.
While at it, use a local uncore var and switch to the new read/write
functions where it makes sense.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
Signed-off-
From: Daniele Ceraolo Spurio
We have several cases where we don't have forcewake (older gens, GVT and
planned display-only uncore), so, instead of checking every time against
the various condition, save the info in a flag and use that.
Note that this patch also change the behavior for gen5 with
From: Daniele Ceraolo Spurio
The intel_uncore structure is the owner of register access, so
subclass the function to it.
While at it, use a local uncore var and switch to the new read/write
functions where it makes sense.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
From: Daniele Ceraolo Spurio
The intel_uncore structure is the owner of register access, so
subclass the function to it.
While at it, use a local uncore var and switch to the new read/write
functions where it makes sense.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
From: Daniele Ceraolo Spurio
Remove a bit of pointer dancing in the reg access path.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
Signed-off-by: Chris Wilson
Link:
https://patchwork.freedesktop.org/patch/msgid/20190325214940.23632-5-daniele.ceraolospu...@intel.com
From: Daniele Ceraolo Spurio
They now work on uncore, so use raw_uncore_ prefix. Also move them to
uncore.h
Signed-off-by: Daniele Ceraolo Spurio
Cc: Paulo Zanoni
Cc: Chris Wilson
Reviewed-by: Paulo Zanoni
Signed-off-by: Chris Wilson
Link:
https://patchwork.freedesktop.org/patch/msgid/2019
== Series Details ==
Series: drm/i915/selftests: Fix an IS_ERR() vs NULL check
URL : https://patchwork.freedesktop.org/series/58557/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5815_full -> Patchwork_12598_full
Summary
--
== Series Details ==
Series: drm/i915: Update size upon return from GEM_CREATE (rev2)
URL : https://patchwork.freedesktop.org/series/58592/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6fac14bf9f60 drm/i915: Update size upon return from GEM_CREATE
-:15: WARNING:COMMIT_LOG_LONG
== Series Details ==
Series: drm/i915: Only reset the pinned kernel contexts on resume
URL : https://patchwork.freedesktop.org/series/58589/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12603
Summary
== Series Details ==
Series: drm/i915: Only reset the pinned kernel contexts on resume
URL : https://patchwork.freedesktop.org/series/58589/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Only reset the pinned kernel contexts on resume
-drive
== Series Details ==
Series: series starting with [1/2] drm/i915: Do not enable FEC without DSC
URL : https://patchwork.freedesktop.org/series/58588/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12602
Sum
Hi Daniele,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on next-20190326]
[cannot apply to v5.1-rc2]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
== Series Details ==
Series: series starting with [v2,1/6] drm/i915: Add broadcast RGB property for
DP MST
URL : https://patchwork.freedesktop.org/series/58585/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12601
=
Even with 128MiB reserved for other use, a single pass of gem_exec_big
runs out of memory. Give in and halve our batch size, that has to be
enough slack! As to why it keeps on failing, is left as an exercise to
the reader -- we have to solve the mm/ mystery one day, as eventually it
will be our onl
== Series Details ==
Series: Do not re-read dpll registers (rev3)
URL : https://patchwork.freedesktop.org/series/58382/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5815_full -> Patchwork_12597_full
Summary
---
**FA
On Tue, Mar 26, 2019 at 06:55:32PM +0100, Noralf Trønnes wrote:
> For each enabled crtc the functions sets dpms on all registered connectors.
> Limit this to only doing it once and on the connectors actually in use.
>
> Signed-off-by: Noralf Trønnes
Fixes: 023eb571a1d0 ("drm: correctly update con
On Tue, Mar 26, 2019 at 06:55:31PM +0100, Noralf Trønnes wrote:
> The gamma_size variable has not been used since
> commit 4abe35204af8 ("drm/kms/fb: use slow work mechanism for normal hotplug
> also.")
>
> While in the area move a comment back to its code block.
> They got separated by
> commit
== Series Details ==
Series: series starting with [v2,1/6] drm/i915: Add broadcast RGB property for
DP MST
URL : https://patchwork.freedesktop.org/series/58585/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Add broadcast RGB property for DP
== Series Details ==
Series: series starting with [01/21] drm/fb-helper: Add fill_info() functions
URL : https://patchwork.freedesktop.org/series/58578/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5818 -> Patchwork_12600
== Series Details ==
Series: series starting with [v2,1/6] drm/i915: Add broadcast RGB property for
DP MST
URL : https://patchwork.freedesktop.org/series/58585/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
18c4bad008ca drm/i915: Add broadcast RGB property for DP MST
34e5685e9
On 26/03/2019 18:00, Chris Wilson wrote:
Tvrtko spotted that I left off the trailing ';'. It went unnoticed by CI
because despite adding the macro, we didn't add a user, so include one as
well (a simple debug print).
Reported-by: Tvrtko Ursulin
Fixes: 97ee6e925552 ("drm/i915: stop storing the
On Tue, Mar 26, 2019 at 07:34:01PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Remove the unused DRM_DISPLAY_INFO_LEN from the uapi headers.
> I presume the original plan was to expose the display name
> via getconnector, but looks like that never happened. So we have
> the define for t
On Tue, Mar 26, 2019 at 07:34:00PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.name is only ever set by a few panel drveirs but
> never actually used anywhere except in i915 debugfs code. Trash it.
>
> Signed-off-by: Ville Syrjälä
Huh, nice find.
Reviewed-by: Daniel
On Tue, Mar 26, 2019 at 07:33:59PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> A set of 8 spaces has snuck in. Replace with a tab, and
> toss in an extra newline while at it.
>
> Signed-off-by: Ville Syrjälä
> ---
> include/drm/drm_connector.h | 3 ++-
> 1 file changed, 2 insertions(
On Tue, Mar 26, 2019 at 07:33:58PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> drm_display_info.pixel_clock is unused. Let's get rid of it.
>
> Signed-off-by: Ville Syrjälä
> ---
> include/drm/drm_connector.h | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/include/drm/
On Tue, Mar 26, 2019 at 06:16:57PM +0200, Ville Syrjälä wrote:
> On Tue, Mar 26, 2019 at 09:00:27AM -0700, Manasi Navare wrote:
> > On Tue, Mar 26, 2019 at 04:49:02PM +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Currently we enable FEC even when DSC is no used. While that is
An example to showcase the client API.
TODO:
A bootsplash client needs a way to tell drm_fb_helper to stay away,
otherwise it will chime in on setup and hotplug.
Most DRM drivers register fbdev before calling drm_dev_register() (the
generic emulation is an exception). This have to be reversed for
drm_dev_register() initializes internal clients like bootsplash as the
last thing it does, so all setup needs to be done at this point.
Fix by calling vc4_kms_load() before registering.
Also check the error code returned from that function.
Cc: Eric Anholt
Signed-off-by: Noralf Trønnes
---
dri
Add display abstraction and helpers to probe for displays and commit
modesets.
TODO:
If the bootsplash client doesn't need to subclass drm_client_display,
the callbacks can be removed.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c | 415 +++
incl
No functional changes, just moving code as-is and fixing includes.
There is one addition and that is exporting drm_client_modesets_probe().
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 698
drivers/gpu/drm/drm_fb_helper.c | 697
drm_fb_helper_is_bound() is used to check if DRM userspace is in control.
This is done by looking at the fb on the primary plane. By the time
fb-helper gets around to committing, it's possible that the facts have
changed.
Avoid this race by holding the drm_device->master_mutex lock while
committin
All drivers add all their connectors so there's no need to keep around an
array of available connectors.
Rename functions which signature is changed since they will be moved to
drm_client in a later patch.
Signed-off-by: Noralf Trønnes
---
checkpatch complains, but I'm unable to satisfy it:
ER
This prepares the modeset code so it can be moved out as-is in the next
patch.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 75 +
include/drm/drm_fb_helper.h | 4 --
2 files changed, 57 insertions(+), 22 deletions(-)
diff --git a/drive
Tvrtko spotted that I left off the trailing ';'. It went unnoticed by CI
because despite adding the macro, we didn't add a user, so include one as
well (a simple debug print).
Reported-by: Tvrtko Ursulin
Fixes: 97ee6e925552 ("drm/i915: stop storing the media fuse")
Signed-off-by: Chris Wilson
C
It is generic code and having it in the helper will let other drivers
benefit from it.
One change was necessary assuming this to be true:
INTEL_INFO(dev_priv)->num_pipes == dev->mode_config.num_crtc
Suggested-by: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: intel-gfx
This makes the necessary changes so the commit code can be moved out to
drm_client as-is in the next patch. It's split up to ease review.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 93 +
1 file changed, 59 insertions(+), 34 deletions(-)
d
Prepare for moving drm_fb_helper modesetting code to drm_client.
drm_client will be linked to drm.ko, so move
__drm_atomic_helper_disable_plane() and __drm_atomic_helper_set_config()
out of drm_kms_helper.ko.
While at it, fix two checkpatch complaints:
- WARNING: Block comments use a trailing */ o
For each enabled crtc the functions sets dpms on all registered connectors.
Limit this to only doing it once and on the connectors actually in use.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/dr
Move the modeset commit code to drm_client.
No changes except exporting API.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_client.c| 236
drivers/gpu/drm/drm_fb_helper.c | 232 ---
include/drm/drm_client.h| 3 +
3
It now only contains the modeset so use that directly instead. The modeset
code will be moved to drm_client, so add code there.
The modeset connector array size is hardcoded for the cloned case to avoid
having to pass in a value from the driver. A value of 8 is chosen to err
on the safe side. This
Getting rotation info is cheap so we can do it on demand.
This is done in preparation for the removal of struct drm_fb_helper_crtc.
Cc: Hans de Goede
Signed-off-by: Noralf Trønnes
---
Hans,
You had this comment inline in restore_fbdev_mode_atomic() the last time
I sent this out:
We want p
The gamma_size variable has not been used since
commit 4abe35204af8 ("drm/kms/fb: use slow work mechanism for normal hotplug
also.")
While in the area move a comment back to its code block.
They got separated by
commit d50ba256b5f1 ("drm/kms: start adding command line interface using fb.").
Sign
This moves the modesetting code from drm_fb_helper to drm_client so it
can be shared by all internal clients.
I have also added a client display abstraction and a bootsplash example
client to show where this might be heading. Hopefully Max Staudt will be
able to pick up his bootsplash work now.
N
The values are already present in the modeset.
This is done in preparation for the removal of struct drm_fb_helper_crtc.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_fb_helper.c | 12
include/drm/drm_fb_helper.h | 2 --
2 files changed, 4 insertions(+), 10 deletions(-
== Series Details ==
Series: series starting with [01/21] drm/fb-helper: Add fill_info() functions
URL : https://patchwork.freedesktop.org/series/58578/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/fb-helper: Add fill_info() functions
Okay!
Comm
== Series Details ==
Series: series starting with [01/21] drm/fb-helper: Add fill_info() functions
URL : https://patchwork.freedesktop.org/series/58578/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
14d8e1994710 drm/fb-helper: Add fill_info() functions
-:17: WARNING:TYPO_SPELLI
From: Ville Syrjälä
Remove the unused DRM_DISPLAY_INFO_LEN from the uapi headers.
I presume the original plan was to expose the display name
via getconnector, but looks like that never happened. So we have
the define for the length of the string but no string anywhere.
A quick scan didn't seem t
From: Ville Syrjälä
drm_display_info.pixel_clock is unused. Let's get rid of it.
Signed-off-by: Ville Syrjälä
---
include/drm/drm_connector.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index bb3bd8e1633a..fcdca46e0c24 1006
From: Ville Syrjälä
drm_display_info.name is only ever set by a few panel drveirs but
never actually used anywhere except in i915 debugfs code. Trash it.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_debugfs.c| 1 -
drivers/gpu/drm/panel/panel-arm-versatile.c
From: Ville Syrjälä
A set of 8 spaces has snuck in. Replace with a tab, and
toss in an extra newline while at it.
Signed-off-by: Ville Syrjälä
---
include/drm/drm_connector.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_connector.h b/include/drm/drm_con
Quoting Vanshidhar Konda (2019-03-26 17:29:07)
> On Tue, Mar 26, 2019 at 06:02:18PM +0100, Michał Winiarski wrote:
> >Since GEM_CREATE is trying to outsmart the user by rounding up unaligned
> >objects, we used to update the size returned to userspace.
> >This update seems to have been lost through
On Tue, Mar 26, 2019 at 06:02:18PM +0100, Michał Winiarski wrote:
Since GEM_CREATE is trying to outsmart the user by rounding up unaligned
objects, we used to update the size returned to userspace.
This update seems to have been lost throughout the history.
v2: Use round_up(), reorder locals (Ch
Quoting Kenneth Graunke (2019-03-26 17:01:57)
> On Tuesday, March 26, 2019 12:16:20 AM PDT Chris Wilson wrote:
> > Quoting Kenneth Graunke (2019-03-26 05:52:10)
> > > On Monday, March 25, 2019 3:58:59 AM PDT Chris Wilson wrote:
> > > > iris currently uses two distinct GEM contexts to have distinct
On Tuesday, March 26, 2019 12:16:20 AM PDT Chris Wilson wrote:
> Quoting Kenneth Graunke (2019-03-26 05:52:10)
> > On Monday, March 25, 2019 3:58:59 AM PDT Chris Wilson wrote:
> > > iris currently uses two distinct GEM contexts to have distinct logical
> > > HW contexts for the compute and render p
Since GEM_CREATE is trying to outsmart the user by rounding up unaligned
objects, we used to update the size returned to userspace.
This update seems to have been lost throughout the history.
v2: Use round_up(), reorder locals (Chris)
References: ff72145badb8 ("drm: dumb scanout create/mmap for i
== Series Details ==
Series: more uncore rework
URL : https://patchwork.freedesktop.org/series/58550/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5814_full -> Patchwork_12596_full
Summary
---
**SUCCESS**
No regr
Quoting Michał Winiarski (2019-03-26 16:33:45)
> Since GEM_CREATE is trying to outsmart the user by rounding up unaligned
> objects, we used to update the size returned to userspace.
> This update seems to have been lost throughout the history.
>
> References: ff72145badb8 ("drm: dumb scanout crea
Since GEM_CREATE is trying to outsmart the user by rounding up unaligned
objects, we used to update the size returned to userspace.
This update seems to have been lost throughout the history.
References: ff72145badb8 ("drm: dumb scanout create/mmap for intel/radeon (v3)")
Signed-off-by: Michał Win
== Series Details ==
Series: Device id consolidation
URL : https://patchwork.freedesktop.org/series/58561/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5817 -> Patchwork_12599
Summary
---
**SUCCESS**
No regressio
On Tue, Mar 26, 2019 at 09:00:27AM -0700, Manasi Navare wrote:
> On Tue, Mar 26, 2019 at 04:49:02PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Currently we enable FEC even when DSC is no used. While that is
> > theoretically valid supposedly there isn't much of a benefit from
> >
== Series Details ==
Series: Device id consolidation
URL : https://patchwork.freedesktop.org/series/58561/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Split Pineview device info into desktop and mobile
-drivers/gpu/drm/i915/selftests/../i9
On Tue, Mar 26, 2019 at 04:49:03PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> No point in duplicating all this code when we can just
> use a variable top hold the output bpp (the only thing
> that differs between the two branches).
>
> Cc: Anusha Srivatsa
> Cc: Manasi Navare
> Signe
== Series Details ==
Series: Device id consolidation
URL : https://patchwork.freedesktop.org/series/58561/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
caf40a504a05 drm/i915: Split Pineview device info into desktop and mobile
1a9cbf3aa2a4 drm/i915: Remove redundant device id f
On Tue, Mar 26, 2019 at 04:49:02PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Currently we enable FEC even when DSC is no used. While that is
> theoretically valid supposedly there isn't much of a benefit from
> this. But more importantly we do not account for the FEC link
> bandwidth
== Series Details ==
Series: drm/i915: stop storing the media fuse (rev2)
URL : https://patchwork.freedesktop.org/series/58387/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5814_full -> Patchwork_12595_full
Summary
---
Quoting Tvrtko Ursulin (2019-03-26 15:44:35)
>
> On 22/03/2019 09:21, Chris Wilson wrote:
> > +static void clone_vm(int i915)
> > +{
> > + struct drm_i915_gem_context_create_ext_setparam set = {
> > + { .name = I915_CONTEXT_CREATE_EXT_SETPARAM },
> > + { .param = I915_C
Quoting Tvrtko Ursulin (2019-03-26 15:44:35)
>
> On 22/03/2019 09:21, Chris Wilson wrote:
> > +static void clone_engines(int i915)
> > +{
> > + struct drm_i915_gem_context_create_ext_setparam set = {
> > + { .name = I915_CONTEXT_CREATE_EXT_SETPARAM },
> > + { .param = I
On 22/03/2019 09:21, Chris Wilson wrote:
Exercise cloning contexts, an extension of merely creating one.
Signed-off-by: Chris Wilson
---
tests/Makefile.sources | 1 +
tests/i915/gem_ctx_clone.c | 421 +
tests/meson.build | 1 +
3 files
On resume, we know that the only pinned contexts in danger of seeing
corruption are the kernel context, and so we do not need to walk the
list of all GEM contexts as we tracked them on each engine.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_drv.h| 1 -
drivers/gpu/drm
1 - 100 of 221 matches
Mail list logo
