[Intel-gfx] [PATCH v4] drm/i915: Invoke another _DSM to enable MUX on HP Workstation laptops

2021-05-19 Thread Kai-Heng Feng
On HP Fury G7 Workstations, graphics output is re-routed from Intel GFX to discrete GFX after S3. This is not desirable, because userspace will treat connected display as a new one, losing display settings. The expected behavior is to let discrete GFX drives all external displays. The platform in

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for ADL-P: more reviewed patches

2021-05-19 Thread Lucas De Marchi
On Thu, May 20, 2021 at 06:26:17AM +, Patchwork wrote: == Series Details == Series: ADL-P: more reviewed patches URL : https://patchwork.freedesktop.org/series/90305/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10100_full -> Patchwork_20151_full ===

Re: [Intel-gfx] [PATCH v7 01/15] swiotlb: Refactor swiotlb init functions

2021-05-19 Thread Claire Chang
On Thu, May 20, 2021 at 2:50 AM Florian Fainelli wrote: > > > > On 5/17/2021 11:42 PM, Claire Chang wrote: > > Add a new function, swiotlb_init_io_tlb_mem, for the io_tlb_mem struct > > initialization to make the code reusable. > > > > Note that we now also call set_memory_decrypted in swiotlb_ini

Re: [Intel-gfx] [PATCH v7 04/15] swiotlb: Add restricted DMA pool initialization

2021-05-19 Thread Claire Chang
On Thu, May 20, 2021 at 2:54 AM Florian Fainelli wrote: > > > > On 5/17/2021 11:42 PM, Claire Chang wrote: > > Add the initialization function to create restricted DMA pools from > > matching reserved-memory nodes. > > > > Signed-off-by: Claire Chang > > --- > > include/linux/device.h | 4 +++

[Intel-gfx] ✗ Fi.CI.IGT: failure for ADL-P: more reviewed patches

2021-05-19 Thread Patchwork
== Series Details == Series: ADL-P: more reviewed patches URL : https://patchwork.freedesktop.org/series/90305/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10100_full -> Patchwork_20151_full Summary --- **FAILURE**

[Intel-gfx] ✗ Fi.CI.IGT: failure for GuC submission / DRM scheduler integration plan + new uAPI (rev2)

2021-05-19 Thread Patchwork
== Series Details == Series: GuC submission / DRM scheduler integration plan + new uAPI (rev2) URL : https://patchwork.freedesktop.org/series/89840/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10100_full -> Patchwork_20150_full ===

[Intel-gfx] ✗ Fi.CI.IGT: failure for Rename all CSR references to DMC (rev5)

2021-05-19 Thread Patchwork
== Series Details == Series: Rename all CSR references to DMC (rev5) URL : https://patchwork.freedesktop.org/series/90043/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10100_full -> Patchwork_20149_full Summary ---

[Intel-gfx] linux-next: manual merge of the drm-intel tree with Linus' tree

2021-05-19 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/i915_mm.c between commit: 293837b9ac8d ("Revert "i915: fix remap_io_sg to verify the pgprot"") from Linus' tree and commit: ec279384c6a0 ("drm/i915: Initialize err in remap_io_sg()") from the

Re: [Intel-gfx] [PATCH] drm/i915/fbc: Don't nuke manually around flips

2021-05-19 Thread Souza, Jose
On Thu, 2021-05-06 at 00:01 +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Apparently we have discovered another way to hit the dreaded > top of screen FBC corruption on GLK. Previously we thought it > was limited to some combination of FBC nuke+disable+plane update > during the same frame

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm: Extract DPCD backlight helpers from i915, add support in nouveau (rev10)

2021-05-19 Thread Patchwork
== Series Details == Series: drm: Extract DPCD backlight helpers from i915, add support in nouveau (rev10) URL : https://patchwork.freedesktop.org/series/84754/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10100_full -> Patchwork_20147_full ==

Re: [Intel-gfx] [PATCH v7 02/15] swiotlb: Refactor swiotlb_create_debugfs

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Split the debugfs creation to make the code reusable for supporting > different bounce buffer pools, e.g. restricted DMA pool. > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian __

Re: [Intel-gfx] [PATCH v7 07/15] swiotlb: Update is_swiotlb_active to add a struct device argument

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Update is_swiotlb_active to add a struct device argument. This will be > useful later to allow for restricted DMA pool. > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian ___ Intel

Re: [Intel-gfx] [PATCH v7 05/15] swiotlb: Add a new get_io_tlb_mem getter

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Add a new getter, get_io_tlb_mem, to help select the io_tlb_mem struct. > The restricted DMA pool is preferred if available. > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian ___

Re: [Intel-gfx] [PATCH v7 06/15] swiotlb: Update is_swiotlb_buffer to add a struct device argument

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Update is_swiotlb_buffer to add a struct device argument. This will be > useful later to allow for restricted DMA pool. > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian ___ Intel

[Intel-gfx] [PULL] drm-intel-next

2021-05-19 Thread Rodrigo Vivi
Hi Dave and Daniel, Here goes the first pull request targeting 5.14. Main highlight goes to the ADL-P platform and display XeLPD IP enabling patches. Also with a refactor on how we handle the graphics and display IP versions. drm-intel-next-2021-05-19-1: Core Changes: - drm: Rename DP_PSR_SELEC

Re: [Intel-gfx] [PATCH v7 04/15] swiotlb: Add restricted DMA pool initialization

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Add the initialization function to create restricted DMA pools from > matching reserved-memory nodes. > > Signed-off-by: Claire Chang > --- > include/linux/device.h | 4 +++ > include/linux/swiotlb.h | 3 +- > kernel/dma/swiotlb.c| 76 ++

Re: [Intel-gfx] [PATCH v7 11/15] dma-direct: Add a new wrapper __dma_direct_free_pages()

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Add a new wrapper __dma_direct_free_pages() that will be useful later > for swiotlb_free(). > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian ___ Intel-gfx mailing list Intel-gfx@

Re: [Intel-gfx] [PATCH v7 01/15] swiotlb: Refactor swiotlb init functions

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Add a new function, swiotlb_init_io_tlb_mem, for the io_tlb_mem struct > initialization to make the code reusable. > > Note that we now also call set_memory_decrypted in swiotlb_init_with_tbl. > > Signed-off-by: Claire Chang > --- > kernel/dma/swi

Re: [Intel-gfx] [PATCH v7 03/15] swiotlb: Add DMA_RESTRICTED_POOL

2021-05-19 Thread Florian Fainelli
On 5/17/2021 11:42 PM, Claire Chang wrote: > Add a new kconfig symbol, DMA_RESTRICTED_POOL, for restricted DMA pool. > > Signed-off-by: Claire Chang Reviewed-by: Florian Fainelli -- Florian ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.or

Re: [Intel-gfx] [PATCH] Revert "drm/i915: Propagate errors on awaiting already signaled fences"

2021-05-19 Thread Jason Ekstrand
On May 19, 2021 12:16:15 Daniel Vetter wrote: On Wed, May 19, 2021 at 5:06 PM Jason Ekstrand wrote: Once we no longer rely on error propagation, I think there's a lot we can rip out. I honestly did not find that much ... what did you uncover? When I was digging through this earlier today

Re: [Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-19 Thread Daniel Vetter
On Wed, May 19, 2021 at 6:16 PM Tvrtko Ursulin wrote: > > > On 18/05/2021 10:40, Tvrtko Ursulin wrote: > > > > On 18/05/2021 10:16, Daniel Stone wrote: > >> Hi, > >> > >> On Tue, 18 May 2021 at 10:09, Tvrtko Ursulin > >> wrote: > >>> I was just wondering if stat(2) and a chrdev major check would

Re: [Intel-gfx] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Matthew Brost
On Wed, May 19, 2021 at 01:10:04PM +0200, Daniel Vetter wrote: > On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote: > > Add entry fpr i915 new parallel submission uAPI plan. > > > > v2: > > (Daniel Vetter): > > - Expand logical order explaination > > - Add dummy header > > - Onl

Re: [Intel-gfx] [PATCH] Revert "drm/i915: Propagate errors on awaiting already signaled fences"

2021-05-19 Thread Daniel Vetter
On Wed, May 19, 2021 at 5:06 PM Jason Ekstrand wrote: > > Once we no longer rely on error propagation, I think there's a lot we > can rip out. I honestly did not find that much ... what did you uncover? -Daniel > > --Jason > > On Wed, May 19, 2021 at 5:15 AM Daniel Vetter wrote: > > > > From: J

Re: [Intel-gfx] [Mesa-dev] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Matthew Brost
On Wed, May 19, 2021 at 01:45:39PM +0200, Christian König wrote: > Oh, yeah we call that gang submit on the AMD side. > > Had already some internal discussions how to implement this, but so far > couldn't figure out how to cleanly introduce that into the DRM scheduler. > > Can you briefly describ

Re: [Intel-gfx] [PATCH 1/3] gpu: drm: replace occurrences of invalid character

2021-05-19 Thread Alex Deucher
Pushed out to drm-misc-next. Also fixed up Michel's name. Alex On Wed, May 19, 2021 at 11:56 AM Randy Dunlap wrote: > > On 5/19/21 1:15 AM, Mauro Carvalho Chehab wrote: > > There are some places at drm that ended receiving a > > REPLACEMENT CHARACTER U+fffd ('�'), probably because of > > some b

Re: [Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-19 Thread Tvrtko Ursulin
On 18/05/2021 10:40, Tvrtko Ursulin wrote: On 18/05/2021 10:16, Daniel Stone wrote: Hi, On Tue, 18 May 2021 at 10:09, Tvrtko Ursulin wrote: I was just wondering if stat(2) and a chrdev major check would be a solid criteria to more efficiently (compared to parsing the text content) detect d

Re: [Intel-gfx] [PATCH 1/3] gpu: drm: replace occurrences of invalid character

2021-05-19 Thread Randy Dunlap
On 5/19/21 1:15 AM, Mauro Carvalho Chehab wrote: > There are some places at drm that ended receiving a > REPLACEMENT CHARACTER U+fffd ('�'), probably because of > some bad charset conversion. > > Fix them by using what it seems to be the proper > character. > > Signed-off-by: Mauro Carvalho

Re: [Intel-gfx] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Tvrtko Ursulin
On 19/05/2021 12:10, Daniel Vetter wrote: On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote: Add entry fpr i915 new parallel submission uAPI plan. v2: (Daniel Vetter): - Expand logical order explaination - Add dummy header - Only allow N BBs in execbuf IOCTL - Config

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/jsl: Add W/A 1409054076 for JSL (rev3)

2021-05-19 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev3) URL : https://patchwork.freedesktop.org/series/90129/ State : success == Summary == CI Bug Log - changes from CI_DRM_10102 -> Patchwork_20155 Summary --- **

Re: [Intel-gfx] [PATCH] Revert "drm/i915: Propagate errors on awaiting already signaled fences"

2021-05-19 Thread Jason Ekstrand
Once we no longer rely on error propagation, I think there's a lot we can rip out. --Jason On Wed, May 19, 2021 at 5:15 AM Daniel Vetter wrote: > > From: Jason Ekstrand > > This reverts commit 9e31c1fe45d555a948ff66f1f0e3fe1f83ca63f7. Ever > since that commit, we've been having issues where a

Re: [Intel-gfx] [PATCH 1/2] drm/i915/cmdparser: No-op failed batches on all platforms

2021-05-19 Thread Jason Ekstrand
On Wed, May 19, 2021 at 2:43 AM Daniel Vetter wrote: > > On gen9 for blt cmd parser we relied on the magic fence error > propagation which: > - doesn't work on gen7, because there's no scheduler with ringbuffers > there yet > - fence error propagation can be weaponized to attack other things, so

[Intel-gfx] [PATCH i-g-t 9/9] tests/i915/gem_exec_basic: Iterate over all memory regions

2021-05-19 Thread Matthew Auld
From: "Kalamarz, Lukasz" As a part of local memory effort we need to make sure, that every available memory region is covered. This patch is an attempt for this problem. If it will be accepted it will be replicated on each test that can actually benefit from it. Signed-off-by: Dominik Grzegorzek

[Intel-gfx] [PATCH i-g-t 8/9] tests/i915/gem_create: exercise placements extension

2021-05-19 Thread Matthew Auld
Add some explicit testcases for the create_ext placements extension. Signed-off-by: Matthew Auld Cc: Dominik Grzegorzek Cc: Joonas Lahtinen Signed-off-by: Matthew Auld --- tests/i915/gem_create.c | 188 1 file changed, 188 insertions(+) diff --git a/t

[Intel-gfx] [PATCH i-g-t 7/9] tests/i915/gem_media_fill: Use memory region interface

2021-05-19 Thread Matthew Auld
From: Andrzej Turko Converted the test gem_media_fill to use memory region uapi. Signed-off-by: Andrzej Turko Cc: Zbigniew Kempczynski Cc: Dominik Grzegorzek Cc: Petri Latvala Signed-off-by: Matthew Auld --- tests/i915/gem_media_fill.c | 57 - 1 file cha

[Intel-gfx] [PATCH i-g-t 5/9] tests/i915/gem_exec_basic: Use memory region interface

2021-05-19 Thread Matthew Auld
From: Andrzej Turko Converted the test gem_exec_basic to use the memory region uapi. Signed-off-by: Andrzej Turko Cc: Zbigniew Kempczynski Cc: Dominik Grzegorzek Cc: Petri Latvala Signed-off-by: Matthew Auld --- tests/i915/gem_exec_basic.c | 50 + 1 file

[Intel-gfx] [PATCH i-g-t 6/9] tests/i915/gem_gpgpu_fill: Use memory region interface

2021-05-19 Thread Matthew Auld
From: Andrzej Turko Converted the test gem_gpgpu_fill to use memory region uapi. Signed-off-by: Andrzej Turko Cc: Zbigniew Kempczynski Cc: Dominik Grzegorzek Cc: Petri Latvala Signed-off-by: Matthew Auld --- tests/i915/gem_gpgpu_fill.c | 42 ++--- 1 file cha

[Intel-gfx] [PATCH i-g-t 2/9] lib/i915/gem_create: Add gem_create_ext

2021-05-19 Thread Matthew Auld
From: Andrzej Turko Add a wrapper for gem_create_ext ioctl (a version of gem_create that accepts extensions). In preparation for the driver change implementing it, a local definition of its id and necessary structs have been added, which are to be erased as soon as those definitions appear in the

[Intel-gfx] [PATCH i-g-t 4/9] tests/gem_gpgpu_fill: Convert from simple to standard igt_main

2021-05-19 Thread Matthew Auld
From: Dominik Grzegorzek As we need to add new test variants, convert the code to standard igt_main format so those variants can be easily accommodated. Signed-off-by: Janusz Krzysztofik Signed-off-by: Zbigniew Kempczyński Signed-off-by: Matthew Auld --- tests/i915/gem_gpgpu_fill.c | 25

[Intel-gfx] [PATCH i-g-t 3/9] lib/i915/intel_memory_region: Add new memory region lib

2021-05-19 Thread Matthew Auld
From: Andrzej Turko With an introduction of Local Memory concept we should be able to allocate object in specific memory region. This patch implements helper functions that allow this, both for querying what the device supports and hooking into gem_create_ext to select the placements. Co-authore

[Intel-gfx] [PATCH i-g-t 1/9] i915_drm.h sync

2021-05-19 Thread Matthew Auld
Sync to get gem_create_ext and the regions query stuff. Generated from kernel commit: 2459e56fd8af ("drm/i915/uapi: implement object placement extension") Signed-off-by: Matthew Auld --- include/drm-uapi/i915_drm.h | 394 1 file changed, 360 insertions(+), 3

[Intel-gfx] [PATCH i-g-t 0/9] DG1/LMEM uAPI basics v2

2021-05-19 Thread Matthew Auld
Just the really basic stuff, which unlocks adding more interesting testcases later, like gem_lmem_swapping. On the kernel side we landed the uAPI bits[1] behind CONFIG_BROKEN, which is already enabled in CI builds, so it should be possible to get some more BAT testing(outside of just the selftests

[Intel-gfx] [PATCH V3] drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-19 Thread Tejas Upadhyay
When pipe A is disabled and MIPI DSI is enabled on pipe B, the AMT KVMR feature will incorrectly see pipe A as enabled. Set 0x42080 bit 23=1 before enabling DSI on pipe B and leave it set while DSI is enabled on pipe B. No impact to setting it all the time. Changes since V2: - Used REG_BIT

Re: [Intel-gfx] [Mesa-dev] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Marcin Ślusarz
śr., 19 maj 2021 o 01:41 Matthew Brost napisał(a): > > Add entry fpr i915 new parallel submission uAPI plan. s/fpr/for/ > > v2: > (Daniel Vetter): > - Expand logical order explaination > - Add dummy header > - Only allow N BBs in execbuf IOCTL > - Configure parallel submission per slot

Re: [Intel-gfx] New uAPI for color management proposal and feedback request

2021-05-19 Thread Ville Syrjälä
On Wed, May 19, 2021 at 12:34:05PM +0300, Pekka Paalanen wrote: > On Wed, 12 May 2021 16:04:16 +0300 > Ville Syrjälä wrote: > > > On Wed, May 12, 2021 at 02:06:56PM +0200, Werner Sembach wrote: > > > Hello, > > > > > > In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gvt: remove local storage of debugfs file

2021-05-19 Thread Patchwork
== Series Details == Series: drm/i915/gvt: remove local storage of debugfs file URL : https://patchwork.freedesktop.org/series/90294/ State : success == Summary == CI Bug Log - changes from CI_DRM_10098_full -> Patchwork_20146_full Summary

Re: [Intel-gfx] [Mesa-dev] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Christian König
Oh, yeah we call that gang submit on the AMD side. Had already some internal discussions how to implement this, but so far couldn't figure out how to cleanly introduce that into the DRM scheduler. Can you briefly describe in a few words how that is supposed to work on the Intel side? Thanks

[Intel-gfx] [PATCH 1/3] gpu: drm: replace occurrences of invalid character

2021-05-19 Thread Mauro Carvalho Chehab
There are some places at drm that ended receiving a REPLACEMENT CHARACTER U+fffd ('�'), probably because of some bad charset conversion. Fix them by using what it seems to be the proper character. Signed-off-by: Mauro Carvalho Chehab --- drivers/gpu/drm/amd/include/atombios.h | 10 +--

Re: [Intel-gfx] [PATCH 9/9] platform/x86/intel_cht_int33fe: Correct "displayport" fwnode reference

2021-05-19 Thread Hans de Goede
Hi, On 5/3/21 5:46 PM, Hans de Goede wrote: > The Type-C connector on these devices is connected to DP-2 not DP-1, > so the reference must be to the DD04 child-node of the GPU, rather > then the DD02 child-node. > > Signed-off-by: Hans de Goede Since this is pretty much independent from the res

Re: [Intel-gfx] [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip

2021-05-19 Thread Deucher, Alexander
[AMD Public Use] > -Original Message- > From: Jani Nikula > Sent: Wednesday, May 19, 2021 4:50 AM > To: dim-to...@lists.freedesktop.org > Cc: dri-de...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; > jani.nik...@intel.com; Deucher, Alexander > ; Koenig, Christian > ; Pan; Pan, X

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Petri Latvala
On Wed, May 19, 2021 at 12:36:17PM +0100, Matthew Auld wrote: > On Wed, 19 May 2021 at 12:00, Petri Latvala wrote: > > > > On Wed, May 19, 2021 at 11:45:17AM +0100, Matthew Auld wrote: > > > On Wed, 19 May 2021 at 09:49, Petri Latvala > > > wrote: > > > > > > > > On Wed, May 19, 2021 at 09:13:37

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms (rev2)

2021-05-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms (rev2) URL : https://patchwork.freedesktop.org/series/90310/ State : success == Summary == CI Bug Log - changes from CI_DRM_10102 -> Patchwork_20154 ==

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Matthew Auld
On Wed, 19 May 2021 at 12:00, Petri Latvala wrote: > > On Wed, May 19, 2021 at 11:45:17AM +0100, Matthew Auld wrote: > > On Wed, 19 May 2021 at 09:49, Petri Latvala wrote: > > > > > > On Wed, May 19, 2021 at 09:13:37AM +0100, Matthew Auld wrote: > > > > On Tue, 11 May 2021 at 17:52, Matthew Auld

Re: [Intel-gfx] [PATCH v2 10/15] drm/i915/ttm: Introduce a TTM i915 gem object backend

2021-05-19 Thread Thomas Hellström
Thanks a lot for reviewing, Matthew! On 5/19/21 11:53 AM, Matthew Auld wrote: On Tue, 18 May 2021 at 09:28, Thomas Hellström wrote: Most logical place to introduce TTM buffer objects is as an i915 gem object backend. We need to add some ops to account for added functionality like delayed delet

Re: [Intel-gfx] [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

2021-05-19 Thread Daniel Vetter
On Tue, May 18, 2021 at 04:58:30PM -0700, Matthew Brost wrote: > Add entry fpr i915 new parallel submission uAPI plan. > > v2: > (Daniel Vetter): > - Expand logical order explaination > - Add dummy header > - Only allow N BBs in execbuf IOCTL > - Configure parallel submission per slot not

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms (rev2)

2021-05-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms (rev2) URL : https://patchwork.freedesktop.org/series/90310/ State : warning == Summary == $ dim checkpatch origin/drm-tip 2bbc347a556d drm/i915/cmdparser: No-op failed batches on

[Intel-gfx] ✗ Fi.CI.BUILD: failure for nightly.conf: drop amd branches from drm-tip

2021-05-19 Thread Patchwork
== Series Details == Series: nightly.conf: drop amd branches from drm-tip URL : https://patchwork.freedesktop.org/series/90317/ State : failure == Summary == Applying: nightly.conf: drop amd branches from drm-tip Using index info to reconstruct a base tree... A nightly.conf Falling back

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Petri Latvala
On Wed, May 19, 2021 at 11:45:17AM +0100, Matthew Auld wrote: > On Wed, 19 May 2021 at 09:49, Petri Latvala wrote: > > > > On Wed, May 19, 2021 at 09:13:37AM +0100, Matthew Auld wrote: > > > On Tue, 11 May 2021 at 17:52, Matthew Auld wrote: > > > > > > > > Just the really basic stuff, which unloc

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Matthew Auld
On Wed, 19 May 2021 at 09:49, Petri Latvala wrote: > > On Wed, May 19, 2021 at 09:13:37AM +0100, Matthew Auld wrote: > > On Tue, 11 May 2021 at 17:52, Matthew Auld wrote: > > > > > > Just the really basic stuff, which unlocks adding more interesting > > > testcases > > > later, like gem_lmem_swa

Re: [Intel-gfx] [PATCH v2 09/15] drm/ttm, drm/amdgpu: Allow the driver some control over swapping

2021-05-19 Thread Christian König
Am 19.05.21 um 08:27 schrieb Thomas Hellström: On 5/18/21 6:30 PM, Christian König wrote: Am 18.05.21 um 18:07 schrieb Thomas Hellström: On 5/18/21 5:42 PM, Christian König wrote: Am 18.05.21 um 17:38 schrieb Thomas Hellström: On 5/18/21 5:28 PM, Christian König wrote: Am 18.05.21 um 17:2

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/plane: add intel_plane_helper_add() helper

2021-05-19 Thread Patchwork
== Series Details == Series: drm/i915/plane: add intel_plane_helper_add() helper URL : https://patchwork.freedesktop.org/series/90287/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10098_full -> Patchwork_20145_full Summary

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms

2021-05-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms URL : https://patchwork.freedesktop.org/series/90310/ State : success == Summary == CI Bug Log - changes from CI_DRM_10102 -> Patchwork_20152 =

[Intel-gfx] [PATCH] Revert "drm/i915: Propagate errors on awaiting already signaled fences"

2021-05-19 Thread Daniel Vetter
From: Jason Ekstrand This reverts commit 9e31c1fe45d555a948ff66f1f0e3fe1f83ca63f7. Ever since that commit, we've been having issues where a hang in one client can propagate to another. In particular, a hang in an app can propagate to the X server which causes the whole desktop to lock up. Erro

Re: [Intel-gfx] [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip

2021-05-19 Thread Daniel Vetter
On Wed, May 19, 2021 at 11:49:32AM +0300, Jani Nikula wrote: > We've had a stale repo for amd in drm-tip since around v4.15 i.e. for > more than three years. Nobody seems to notice or care. Drop the amd > branches from drm-tip. > > Having the current amd branches in drm-tip would be nice to have,

Re: [Intel-gfx] [PATCH v2 11/15] drm/i915/lmem: Verify checks for lmem residency

2021-05-19 Thread Matthew Auld
On Tue, 18 May 2021 at 09:28, Thomas Hellström wrote: > > Since objects can be migrated or evicted when not pinned or locked, > update the checks for lmem residency or future residency so that > the value returned is not immediately stale. > > Signed-off-by: Thomas Hellström Reviewed-by: Matthew

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms

2021-05-19 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/cmdparser: No-op failed batches on all platforms URL : https://patchwork.freedesktop.org/series/90310/ State : warning == Summary == $ dim checkpatch origin/drm-tip d4f598ce6c56 drm/i915/cmdparser: No-op failed batches on all pl

Re: [Intel-gfx] [PATCH v2 10/15] drm/i915/ttm: Introduce a TTM i915 gem object backend

2021-05-19 Thread Matthew Auld
On Tue, 18 May 2021 at 09:28, Thomas Hellström wrote: > > Most logical place to introduce TTM buffer objects is as an i915 > gem object backend. We need to add some ops to account for added > functionality like delayed delete and LRU list manipulation. > > Initially we support only LMEM and SYSTEM

Re: [Intel-gfx] New uAPI for color management proposal and feedback request

2021-05-19 Thread Pekka Paalanen
On Wed, 12 May 2021 16:04:16 +0300 Ville Syrjälä wrote: > On Wed, May 12, 2021 at 02:06:56PM +0200, Werner Sembach wrote: > > Hello, > > > > In addition to the existing "max bpc", and "Broadcast RGB/output_csc" drm > > properties I propose 4 new properties: > > "preferred pixel encoding", "acti

Re: [Intel-gfx] [PULL] gvt-fixes

2021-05-19 Thread Jani Nikula
On Wed, 19 May 2021, Zhenyu Wang wrote: > Hi, > > This is to fix GVT config workaround introduced during -rc1 via > vfio/mdev change, which exposed dependency issue explicitly that > made current GVT config nasty. So this is to fix dependency issue > and get back original config sanity. Pulled to

[Intel-gfx] [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip

2021-05-19 Thread Jani Nikula
We've had a stale repo for amd in drm-tip since around v4.15 i.e. for more than three years. Nobody seems to notice or care. Drop the amd branches from drm-tip. Having the current amd branches in drm-tip would be nice to have, if only to have a common drm integration tree. However, maintaining tha

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Petri Latvala
On Wed, May 19, 2021 at 09:13:37AM +0100, Matthew Auld wrote: > On Tue, 11 May 2021 at 17:52, Matthew Auld wrote: > > > > Just the really basic stuff, which unlocks adding more interesting testcases > > later, like gem_lmem_swapping. > > > > On the kernel side we landed the uAPI bits[1] behind CON

Re: [Intel-gfx] [PATCH] drm/i915/gvt: remove local storage of debugfs file

2021-05-19 Thread Zhenyu Wang
On 2021.05.19 10:31:18 +0200, Greg Kroah-Hartman wrote: > On Wed, May 19, 2021 at 04:03:13PM +0800, Zhenyu Wang wrote: > > On 2021.05.18 18:28:53 +0200, Greg Kroah-Hartman wrote: > > > On Tue, May 18, 2021 at 06:17:05PM +0200, Greg Kroah-Hartman wrote: > > > > There is no need to keep the dentry ar

Re: [Intel-gfx] [PATCH] drm/i915/gvt: remove local storage of debugfs file

2021-05-19 Thread Greg Kroah-Hartman
On Wed, May 19, 2021 at 04:03:13PM +0800, Zhenyu Wang wrote: > On 2021.05.18 18:28:53 +0200, Greg Kroah-Hartman wrote: > > On Tue, May 18, 2021 at 06:17:05PM +0200, Greg Kroah-Hartman wrote: > > > There is no need to keep the dentry around for the debugfs kvmgt cache > > > file, as we can just look

Re: [Intel-gfx] [PATCH i-g-t 07/12] i915_drm.h sync

2021-05-19 Thread Jani Nikula
On Wed, 19 May 2021, Petri Latvala wrote: > On Tue, May 11, 2021 at 05:51:12PM +0100, Matthew Auld wrote: >> Sync to get gem_create_ext and the regions query stuff. > > Kernel commit sha in commit message please. Might be nice to have a script or a build target to update a file from kernel, with

Re: [Intel-gfx] [PATCH] drm/i915/gvt: remove local storage of debugfs file

2021-05-19 Thread Zhenyu Wang
On 2021.05.18 18:28:53 +0200, Greg Kroah-Hartman wrote: > On Tue, May 18, 2021 at 06:17:05PM +0200, Greg Kroah-Hartman wrote: > > There is no need to keep the dentry around for the debugfs kvmgt cache > > file, as we can just look it up when we want to remove it later on. > > Simplify the structure

Re: [Intel-gfx] [PATCH i-g-t 07/12] i915_drm.h sync

2021-05-19 Thread Petri Latvala
On Tue, May 11, 2021 at 05:51:12PM +0100, Matthew Auld wrote: > Sync to get gem_create_ext and the regions query stuff. Kernel commit sha in commit message please. -- Petri Latvala > > Signed-off-by: Matthew Auld > --- > include/drm-uapi/i915_drm.h | 394 ---

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 00/12] DG1/LMEM uAPI basics

2021-05-19 Thread Matthew Auld
On Tue, 11 May 2021 at 17:52, Matthew Auld wrote: > > Just the really basic stuff, which unlocks adding more interesting testcases > later, like gem_lmem_swapping. > > On the kernel side we landed the uAPI bits[1] behind CONFIG_BROKEN, which is > already enabled in CI builds, so it should be possi

[Intel-gfx] [PULL] gvt-fixes

2021-05-19 Thread Zhenyu Wang
Hi, This is to fix GVT config workaround introduced during -rc1 via vfio/mdev change, which exposed dependency issue explicitly that made current GVT config nasty. So this is to fix dependency issue and get back original config sanity. Thanks -- The following changes since commit e4527420ed087f9

[Intel-gfx] [PATCH 1/2] drm/i915/cmdparser: No-op failed batches on all platforms

2021-05-19 Thread Daniel Vetter
On gen9 for blt cmd parser we relied on the magic fence error propagation which: - doesn't work on gen7, because there's no scheduler with ringbuffers there yet - fence error propagation can be weaponized to attack other things, so not a good design idea Instead of magic, do the same thing on

[Intel-gfx] [PATCH 2/2] Revert "drm/i915: Propagate errors on awaiting already signaled fences"

2021-05-19 Thread Daniel Vetter
From: Jason Ekstrand This reverts commit 9e31c1fe45d555a948ff66f1f0e3fe1f83ca63f7. Ever since that commit, we've been having issues where a hang in one client can propagate to another. In particular, a hang in an app can propagate to the X server which causes the whole desktop to lock up. Sign

Re: [Intel-gfx] [PATCH v4 16/23] drm/i915/display: Remove a redundant function argument from intel_psr_enable_source()

2021-05-19 Thread Anshuman Gupta
On 2021-05-15 at 08:40:28 +0530, Matt Roper wrote: > From: Gwan-gyeong Mun > > It removes intel_crtc_state from function argument of > intel_psr_enable_source() in order to use intel_psr_enable_source() > without intel_crtc_state on other psr internal functions. > And we can get cpu_trancoder fro