dri-devel August 2019

dri-devel@lists.freedesktop.org

318 participants
2338 discussions

[git pull] drm fixes for 5.3-rc5
by Dave Airlie 16 Aug '19

16 Aug '19

Hi Linus, Nothing too crazy this week, one amdgpu fix to use vmalloc for a struct that grew in size, and another MST fix for nouveau, and some other misc fixes. Regards, Dave. drm-fixes-2019-08-16: drm fixes for 5.3-rc5 i915: - single GVT use after free fix scheduler: - entity destruction race fix amdgpu: - struct allocation fix - gfx9 soft recovery fix nouveau: - followup MST fix ast: - vga register race fix. The following changes since commit d45331b00ddb179e291766617259261c112db872: Linux 5.3-rc4 (2019-08-11 13:26:41 -0700) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-08-16 for you to fetch changes up to a85abd5d45adba75535b7fc6d9f78329a693b7a9: Merge tag 'drm-intel-fixes-2019-08-15' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2019-08-16 12:41:52 +1000) ---------------------------------------------------------------- drm fixes for 5.3-rc5 i915: - single GVT use after free fix scheduler: - entity destruction race fix amdgpu: - struct allocation fix - gfx9 soft recovery fix nouveau: - followup MST fix ast: - vga register race fix. ---------------------------------------------------------------- Alex Deucher (1): drm/amd/display: use kvmalloc for dc_state (v2) Christian König (1): drm/scheduler: use job count instead of peek Dan Carpenter (1): drm/i915: Use after free in error path in intel_vgpu_create_workload() Dave Airlie (2): Merge tag 'drm-fixes-5.3-2019-08-14' of git://people.freedesktop.org/~agd5f/linux into drm-fixes Merge tag 'drm-intel-fixes-2019-08-15' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes Jani Nikula (1): Merge tag 'gvt-fixes-2019-08-13' of https://github.com/intel/gvt-linux into drm-intel-fixes Lyude Paul (1): drm/nouveau: Only recalculate PBN/VCPI on mode/connector changes Pierre-Eric Pelloux-Prayer (1): drm/amdgpu: fix gfx9 soft recovery Y.C. Chen (1): drm/ast: Fixed reboot test may cause system hanged drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 2 +- drivers/gpu/drm/amd/display/dc/core/dc.c | 11 ++++++----- drivers/gpu/drm/ast/ast_main.c | 5 ++++- drivers/gpu/drm/ast/ast_mode.c | 2 +- drivers/gpu/drm/ast/ast_post.c | 2 +- drivers/gpu/drm/i915/gvt/scheduler.c | 4 ++-- drivers/gpu/drm/nouveau/dispnv50/disp.c | 22 +++++++++++++--------- drivers/gpu/drm/scheduler/sched_entity.c | 4 ++-- 8 files changed, 30 insertions(+), 22 deletions(-)

2 1

Re: [PATCH 09/10] mm: remove the unused MIGRATE_PFN_DEVICE flag
by Jason Gunthorpe 16 Aug '19

16 Aug '19

On Wed, Aug 14, 2019 at 09:59:27AM +0200, Christoph Hellwig wrote: > No one ever checks this flag, and we could easily get that information > from the page if needed. > > Signed-off-by: Christoph Hellwig <hch(a)lst.de> > Reviewed-by: Ralph Campbell <rcampbell(a)nvidia.com> > --- > drivers/gpu/drm/nouveau/nouveau_dmem.c | 3 +-- > include/linux/migrate.h | 1 - > mm/migrate.c | 4 ++-- > 3 files changed, 3 insertions(+), 5 deletions(-) Reviewed-by: Jason Gunthorpe <jgg(a)mellanox.com> Jason

1 0

Re: [PATCH 10/10] mm: remove CONFIG_MIGRATE_VMA_HELPER
by Jason Gunthorpe 16 Aug '19

16 Aug '19

On Wed, Aug 14, 2019 at 09:59:28AM +0200, Christoph Hellwig wrote: > CONFIG_MIGRATE_VMA_HELPER guards helpers that are required for proper > devic private memory support. Remove the option and just check for > CONFIG_DEVICE_PRIVATE instead. > > Signed-off-by: Christoph Hellwig <hch(a)lst.de> > --- > drivers/gpu/drm/nouveau/Kconfig | 1 - > mm/Kconfig | 3 --- > mm/migrate.c | 4 ++-- > 3 files changed, 2 insertions(+), 6 deletions(-) Reviewed-by: Jason Gunthorpe <jgg(a)mellanox.com> Aside from it making sense, I checked no other driver enables DEVICE_PRIVATE, so no change in kernel build. Jason

1 0

[Bug 110361] [CI][DRMTIP] igt@kms_chamelium@hdmi-cmp-planes-random - fail - Failed assertion: false, Conversion not implemented
by bugzilla-daemon＠freedesktop.org 16 Aug '19

16 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=110361 emersion <contact(a)emersion.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from emersion <contact(a)emersion.fr> --- Not seen in 3 months. Closing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[GIT PULL FOR v5.4] R-Car DU fix & misc. DRM cleanups
by Laurent Pinchart 16 Aug '19

16 Aug '19

Hi Dave, The following changes since commit 8120ed5ebd2aaad1fee1a777effa158e5284b816: Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next (2019-08-16 12:43:21 +1000) are available in the Git repository at: git://linuxtv.org/pinchartl/media.git tags/du-next-20190816 for you to fetch changes up to 0b936e6122738f4cf474d1f3ff636cba0edc8b94: drm: rcar-du: lvds: Fix bridge_to_rcar_lvds (2019-08-16 15:50:27 +0300) ---------------------------------------------------------------- - R-Car DU fixes - Misc. DRM cleanups ---------------------------------------------------------------- Fabrizio Castro (1): drm: rcar-du: lvds: Fix bridge_to_rcar_lvds Laurent Pinchart (2): drm: Don't include drm/drm_encoder_slave.h when not needed drm: Remove bridge support from legacy helpers drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 1 - drivers/gpu/drm/drm_crtc_helper.c | 32 ------------------------------- drivers/gpu/drm/imx/dw_hdmi-imx.c | 2 +- drivers/gpu/drm/rcar-du/rcar_lvds.c | 8 ++++---- 4 files changed, 5 insertions(+), 38 deletions(-) -- Regards, Laurent Pinchart

1 0

[Bug 109380] [CI][BAT] igt@kms_chamelium@*- warn/fail - Last errno: 113, No route to host
by bugzilla-daemon＠freedesktop.org 16 Aug '19

16 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=109380 --- Comment #6 from emersion <contact(a)emersion.fr> --- Related bug about Chamelium not having all ports plugged in: https://bugs.freedesktop.org/show_bug.cgi?id=110940 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[GIT PULL FOR v5.3] R-Car LVDS fix
by Laurent Pinchart 16 Aug '19

16 Aug '19

Hi Dave, The following changes since commit a85abd5d45adba75535b7fc6d9f78329a693b7a9: Merge tag 'drm-intel-fixes-2019-08-15' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2019-08-16 12:41:52 +1000) are available in the Git repository at: git://linuxtv.org/pinchartl/media.git tags/du-fixes-20190816 vi for you to fetch changes up to a53358a31c989c360ea59536d28762b9d2d68d19: drm: rcar_lvds: Fix dual link mode operations (2019-08-16 15:53:28 +0300) This fixes a bug introduced in v5.3, I'm thus sending it as a fix for the current kernel release candidate. If it's too late it could also be merged in v5.4. ---------------------------------------------------------------- R-Car LVDS encoder fix ---------------------------------------------------------------- Jacopo Mondi (1): drm: rcar_lvds: Fix dual link mode operations drivers/gpu/drm/rcar-du/rcar_lvds.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) -- Regards, Laurent Pinchart

1 0

[Bug 107459] Atomically set gamma ramps are not applied until TTY switch
by bugzilla-daemon＠freedesktop.org 16 Aug '19

16 Aug '19

https://bugs.freedesktop.org/show_bug.cgi?id=107459 Bug ID: 107459 Summary: Atomically set gamma ramps are not applied until TTY switch Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: sir(a)cmpwn.com When atomically setting gamma ramps on AMDGPU (specifically ), the changes don't take effect until switching to another TTY and back again. Using the legacy DRM interface works as expected. To reproduce, build and run the rootston Wayland compositor: https://github.com/swaywm/wlroots We will shortly be merging this patch for a new gamma control protocol extension, which you will need to apply if we haven't merged it by the time you attempt it: https://github.com/swaywm/wlroots/pull/1157 An sample program will be available in the build directory, ./examples/gamma-control, which can adjust gamma. By default this will use the atomic interface, set WLR_DRM_NO_ATOMIC=1 before starting rootston to use the legacy interface. Our atomic gamma code is here: https://github.com/swaywm/wlroots/blob/master/backend/drm/atomic.c#L199-L230 -- You are receiving this mail because: You are the assignee for the bug.

1 8

Re: [PATCH 04/15] mm: remove the pgmap field from struct hmm_vma_walk
by Jason Gunthorpe 16 Aug '19

16 Aug '19

On Fri, Aug 16, 2019 at 06:44:48AM +0200, Christoph Hellwig wrote: > On Fri, Aug 16, 2019 at 12:43:07AM +0000, Jason Gunthorpe wrote: > > On Thu, Aug 15, 2019 at 04:51:33PM -0400, Jerome Glisse wrote: > > > > > struct page. In this case any way we can update the > > > nouveau_dmem_page() to check that page page->pgmap == the > > > expected pgmap. > > > > I was also wondering if that is a problem.. just blindly doing a > > container_of on the page->pgmap does seem like it assumes that only > > this driver is using DEVICE_PRIVATE. > > > > It seems like something missing in hmm_range_fault, it should be told > > what DEVICE_PRIVATE is acceptable to trigger HMM_PFN_DEVICE_PRIVATE > > and fault all others? > > The whole device private handling in hmm and migrate_vma seems pretty > broken as far as I can tell, and I have some WIP patches. Basically we > should not touch (or possibly eventually call migrate to ram eventually > in the future) device private pages not owned by the caller, where I > try to defined the caller by the dev_pagemap_ops instance. I think it needs to be more elaborate. For instance, a system may have multiple DEVICE_PRIVATE map's owned by the same driver - but multiple physical devices using that driver. Each physical device's driver should only ever get DEVICE_PRIVATE pages for it's own on-device memory. Never a DEVICE_PRIVATE for another device's memory. The dev_pagemap_ops would not be unique enough, right? Probably also clusters of same-driver struct device can share a DEVICE_PRIVATE, at least high end GPU's now have private memory coherency busses between their devices. Since we want to trigger migration to CPU on incompatible DEVICE_PRIVATE pages, it seems best to sort this out in the hmm_range_fault? Maybe some sort of unique ID inside the page->pgmap and passed as input? Jason

1 0

linux-next: build warning after merge of the drm-misc tree
by Stephen Rothwell 16 Aug '19

16 Aug '19

Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) produced this warning: warning: same module names found: drivers/video/fbdev/omap2/omapfb/displays/panel-nec-nl8048hl11.ko drivers/gpu/drm/panel/panel-nec-nl8048hl11.ko warning: same module names found: drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.ko drivers/gpu/drm/panel/panel-sharp-ls037v7dw01.ko warning: same module names found: drivers/video/fbdev/omap2/omapfb/displays/panel-sony-acx565akm.ko drivers/gpu/drm/panel/panel-sony-acx565akm.ko warning: same module names found: drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.ko drivers/gpu/drm/panel/panel-tpo-td028ttec1.ko warning: same module names found: drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td043mtea1.ko drivers/gpu/drm/panel/panel-tpo-td043mtea1.ko Introduced by commits df439abe6501 ("drm/panel: Add driver for the NEC NL8048HL11 panel") c9cf4c2a3bd3 ("drm/panel: Add driver for the Sharp LS037V7DW01 panel") 1c8fc3f0c5d2 ("drm/panel: Add driver for the Sony ACX565AKM panel") 415b8dd08711 ("drm/panel: Add driver for the Toppoly TD028TTEC1 panel") dc2e1e5b2799 ("drm/panel: Add driver for the Toppoly TD043MTEA1 panel") -- Cheers, Stephen Rothwell

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel August 2019