Hello Thomas Hellström,
The patch 2f6b90da9192: "drm/i915: Use vma resources for async
unbinding" from Jan 10, 2022, leads to the following Smatch static
checker warning:
drivers/gpu/drm/i915/i915_vma.c:515 i915_vma_bind()
error: we previously assumed 'work->vma_res' could be null
On Fri, 2022-02-25 at 16:41 -0500, Lyude Paul wrote:
> JFYI I've been running the patch on my laptop for about a day now,
> flickering
> is totally gone and also I'm a bit astonished at the power savings!
Good to hear you had now this good user experience with i915 + latest
PSR2 fixes.
> Tested-b
Please ignore this, patch
https://cgit.freedesktop.org/drm-tip/commit/?id=ba1366f3d039e7c3ca1fc29ed00ce3ed2b8fd32f
has already landed today in drm-tip.
Thanks,
Tejas
> -Original Message-
> From: Surendrakumar Upadhyay, TejaskumarX
>
> Sent: 25 February 2022 19:46
> To: intel-gfx@lists.
On Sun, Feb 27, 2022 at 3:04 PM Alex Elder wrote:
>
> Glancing at the Greybus code, I don't believe there's any
> reason it needs to shift a negative value. Such warnings
> could be fixed by making certain variables unsigned, for
> example.
As mentioned in the original thread, making things unsi
On Sun, Feb 27, 2022 at 1:54 PM Arnd Bergmann wrote:
>
> Since the differences between gnu99, gnu11 and gnu17 are fairly minimal
> and mainly impact warnings at the -Wpedantic level that the kernel
> never enables, the easiest way is to just leave out the -std=gnu89
> argument entirely, and rely o
Hi Alan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next
drm/drm-next tegra-drm/drm/tegra/for-next airlied/drm-next v5.17-rc5
next-20220225]
[If your patch is applied to the wrong
== Series Details ==
Series: drm/mm: Add an iterator to optimally walk over holes suitable for an
allocation
URL : https://patchwork.freedesktop.org/series/100796/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11291_full -> Patchwork_22431_full
===
== Series Details ==
Series: drm/mm: Add an iterator to optimally walk over holes suitable for an
allocation
URL : https://patchwork.freedesktop.org/series/100796/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11291 -> Patchwork_22431
=
== Series Details ==
Series: drm/mm: Add an iterator to optimally walk over holes suitable for an
allocation
URL : https://patchwork.freedesktop.org/series/100796/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be chec
== Series Details ==
Series: drm/mm: Add an iterator to optimally walk over holes suitable for an
allocation
URL : https://patchwork.freedesktop.org/series/100796/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
427fbe66bc3d drm/mm: Add an iterator to optimally walk over holes f
The first patch is a drm core patch that replaces the for loop in
drm_mm_insert_node_in_range() with the iterator and would not
cause any functional changes. The second patch is a i915 driver
specific patch that also uses the iterator but solves a different
problem.
v2:
- Added a new patch to this
On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or
more framebuffers/scanout buffers results in only one that is mappable/
fenceable. Therefore, pageflipping between these 2 FBs where only one
is mappable/fenceable creates latencies large enough to miss alternate
vblanks thereby
This iterator relies on drm_mm_first_hole() and drm_mm_next_hole()
functions to identify suitable holes for an allocation of a given
size by efficiently traversing the rbtree associated with the given
allocator.
It replaces the for loop in drm_mm_insert_node_in_range() and can
also be used by drm
Matt,
Thanks for the review.
On 2022-02-18 at 17:47:22 -0800, Matt Roper wrote:
> On Sat, Feb 19, 2022 at 12:17:52AM +0530, Ramalingam C wrote:
> > From: Ayaz A Siddiqui
> >
> > Xe-HP and latest devices support Flat CCS which reserved a portion of
> > the device memory to store compression meta
]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Jordan-Justen/GuC-HWCONFIG-with-documentation/20220
== Series Details ==
Series: drm/i915: Use i915_gem_object_pin_map_unlocked function for lmem
allocation (rev2)
URL : https://patchwork.freedesktop.org/series/98878/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11291_full -> Patchwork_22430_full
=
]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Jordan-Justen/GuC-HWCONFIG-with-documentation/20220
== Series Details ==
Series: GuC HWCONFIG with documentation (rev7)
URL : https://patchwork.freedesktop.org/series/99787/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11291_full -> Patchwork_22429_full
Summary
---
*
== Series Details ==
Series: drm/i915: Use i915_gem_object_pin_map_unlocked function for lmem
allocation (rev2)
URL : https://patchwork.freedesktop.org/series/98878/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11291 -> Patchwork_22430
===
== Series Details ==
Series: drm/i915: Use i915_gem_object_pin_map_unlocked function for lmem
allocation (rev2)
URL : https://patchwork.freedesktop.org/series/98878/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
87952586a365 drm/i915: Use i915_gem_object_pin_map_unlocked funct
== Series Details ==
Series: GuC HWCONFIG with documentation (rev7)
URL : https://patchwork.freedesktop.org/series/99787/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11291 -> Patchwork_22429
Summary
---
**SUCCESS**
== Series Details ==
Series: GuC HWCONFIG with documentation (rev7)
URL : https://patchwork.freedesktop.org/series/99787/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: GuC HWCONFIG with documentation (rev7)
URL : https://patchwork.freedesktop.org/series/99787/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7666ff157a3c drm/i915/guc: Add fetch of hwconfig table
-:108: WARNING:FILE_PATH_CHANGES: added, moved or delet
From: John Harrison
Implement support for fetching the hardware description table from the
GuC. The call is made twice - once without a destination buffer to
query the size and then a second time to fill in the buffer.
The table is stored in the GT structure so that it can be fetched once
at dri
Also, document DRM_I915_QUERY_HWCONFIG_BLOB with this struct.
v3:
* Add various changes suggested by Tvrtko
v5:
* Fix documenation formatting and verified with `make htmldocs` as
suggested by Daniel
Cc: Daniel Vetter
Signed-off-by: Jordan Justen
Acked-by: Jon Bloomfield
Acked-by: Daniel
From: Rodrigo Vivi
The DRM_I915_QUERY_HWCONFIG_BLOB query item returns a blob of data
which it receives from the GuC software. This blob provides some
useful data about the hardware for drivers.
Although the blob is not fully documented at this time, the basic
format is an array of u32 values. T
i915_drm.h now defines the format of the returned
DRM_I915_QUERY_HWCONFIG_BLOB query item. Since i915 receives this from
the black box GuC software, it should verify that the data matches
that format before sending it to user-space.
The verification makes a single simple pass through the blob cont
This is John/Rodrigo's 2 patches with some minor changes, and I added
2 patches.
"drm/i915/uapi: Add query for hwconfig blob" was changed:
* Rename DRM_I915_QUERY_HWCONFIG_TABLE to DRM_I915_QUERY_HWCONFIG_BLOB
as requested by Joonas.
* Reword commit message
* I added Acked-by to this patc
28 matches
Mail list logo