Re: [Intel-gfx] [PATCH 08/18] fbdev/hyperv-fb: Do not set struct fb_info.apertures

2022-12-30 Thread Michael Kelley (LINUX)
From: Thomas Zimmermann Sent: Monday, December 19, 2022 8:05 AM > > Generic fbdev drivers use the apertures field in struct fb_info to > control ownership of the framebuffer memory and graphics device. Do > not set the values in hyperv-fb. > > Signed-off-by: Thomas Zimmermann > --- > drivers/

[Intel-gfx] [PATCH] fix gvtg cursor position if it is negative

2022-12-30 Thread qi zhou
>From 8d2a0c2c265119cb481deab825ea59c9605f3bd8 Mon Sep 17 00:00:00 2001 From: Qi Zhou Date: Thu, 29 Dec 2022 20:15:51 +0800 Subject: [PATCH] fix gvtg cursor position if it is negative It is valid if position of cursor is negative(not hotspot coordinates). for example: precision section, resize, m

Re: [Intel-gfx] [PATCH] fix gvtg cursor position if it is negative

2022-12-30 Thread qi zhou
To test, you need patch qemu too, I paste it here for convenience, and I it have been sent to qemu dev mailling list >From 4f14d6216d3f05f01ffe419ff0baeebe416a3e58 Mon Sep 17 00:00:00 2001 From: Qi Zhou Date: Thu, 29 Dec 2022 20:25:06 +0800 Subject: [PATCH] fix gvtg cursor position if it is nega

Re: [Intel-gfx] [PATCH v2 1/2] drm/i915: convert i915_active.count from atomic_t to refcount_t

2022-12-30 Thread Praveen Kumar
On 25-12-2022 13:17, Deepak R Varma wrote: > The refcount_* APIs are designed to address known issues with the > atomic_t APIs for reference counting. They provide following distinct > advantages: >- protect the reference counters from overflow/underflow >- avoid use-after-free errors >

Re: [Intel-gfx] [PATCH] drm/i915: Expand force_probe to block probe of devices as well.

2022-12-30 Thread Rodrigo Vivi
On Thu, Dec 29, 2022 at 03:01:34PM -0300, Gustavo Sousa wrote: > On Thu, Dec 29, 2022 at 11:12:30AM -0500, Rodrigo Vivi wrote: > > There are new cases where we want to block i915 probe, such > > as when experimenting or developing the new Xe driver. > > > > But also, with the new hibrid cards, use

Re: [Intel-gfx] [PATCH v3 1/2] drm/i915/dmc: Do not require specific versions

2022-12-30 Thread Rodrigo Vivi
On Thu, Dec 29, 2022 at 04:07:39PM -0300, Gustavo Sousa wrote: > Currently there is no DMC version requirement with respect to how i915 > interacts with it and new versions of the firmware serve as drop-in > replacements of older ones. As such, do not require specific versions. > > References: htt

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/dmc: Prepare to use unversioned paths

2022-12-30 Thread Rodrigo Vivi
On Thu, Dec 29, 2022 at 04:07:40PM -0300, Gustavo Sousa wrote: > New DMC releases in linux-firmware will stop using version number in > blob filenames. This new convention provides the following benefits: > > 1. It simplifies code maintenance, as new DMC releases for a platform > using the

[Intel-gfx] ✗ Fi.CI.BUILD: failure for fix gvtg cursor position if it is negative (rev2)

2022-12-30 Thread Patchwork
== Series Details == Series: fix gvtg cursor position if it is negative (rev2) URL : https://patchwork.freedesktop.org/series/112307/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/112307/revisions/2/mbox/ not applied Applying: fix gvtg cursor pos

Re: [Intel-gfx] [PATCH v16 0/6] Fixes integer overflow or integer truncation issues in page lookups, ttm place configuration and scatterlist creation

2022-12-30 Thread Rodrigo Vivi
On Wed, Dec 28, 2022 at 09:22:46PM +0200, Gwan-gyeong Mun wrote: > This patch series fixes integer overflow or integer truncation issues in > page lookups, ttm place configuration and scatterlist creation, etc. > We need to check that we avoid integer overflows when looking up a page, > and so fix

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

2022-12-30 Thread Rodrigo Vivi
Hi Dave and Daniel, Here goes the initial fixes for 6.2. The most critical ones seems to be the evict fix from Matt and the MIPI DSI from Jani. Both targeting stable trees. I'm sorry for sending this on a Friday and not on a Thursday as usual. Where did this week go? Worst case this wait one wee

Re: [Intel-gfx] [RFC PATCH 04/20] drm/sched: Convert drm scheduler to use a work queue rather than kthread

2022-12-30 Thread Boris Brezillon
Hello Matthew, On Thu, 22 Dec 2022 14:21:11 -0800 Matthew Brost wrote: > In XE, the new Intel GPU driver, a choice has made to have a 1 to 1 > mapping between a drm_gpu_scheduler and drm_sched_entity. At first this > seems a bit odd but let us explain the reasoning below. > > 1. In XE the submi

Re: [Intel-gfx] [RFC PATCH 04/20] drm/sched: Convert drm scheduler to use a work queue rather than kthread

2022-12-30 Thread Boris Brezillon
On Fri, 30 Dec 2022 11:20:42 +0100 Boris Brezillon wrote: > Hello Matthew, > > On Thu, 22 Dec 2022 14:21:11 -0800 > Matthew Brost wrote: > > > In XE, the new Intel GPU driver, a choice has made to have a 1 to 1 > > mapping between a drm_gpu_scheduler and drm_sched_entity. At first this > > see

Re: [Intel-gfx] [PATCH v3 1/2] drm/i915/dmc: Do not require specific versions

2022-12-30 Thread Gustavo Sousa
On Fri, Dec 30, 2022 at 03:32:41AM -0500, Rodrigo Vivi wrote: > On Thu, Dec 29, 2022 at 04:07:39PM -0300, Gustavo Sousa wrote: > > Currently there is no DMC version requirement with respect to how i915 > > interacts with it and new versions of the firmware serve as drop-in > > replacements of older

Re: [Intel-gfx] [PATCH] drm/i915: Expand force_probe to block probe of devices as well.

2022-12-30 Thread Jani Nikula
On Fri, 30 Dec 2022, Rodrigo Vivi wrote: > On Thu, Dec 29, 2022 at 03:01:34PM -0300, Gustavo Sousa wrote: >> On Thu, Dec 29, 2022 at 11:12:30AM -0500, Rodrigo Vivi wrote: >> > There are new cases where we want to block i915 probe, such >> > as when experimenting or developing the new Xe driver. >>

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/dmc: Prepare to use unversioned paths

2022-12-30 Thread Gustavo Sousa
On Fri, Dec 30, 2022 at 03:47:43AM -0500, Rodrigo Vivi wrote: > On Thu, Dec 29, 2022 at 04:07:40PM -0300, Gustavo Sousa wrote: > > New DMC releases in linux-firmware will stop using version number in > > blob filenames. This new convention provides the following benefits: > > > > 1. It simplifie

[Intel-gfx] [PATCH v3] arch: rename all internal names __xchg to __arch_xchg

2022-12-30 Thread Andrzej Hajda
__xchg will be used for non-atomic xchg macro. Signed-off-by: Andrzej Hajda Reviewed-by: Arnd Bergmann --- v2: squashed all arch patches into one v3: fixed alpha/xchg_local, thx to l...@intel.com --- arch/alpha/include/asm/cmpxchg.h | 8 arch/arc/include/asm/cmpxchg.h | 4 ++-

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce __xchg, non-atomic xchg (rev3)

2022-12-30 Thread Patchwork
== Series Details == Series: Introduce __xchg, non-atomic xchg (rev3) URL : https://patchwork.freedesktop.org/series/112169/ State : warning == Summary == Error: dim checkpatch failed 81cf90111073 arch/alpha: rename internal name __xchg to __arch_xchg cc5f60d730c4 arch: rename all internal nam

[Intel-gfx] ✓ Fi.CI.BAT: success for Introduce __xchg, non-atomic xchg (rev3)

2022-12-30 Thread Patchwork
== Series Details == Series: Introduce __xchg, non-atomic xchg (rev3) URL : https://patchwork.freedesktop.org/series/112169/ State : success == Summary == CI Bug Log - changes from CI_DRM_12532 -> Patchwork_112169v3 Summary --- **SUC

[Intel-gfx] [drm-tip:drm-tip 7/20] drivers/gpu/drm/i915/gem/i915_gem_shmem.c:241:34: error: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' {aka 'unsigned i

2022-12-30 Thread kernel test robot
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: 91195847031b60062eb046b8bb0c9e64a2291e10 commit: c3bfba9a222550406082c92bbabc9c8b1355d8b8 [7/20] drm/i915: Check for integer truncation on scatterlist creation config: i386-defconfig compiler: gcc-11 (Debian 11.3.0-8) 11.3.0 reprodu

Re: [Intel-gfx] [PATCH v3 1/2] drm/i915/dmc: Do not require specific versions

2022-12-30 Thread Rodrigo Vivi
On Fri, Dec 30, 2022 at 09:42:39AM -0300, Gustavo Sousa wrote: > On Fri, Dec 30, 2022 at 03:32:41AM -0500, Rodrigo Vivi wrote: > > On Thu, Dec 29, 2022 at 04:07:39PM -0300, Gustavo Sousa wrote: > > > Currently there is no DMC version requirement with respect to how i915 > > > interacts with it and

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/dmc: Prepare to use unversioned paths

2022-12-30 Thread Rodrigo Vivi
On Fri, Dec 30, 2022 at 10:36:28AM -0300, Gustavo Sousa wrote: > On Fri, Dec 30, 2022 at 03:47:43AM -0500, Rodrigo Vivi wrote: > > On Thu, Dec 29, 2022 at 04:07:40PM -0300, Gustavo Sousa wrote: > > > New DMC releases in linux-firmware will stop using version number in > > > blob filenames. This new

Re: [Intel-gfx] [PATCH] drm/i915: Expand force_probe to block probe of devices as well.

2022-12-30 Thread Rodrigo Vivi
On Fri, Dec 30, 2022 at 02:42:51PM +0200, Jani Nikula wrote: > On Fri, 30 Dec 2022, Rodrigo Vivi wrote: > > On Thu, Dec 29, 2022 at 03:01:34PM -0300, Gustavo Sousa wrote: > >> On Thu, Dec 29, 2022 at 11:12:30AM -0500, Rodrigo Vivi wrote: > >> > There are new cases where we want to block i915 probe

[Intel-gfx] ✓ Fi.CI.IGT: success for Introduce __xchg, non-atomic xchg (rev3)

2022-12-30 Thread Patchwork
== Series Details == Series: Introduce __xchg, non-atomic xchg (rev3) URL : https://patchwork.freedesktop.org/series/112169/ State : success == Summary == CI Bug Log - changes from CI_DRM_12532_full -> Patchwork_112169v3_full Summary --

[Intel-gfx] [PATCH v4 0/1] drm/i915/dmc: Make firmware loading backwards-compatible

2022-12-30 Thread Gustavo Sousa
This patch series changes DMC loading to be partially backwards-compatible by removing version checking. Future patches in linux-firmware should start using unversioned filenames and we will gradually adapt i915 to use them. For platforms already supported, the change to unversioned paths will req

[Intel-gfx] [PATCH v4 1/1] drm/i915/dmc: Do not require specific versions

2022-12-30 Thread Gustavo Sousa
Currently, i915 interacts with the Hardware and not with any DMC ABI/API, so the API is fixed within the platform, hence no need to get this so-tied version requirement. v2: - Use link to firmware guide from kernel documentation for "References:" instead of mailing list thread. (Rodrigo) -

Re: [Intel-gfx] [PATCH v3 1/2] drm/i915/dmc: Do not require specific versions

2022-12-30 Thread Gustavo Sousa
Thanks for all the feedback. I have just sent a v4 with only this patch. I'll split the second one as instructed. -- Gustavo Sousa On Fri, Dec 30, 2022 at 11:52:07AM -0500, Rodrigo Vivi wrote: > On Fri, Dec 30, 2022 at 09:42:39AM -0300, Gustavo Sousa wrote: > > On Fri, Dec 30, 2022 at 03:32:41AM

[Intel-gfx] [PATCH] drm/i915: Use "%zu" to format size_t

2022-12-30 Thread Nirmoy Das
Switch to %zu for printing size_t which will fix compilation warning for 32-bit build. Reported-by: kernel test robot Signed-off-by: Nirmoy Das --- drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shm

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc: Make firmware loading backwards-compatible (rev4)

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev4) URL : https://patchwork.freedesktop.org/series/112116/ State : warning == Summary == Error: dim checkpatch failed deef1f7547b3 drm/i915/dmc: Do not require specific versions -:16: WARNING:COMMIT_LOG_LO

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dmc: Make firmware loading backwards-compatible (rev4)

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev4) URL : https://patchwork.freedesktop.org/series/112116/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Make firmware loading backwards-compatible (rev4)

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev4) URL : https://patchwork.freedesktop.org/series/112116/ State : success == Summary == CI Bug Log - changes from CI_DRM_12532 -> Patchwork_112116v4 S

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Use "%zu" to format size_t

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915: Use "%zu" to format size_t URL : https://patchwork.freedesktop.org/series/112317/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Use "%zu" to format size_t

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915: Use "%zu" to format size_t URL : https://patchwork.freedesktop.org/series/112317/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12532 -> Patchwork_112317v1 Summary --- **FAILURE

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dmc: Make firmware loading backwards-compatible (rev4)

2022-12-30 Thread Patchwork
== Series Details == Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev4) URL : https://patchwork.freedesktop.org/series/112116/ State : success == Summary == CI Bug Log - changes from CI_DRM_12532_full -> Patchwork_112116v4_full =