drm/i915/guc: Refactor ADS access to use dma_buf_map
Subsystems (3)
cover drm/i915/guc: Refactor ADS access to use dma_buf_map
While porting i915 to arm64 we noticed some issues accessing lmem. Some writes were getting corrupted and the final state of the buffer didn't have exactly what we wrote. This became evident when enabling GuC submission: depending on the number of engines the ADS struct was being corrupted and GuC would reject it, refusin to initialize.
From Documentation/core-api/bus-virt-phys-mapping.rst:
This memory is called "PCI memory" or "shared memory" or "IO memory" or whatever, and there is only one way to access it: the readb/writeb and related functions. You should never take the address of such memory, because there is really nothing you can do with such an address: it's not conceptually in the same memory space as "real memory" at all, so you cannot just dereference a pointer. (Sadly, on x86 it **is** in the same memory space, so on x86 it actually works to just deference a pointer, but it's not portable).
When reading or writing words directly to IO memory, in order to be portable the Linux kernel provides the abstraction detailed in section "Differences between I/O access functions" of Documentation/driver-api/device-io.rst.
This limits our ability to simply overlay our structs on top a buffer and directly access it since that buffer may come from IO memory rather than system memory. Hence the approach taken in intel_guc_ads.c needs to be refactored. This is not the only place in i915 that neeed to be changed, but the one causing the most problems, with a real reproducer. This first set of patch focuses on fixing the gem object to pass the ADS
After the addition of a few helpers in the dma_buf_map API, most of intel_guc_ads.c can be converted to use it. The exception is the regset
initialization: we'd incur into a lot of extra indirection when reading/writting each register. So the regset is converted to use a temporary buffer allocated on probe, which is then copied to its final location when finishing the initialization or on gt reset.
Testing on some discrete cards, after this change we can correctly pass the ADS struct to GuC and have it initialized correctly.
thanks
Lucas De Marchi
Lucas De Marchi (19):
dma-buf-map: Add read/write helpers
dma-buf-map: Add helper to initialize second map drm/i915/gt: Add helper for shmem copy to dma_buf_map drm/i915/guc: Keep dma_buf_map of ads_blob around drm/i915/guc: Add read/write helpers for ADS blob drm/i915/guc: Convert golden context init to dma_buf_map drm/i915/guc: Convert policies update to dma_buf_map drm/i915/guc: Convert engine record to dma_buf_map
dma-buf-map: Add wrapper over memset
drm/i915/guc: Convert guc_ads_private_data_reset to dma_buf_map drm/i915/guc: Convert golden context prep to dma_buf_map drm/i915/guc: Replace check for golden context size drm/i915/guc: Convert mapping table to dma_buf_map drm/i915/guc: Convert capture list to dma_buf_map drm/i915/guc: Prepare for error propagation drm/i915/guc: Use a single pass to calculate regset drm/i915/guc: Convert guc_mmio_reg_state_init to dma_buf_map drm/i915/guc: Convert __guc_ads_init to dma_buf_map drm/i915/guc: Remove plain ads_blob pointer
drivers/gpu/drm/i915/gt/shmem_utils.c | 32 ++ drivers/gpu/drm/i915/gt/shmem_utils.h | 3 + drivers/gpu/drm/i915/gt/uc/intel_guc.h | 14 +- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 374 +++++++++++------- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.h | 3 +- .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 11 +- include/linux/dma-buf-map.h | 127 ++++++ 7 files changed, 405 insertions(+), 159 deletions(-)
Signature · 1 line
2.35.0
PATCH 1/19 dma-buf-map: Add read/write helpers
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.
--- include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)
include/linux/dma-buf-map.h +81 -0
@@ -6,6 +6,7 @@#ifndef __DMA_BUF_MAP_H__#define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h>
@@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in +* system memory. Depending on the buffer's location, the helper picks the +* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_to_offset (struct dma_buf_map *dst,size_t offset, +const void *src,size_t len) +{ +if (dst->is_iomem) +memcpy_toio (dst->vaddr_iomem + offset, src, len); +else +memcpy (dst->vaddr + offset, src, len); +} + +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory +* @dst: Destination in system memory +* @src: The dma-buf mapping structure +* @src: The offset from which to copy +* @len: The number of byte in src +* +* Copies data from a dma-buf mapping with an offset. The dest buffer is in +* system memory. Depending on the mapping location, the helper picks the +* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_from_offset (void *dst,const struct dma_buf_map *src, +size_t offset,size_t len) +{ +if (src->is_iomem) +memcpy_fromio (dst, src->vaddr_iomem + offset, len); +else +memcpy (dst, src->vaddr + offset, len); +} +/** * dma_buf_map_memcpy_to - Memcpy into dma-buf mapping * @dst: The dma-buf mapping structure
@@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ +#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +}) +#endif /* __DMA_BUF_MAP_H__ */
Signature · 1 line
2.35.0
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 70 lines
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the
dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)include/linux/dma-buf-map.h +31
-0@@ -6,6 +6,7 @@#ifndef __DMA_BUF_MAP_H__#define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h> @@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in +* system memory. Depending on the buffer's location, the helper picks the +* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_to_offset (struct dma_buf_map *dst,size_t offset, +const void *src,size_t len) +{ +if (dst->is_iomem) +memcpy_toio (dst->vaddr_iomem + offset, src, len); +else +memcpy (dst->vaddr + offset, src, len); +} + +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory +* @dst: Destination in system memory +* @src: The dma-buf mapping structure +* @src: The offset from which to copy +* @len: The number of byte in src +* +* Copies data from a dma-buf mapping with an offset. The dest buffer is in +* system memory. Depending on the mapping location, the helper picks the +* correct method of accessing the memory.
include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 272
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+*/ +static inline void dma_buf_map_memcpy_from_offset (void *dst,const struct dma_buf_map *src, +size_t offset,size_t len) +{ +if (src->is_iomem) +memcpy_fromio (dst, src->vaddr_iomem + offset, len); +else +memcpy (dst, src->vaddr + offset, len); +} +
Well that's certainly a valid use case, but I suggest to change the implementation of the existing functions to call the new ones with offset=0.
This way we only have one implementation.
Quoted 37 lines
include/linux/dma-buf-map.h +30
-0/** * dma_buf_map_memcpy_to - Memcpy into dma-buf mapping * @dst: The dma-buf mapping structure @@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size.
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 346
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ +#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +}) +
Uff well that absolutely looks like overkill to me.
That's a rather special use case as far as I can see and I think we should only have this in the common framework if more than one driver is using it.
Regards,
Christian.
Quoted 1 line
include/linux/dma-buf-map.h +0
-0#endif /* __DMA_BUF_MAP_H__ */
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
Quoted 82 lines · Christian König
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 67 lines
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the
dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)include/linux/dma-buf-map.h +31
-0@@ -6,6 +6,7 @@#ifndef __DMA_BUF_MAP_H__#define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h> @@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in +* system memory. Depending on the buffer's location, the helper picks the +* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_to_offset (struct dma_buf_map *dst,size_t offset, +const void *src,size_t len) +{ +if (dst->is_iomem) +memcpy_toio (dst->vaddr_iomem + offset, src, len); +else +memcpy (dst->vaddr + offset, src, len); +} + +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory +* @dst: Destination in system memory +* @src: The dma-buf mapping structure +* @src: The offset from which to copy +* @len: The number of byte in src +* +* Copies data from a dma-buf mapping with an offset. The dest buffer is in +* system memory. Depending on the mapping location, the helper picks the +* correct method of accessing the memory. include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 271
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+*/ +static inline void dma_buf_map_memcpy_from_offset (void *dst,const struct dma_buf_map *src, +size_t offset,size_t len) +{ +if (src->is_iomem) +memcpy_fromio (dst, src->vaddr_iomem + offset, len); +else +memcpy (dst, src->vaddr + offset, len); +} +Well that's certainly a valid use case, but I suggest to change the implementation of the existing functions to call the new ones with offset=0.
Quoted 2 lines
This way we only have one implementation.
Trivial - but agree with Christian that is a good cleanup.
Quoted 40 lines
Quoted 40 lines
include/linux/dma-buf-map.h +34
-0/** * dma_buf_map_memcpy_to - Memcpy into dma-buf mapping * @dst: The dma-buf mapping structure @@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ +#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \
Quoted 9 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 346
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+type__ *t__; \ + typeof(t__->field__) val____ = val__; \ +dma_buf_map_memcpy_to_offset (map__, offsetof(type__ , field__), \ + &val____,sizeof (t__->field__)); \ +}) +Uff well that absolutely looks like overkill to me.
Hold on...
Quoted 3 lines
That's a rather special use case as far as I can see and I think we should only have this in the common framework if more than one driver is using it.
I disagree, this is rather elegant.
The i915 can't be the *only* driver that defines a struct which describes the layout of a dma_buf object.
IMO this base macro allows *all* other drivers to build on this write directly to fields in structures those drivers have defined. Patches later in this series do this for the GuC ads.
Matt
Quoted 5 lines
Regards,
Christian.Quoted 1 line
include/linux/dma-buf-map.h +0
-0#endif /* __DMA_BUF_MAP_H__ */
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
Am 27.01.22 um 08:36 schrieb Matthew Brost:
Quoted 51 lines
[SNIP]
Quoted 39 lines
Quoted 39 lines
/**
*dma_buf_map_memcpy_to- Memcpy into dma-buf mapping
* @dst: The dma-buf mapping structureinclude/linux/dma-buf-map.h +33
-0@@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ Quoted 9 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 346
Quoted 7 lines
include/linux/dma-buf-map.h +7
-0+#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +}) +Uff well that absolutely looks like overkill to me.
Hold on...
Quoted 7 lines
Quoted 3 lines
That's a rather special use case as far as I can see and I think we should only have this in the common framework if more than one driver is using it.
I disagree, this is rather elegant.
The i915 can't be the *only* driver that defines a struct which describes the layout of a
dma_bufobject.
That's not the problem, amdgpu as well as nouveau are doing that as well. The problem is DMA-buf is a buffer sharing framework between drivers.
In other words which importer is supposed to use this with a DMA-buf exported by another device?
Quoted 2 lines
IMO this base macro allows *all* other drivers to build on this write directly to fields in structures those drivers have defined.
Exactly that's the point. This is something drivers should absolutely *NOT* do.
That are driver internals and it is extremely questionable to move this into the common framework.
Regards,
Christian.
Quoted 9 lines
Patches
later in this series do this for the GuC ads.Matt
Quoted 4 lines
Regards,
Christian.Quoted 1 line
include/linux/dma-buf-map.h +0
-0#endif /* __DMA_BUF_MAP_H__ */
Re: [Intel-gfx] [PATCH 01/19] dma-buf-map: Add read/write helpers
Quoted 66 lines · Christian König
Am 27.01.22 um 08:36 schrieb Matthew Brost:
Quoted 51 lines
[SNIP]
Quoted 39 lines
Quoted 39 lines
/**
*dma_buf_map_memcpy_to- Memcpy into dma-buf mapping
* @dst: The dma-buf mapping structureinclude/linux/dma-buf-map.h +33
-0@@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ Quoted 9 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 346
Quoted 7 lines
include/linux/dma-buf-map.h +7
-0+#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +}) +Uff well that absolutely looks like overkill to me.
Hold on...
Quoted 7 lines
Quoted 3 lines
That's a rather special use case as far as I can see and I think we should only have this in the common framework if more than one driver is using it.
I disagree, this is rather elegant.
The i915 can't be the *only* driver that defines a struct which describes the layout of a
dma_bufobject.That's not the problem, amdgpu as well as nouveau are doing that as well. The problem is DMA-buf is a buffer sharing framework between drivers.
In other words which importer is supposed to use this with a DMA-buf exported by another device?
Quoted 8 lines
Quoted 2 lines
IMO this base macro allows *all* other drivers to build on this write directly to fields in structures those drivers have defined.
Exactly that's the point. This is something drivers should absolutely *NOT* do.
That are driver internals and it is extremely questionable to move this into the common framework.
See my other reply.
This is about struct dma_buf_map, which is just a tagged pointer.
Which happens to be used by the dma_buf cross-driver interface, but it's also used plenty internally in buffer allocation helpers, fbdev, everything else. And it was _meant_ to be used like that - this thing is my idea, I know :-)
I guess we could move/rename it, but like I said I really don't have any good ideas. Got some?
-Daniel
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
In reply to Lucas De MarchiHi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 49 lines
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the
dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)include/linux/dma-buf-map.h +10
-0@@ -6,6 +6,7 @@#ifndef __DMA_BUF_MAP_H__#define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h> @@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in +* system memory. Depending on the buffer's location, the helper picks the
include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 251
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_to_offset (struct dma_buf_map *dst,size_t offset, +const void *src,size_t len) +{ +if (dst->is_iomem) +memcpy_toio (dst->vaddr_iomem + offset, src, len); +else +memcpy (dst->vaddr + offset, src, len); +}
Please don't add a new function. Rather please add the offset parameter to dma_buf_map_memcpy_to() and update the callers. There are only two calls to dma_buf_map_memcpy_to() within the kernel. To make it clear what the offset applies to, I'd call the parameter 'dst_offset'.
Quoted 11 lines
include/linux/dma-buf-map.h +11
-0+ +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory +* @dst: Destination in system memory +* @src: The dma-buf mapping structure +* @src: The offset from which to copy +* @len: The number of byte in src +* +* Copies data from a dma-buf mapping with an offset. The dest buffer is in +* system memory. Depending on the mapping location, the helper picks the +* correct method of accessing the memory.
include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 272
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+*/ +static inline void dma_buf_map_memcpy_from_offset (void *dst,const struct dma_buf_map *src, +size_t offset,size_t len) +{ +if (src->is_iomem) +memcpy_fromio (dst, src->vaddr_iomem + offset, len); +else +memcpy (dst, src->vaddr + offset, len); +} +
With the dma_buf_map_memcpy_to() changes, please just call this function dma_buf_map_memcpy_from().
Quoted 36 lines
include/linux/dma-buf-map.h +29
-0/** * dma_buf_map_memcpy_to - Memcpy into dma-buf mapping * @dst: The dma-buf mapping structure @@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +*
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 345
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/ +#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +})
As the original author of this file, I feel like this shouldn't be here. At least not until we have another driver using that pattern.
Best regards
Thomas
Quoted 2 lines
include/linux/dma-buf-map.h +1
-0+#endif /* __DMA_BUF_MAP_H__ */
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
Quoted 125 lines · Thomas Zimmermann
Hi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 46 lines
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the
dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+)include/linux/dma-buf-map.h +10
-0@@ -6,6 +6,7 @@#ifndef __DMA_BUF_MAP_H__#define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h> @@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in +* system memory. Depending on the buffer's location, the helper picks the include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 250
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* correct method of accessing the memory. +*/ +static inline void dma_buf_map_memcpy_to_offset (struct dma_buf_map *dst,size_t offset, +const void *src,size_t len) +{ +if (dst->is_iomem) +memcpy_toio (dst->vaddr_iomem + offset, src, len); +else +memcpy (dst->vaddr + offset, src, len); +}Please don't add a new function. Rather please add the offset parameter to
dma_buf_map_memcpy_to()and update the callers. There are only two calls todma_buf_map_memcpy_to()within the kernel. To make it clear what the offset applies to, I'd call the parameter 'dst_offset'.Quoted 11 lines
include/linux/dma-buf-map.h +11
-0+ +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory +* @dst: Destination in system memory +* @src: The dma-buf mapping structure +* @src: The offset from which to copy +* @len: The number of byte in src +* +* Copies data from a dma-buf mapping with an offset. The dest buffer is in +* system memory. Depending on the mapping location, the helper picks the +* correct method of accessing the memory. include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 272
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+*/ +static inline void dma_buf_map_memcpy_from_offset (void *dst,const struct dma_buf_map *src, +size_t offset,size_t len) +{ +if (src->is_iomem) +memcpy_fromio (dst, src->vaddr_iomem + offset, len); +else +memcpy (dst, src->vaddr + offset, len); +} +With the
dma_buf_map_memcpy_to()changes, please just call this functiondma_buf_map_memcpy_from().Quoted 39 lines
include/linux/dma-buf-map.h +33
-0/** * dma_buf_map_memcpy_to - Memcpy into dma-buf mapping * @dst: The dma-buf mapping structure @@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to read +* @field__: Member from struct we want to read +* +* Read a value from dma-buf mapping calculating the offset and size: this assumes +* the dma-buf mapping is aligned with a a struct type__. A single u8, u16, u32 +* or u64 can be read, based on the offset and size of type__.field__. +*/ +#define dma_buf_map_read_field (map__, type__, field__) ({ \ + type__ *t__; \ + typeof(t__->field__) val__; \ + dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \ + sizeof(t__->field__)); \ + val__; \ +}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with +* arbitrary size and handling un-aligned accesses +* +* @map__: The dma-buf mapping structure +* @type__: The struct to be used containing the field to write +* @field__: Member from struct we want to write +* @val__: Value to be written +* +* Write a value to the dma-buf mapping calculating the offset and size. +* A single u8, u16, u32 or u64 can be written based on the offset and size of +* type__.field__. +*/
Quoted 8 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) · line 345
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+#define dma_buf_map_write_field (map__, type__, field__, val__) ({ \ + type__ *t__; \ + typeof(t__->field__) val____ = val__; \ + dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \ + &val____, sizeof(t__->field__)); \ +})As the original author of this file, I feel like this shouldn't be here. At least not until we have another driver using that pattern.
Let me try to clear out the confusion. Then maybe I can extend the documentation of this function in v2 if I'm able to convince this is useful here.
This is not about importer/exporter, having this to work cross-driver. This is about using dma_buf_map (which we are talking about on renaming to iosys_map or something else) for inner driver allocations/abstractions. The abstraction added by iosys_map helps on sharing the same functions we had before. And this macro here is very useful when the buffer is described by a struct layout. Example:
struct bla {
struct inner inner1;
struct inner inner2;
u32 x, y ,z;
};Functions that would previously do:
struct bla *bla = ...; bla->x = 100; bla->y = 200; bla->inner1.inner_inner_field = 30;
Can do the below, having the system/IO memory abstracted away (calling it iosys_map here instead of dma_buf_map, hopeful it helps):
struct iosys_map *map = ...; iosys_map_write_field(map, struct bla, x, 100); iosys_map_write_field(map, struct bla, y, 200); iosys_map_write_field(map, struct bla, inner1.inner_inner_field, 30);
When we are using mostly the same map, the individual drivers can add quick helpers on top. See the ads_blob_write() added in this series, which guarantees the map it's working on is always the guc->ads_map, while reducing verbosity to use the API. From patch "drm/i915/guc: Add read/write helpers for ADS blob":
#define ads_blob_read(guc_, field_) \
dma_buf_map_read_field(&(guc_)->ads_map, struct __guc_ads_blob, \
field_)#define ads_blob_write(guc_, field_, val_) \
dma_buf_map_write_field(&(guc_)->ads_map, struct __guc_ads_blob,\
field_, val_)So in intel_guc_ads, we can have a lot of:
- bla->x = 100;
+ ads_blob_write(guc, x, 10);
thanks
Lucas De Marchi
Re: [PATCH 01/19] dma-buf-map: Add read/write helpers
Hi
Am 27.01.22 um 17:34 schrieb Lucas De Marchi:
Quoted 175 lines · Thomas Zimmermann
Quoted 144 lines
Hi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 54 lines
In certain situations it's useful to be able to read or write to an offset that is calculated by having the memory layout given by a struct declaration. Usually we are going to read/write a u8, u16, u32 or u64.
Add a pair of macros dma_buf_map_read_field()/dma_buf_map_write_field() to calculate the offset of a struct member and memcpy the data from/to the
dma_buf_map. We could use readb, readw, readl, readq and the write* counterparts, however due to alignment issues this may not work on all architectures. If alignment needs to be checked to call the right function, it's not possible to decide at compile-time which function to
call: so just leave the decision to the memcpy function that will do exactly that on IO memory or dereference the pointer.Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>---
include/linux/dma-buf-map.h | 81 +++++++++++++++++++++++++++++++++++++1 file changed, 81 insertions(+)include/linux/dma-buf-map.h +9
-0@@ -6,6 +6,7 @@ #ifndef __DMA_BUF_MAP_H__ #define __DMA_BUF_MAP_H__ +#include <linux/kernel.h> #include <linux/io.h> #include <linux/string.h>@@ -229,6 +230,46 @@ static inline void dma_buf_map_clear(struct dma_buf_map *map) } } +/** +* dma_buf_map_memcpy_to_offset - Memcpy into offset of dma-buf mapping +* @dst: The dma-buf mapping structure +* @offset: The offset from which to copy +* @src: The source buffer +* @len: The number of byte in src +* +* Copies data into a dma-buf mapping with an offset. The source buffer is in
+ * system memory. Depending on the buffer's location, the helper picks the
+ * correct method of accessing the memory.
+ */
+static inline void dma_buf_map_memcpy_to_offset(structdma_buf_map*dst,size_toffset,
+ const void *src,size_tlen)include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 251
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+{ + if (dst->is_iomem) + memcpy_toio(dst->vaddr_iomem + offset, src, len); + else + memcpy(dst->vaddr + offset, src, len); +}Please don't add a new function. Rather please add the offset parameter to
dma_buf_map_memcpy_to()and update the callers. There are only two calls todma_buf_map_memcpy_to()within the kernel. To make it clear what the offset applies to, I'd call the parameter 'dst_offset'.Quoted 18 lines
include/linux/dma-buf-map.h +3
-0+ +/** +* dma_buf_map_memcpy_from_offset - Memcpy from offset of dma-buf mapping into system memory
+ * @dst: Destination in system memory
+ * @src: The dma-buf mapping structure
+ * @src: The offset from which to copy
+ * @len: The number of byte in src
+ *
+ * Copies data from a dma-buf mapping with an offset. The dest buffer is in
+ * system memory. Depending on the mapping location, the helper picks the
+ * correct method of accessing the memory.
+ */
+static inline void dma_buf_map_memcpy_from_offset(void *dst, const structdma_buf_map*src,
+size_toffset,size_tlen)include/linux/dma-buf-map.h static inline void dma_buf_map_clear(struct dma_buf_map *map) · line 272
Quoted 7 lines
include/linux/dma-buf-map.h +7
-0+{ + if (src->is_iomem) + memcpy_fromio(dst, src->vaddr_iomem + offset, len); + else + memcpy(dst, src->vaddr + offset, len); +} +With the
dma_buf_map_memcpy_to()changes, please just call this functiondma_buf_map_memcpy_from().Quoted 50 lines
/**
*dma_buf_map_memcpy_to- Memcpy into dma-buf mapping
* @dst: The dma-buf mapping structureinclude/linux/dma-buf-map.h +2
-0@@ -263,4 +304,44 @@ static inline void dma_buf_map_incr(struct dma_buf_map *map, size_t incr) map->vaddr += incr; } +/** +* dma_buf_map_read_field - Read struct member from dma-buf mapping with
+ * arbitrary size and handling un-aligned accesses
+ *
+ * @map__: The dma-buf mapping structure
+ * @type__: The struct to be used containing the field to read
+ * @field__: Member from struct we want to read
+ *
+ * Read a value from dma-buf mapping calculating the offset and
size: this assumes
+ * the dma-buf mapping is aligned with a a structtype__. A single u8, u16, u32
+ * or u64 can be read, based on the offset and size of type__.field__.
+ */
+#definedma_buf_map_read_field(map__, type__, field__)
({ \
+type__*t__; \
+typeof(t__->field__)val__; \
+ dma_buf_map_memcpy_from_offset(&val__,map__,offsetof(type__, field__), \
+ sizeof(t__->field__)); \
+ val__; \include/linux/dma-buf-map.h +4
-0+}) + +/** +* dma_buf_map_write_field - Write struct member to the dma-buf mapping with
+ * arbitrary size and handling un-aligned accesses
+ *
+ * @map__: The dma-buf mapping structure
+ * @type__: The struct to be used containing the field to write
+ * @field__: Member from struct we want to write
+ * @val__: Value to be written
+ *
+ * Write a value to the dma-buf mapping calculating the offset and size.
+ * A single u8, u16, u32 or u64 can be written based on the offset and size of
+ * type__.field__.
+ */
+#definedma_buf_map_write_field(map__, type__, field__, val__)({ \Quoted 8 lines
Quoted 6 lines
+
type__*t__; \
+typeof(t__->field__)val____= val__; \
+ dma_buf_map_memcpy_to_offset(map__,offsetof(type__, field__), \
+&val____, sizeof(t__->field__)); \
+})As the original author of this file, I feel like this shouldn't be here. At least not until we have another driver using that pattern.
Let me try to clear out the confusion. Then maybe I can extend the documentation of this function in v2 if I'm able to convince this is useful here.
This is not about importer/exporter, having this to work cross-driver. This is about using
dma_buf_map(which we are talking about on renaming toiosys_mapor something else) for inner driver allocations/abstractions. The abstraction added byiosys_maphelps on sharing the same functions we had before. And this macro here is very useful when the buffer is described by a struct layout. Example:struct bla {
struct inner inner1;
struct inner inner2;
u32 x, y ,z;
};Functions that would previously do:
struct bla *bla = ...;
Quoted 8 lines
bla->x = 100;
bla->y = 200;
bla->inner1.inner_inner_field = 30;Can do the below, having the system/IO memory abstracted away (calling it
iosys_maphere instead ofdma_buf_map, hopeful it helps):struct
iosys_map*map = ...;
Please don't start renaming anything here. If we want to do this, let's have a separate mail thread for coloring the bike shed.
Quoted 5 lines
iosys_map_write_field(map, struct bla, x, 100);
iosys_map_write_field(map, struct bla, y, 200);iosys_map_write_field(map, struct bla, inner1.inner_inner_field, 30);
I don't have strong feelings about these macros. They just seemed not needed in general. But I we want to add them here, I 'd like to propose a few small changes.
Again, please add an offset parameter for the map's pointer.
Then I'd call them either dma_buf_map_rd/dma_buf_map_wr for read/write OR dma_buf_map_ld/dma_buf_map_st for load/store. They should take a C type. Something like this
dma_buf_map_wr(map, offset, int32, 0x01234); val = dam_buf_map_rd(map, offset, int32);
Hopefully, that's flexible enough for all users. On top of that, you can build additional helpers like dma_buf_map_rd_field() and dma_buf_map_wr_field().
Ok?
Best regards
Thomas
Quoted 22 lines
When we are using mostly the same map, the individual drivers can add quick helpers on top. See the
ads_blob_write()added in this series, which guarantees the map it's working on is always theguc->ads_map, while reducing verbosity to use the API. From patch "drm/i915/guc: Add read/write helpers for ADS blob":#define
ads_blob_read(guc_, field_)\
dma_buf_map_read_field(&(guc_)->ads_map, struct__guc_ads_blob, \
field_)#define
ads_blob_write(guc_, field_, val_)\
dma_buf_map_write_field(&(guc_)->ads_map, struct __guc_ads_blob,\
field_,val_)So in
intel_guc_ads, we can have a lot of:-
bla->x= 100;
+ads_blob_write(guc, x, 10);thanks
Lucas De Marchi
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
PATCH 2/19 dma-buf-map: Add helper to initialize second map
In reply to Lucas De MarchiWhen dma_buf_map struct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.
Add a helper that copies the struct and add the offset to the proper address.
--- include/linux/dma-buf-map.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)
include/linux/dma-buf-map.h +29 -0
@@ -131,6 +131,35 @@ struct dma_buf_map { .is_iomem = false, \ } +/** +* DMA_BUF_MAP_INIT_OFFSET - Initializes struct dma_buf_map from another dma_buf_map +* @map_: The dma-buf mapping structure to copy from +* @offset: Offset to add to the other mapping +* +* Initializes a new dma_buf_struct based on another. This is the equivalent of doing: +* +* .. code-block: c +* +* dma_buf_map map = other_map; +* dma_buf_map_incr(&map, &offset); +* +* Example usage: +* +* .. code-block: c +* +* void foo(struct device *dev, struct dma_buf_map *base_map) +* { +* ... +* struct dma_buf_map = DMA_BUF_MAP_INIT_OFFSET(base_map, FIELD_OFFSET); +* ... +* } +*/ +#define DMA_BUF_MAP_INIT_OFFSET (map_, offset_) (struct dma_buf_map) \ + { \ + .vaddr = (map_)->vaddr + (offset_), \ + .is_iomem = (map_)->is_iomem, \ + } +/** * dma_buf_map_set_vaddr - Sets a dma-buf mapping structure to an address in system memory * @map: The dma-buf mapping structure
Signature · 1 line
2.35.0
Re: [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct dma_buf_map is only to be filled in by the exporter and should not be modified in this way by the importer.
If you need to copy only a certain subset of the mapping use the functions you added in patch #1.
Regards,
Christian.
Quoted 52 lines
Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)include/linux/dma-buf-map.h +29
-0@@ -131,6 +131,35 @@ struct dma_buf_map { .is_iomem = false, \ } +/** +* DMA_BUF_MAP_INIT_OFFSET - Initializes struct dma_buf_map from another dma_buf_map +* @map_: The dma-buf mapping structure to copy from +* @offset: Offset to add to the other mapping +* +* Initializes a new dma_buf_struct based on another. This is the equivalent of doing: +* +* .. code-block: c +* +* dma_buf_map map = other_map; +* dma_buf_map_incr(&map, &offset); +* +* Example usage: +* +* .. code-block: c +* +* void foo(struct device *dev, struct dma_buf_map *base_map) +* { +* ... +* struct dma_buf_map = DMA_BUF_MAP_INIT_OFFSET(base_map, FIELD_OFFSET); +* ... +* } +*/ +#define DMA_BUF_MAP_INIT_OFFSET (map_, offset_) (struct dma_buf_map) \ + { \ + .vaddr = (map_)->vaddr + (offset_), \ + .is_iomem = (map_)->is_iomem, \ + } +/** * dma_buf_map_set_vaddr - Sets a dma-buf mapping structure to an address in system memory * @map: The dma-buf mapping structure
Re: [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 11 lines · Christian König
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.
humn... not sure if I was clear. There is no importer and exporter here. There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct dma_buf_map *bla_map) { ... }
fill_bar(struct dma_buf_map *bla_map) { ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
struct dma_buf_map map = *bla_map; dma_buf_map_incr(map, offsetof(...));
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De Marchi
Re: [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 6 lines · Christian König
Quoted 5 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 4 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Regards,
Christian.
Quoted 35 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }
fill_bar(structdma_buf_map*bla_map) { ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De Marchi
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 14 lines · Christian König
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 11 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.
Quoted 7 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
s/you guys/you/ if you have to blame anyone - I'm the only s-o-b in these patches. I'm sending these to _build consensus_ on what may be a good use for it showing a real problem it's helping to fix.
From its documentation:
* The type :c:type:struct dma_buf_map <dma_buf_map> and its helpers are
* actually independent from the dma-buf infrastructure. When sharing buffers
* among devices, drivers have to know the location of the memory to access
* the buffers in a safe way. :c:type:struct dma_buf_map <dma_buf_map>
* solves this problem for dma-buf and its users. If other drivers or
* sub-systems require similar functionality, the type could be generalized
* and moved to a more prominent header file.
if there is no consensus and a better alternative, I'm perfectly fine in throwing it out and using the better approach.
Lucas De Marchi
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 27.01.22 um 09:18 schrieb Lucas De Marchi:
Quoted 9 lines · Christian König
Quoted 8 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 4 lines · Christian König
Quoted 2 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 1 line
[SNIP]
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
Quoted 7 lines
Quoted 3 lines
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
s/you guys/you/ if you have to blame anyone - I'm the only s-o-b in these patches. I'm sending these to
_buildconsensus_on what may be a good use for it showing a real problem it's helping to fix.
Well a cover letter would have been helpful, my impression was that you have a larger set and just want to upstream some minor DMA-buf changes necessary for it.
Now I know why people are bugging me all the time to add cover letters to add more context to my sets.
Quoted 11 lines
From its documentation:
* The type :c:type:
struct dma_buf_map <dma_buf_map>and its helpers are
* actually independent from the dma-buf infrastructure. When sharing buffers
* among devices, drivers have to know the location of the memory to access
* the buffers in a safe way. :c:type:struct dma_buf_map <dma_buf_map>
* solves this problem for dma-buf and its users. If other drivers or
* sub-systems require similar functionality, the type could be generalized
* and moved to a more prominent header file.
Quoted 2 lines
if there is no consensus and a better alternative, I'm perfectly fine in throwing it out and using the better approach.
When Thomas Zimmermann upstreamed the dma_buf_map work we had a discussion if that shouldn't be independent of the DMA-buf framework.
The consensus was that as soon as we have more widely use for it this should be made independent. So basically that is what's happening now.
I suggest the following approach:
1. Find a funky name for this, something like iomem_, kiomap_ or similar.
2. Separate this from all you driver dependent work and move the dma_buf_map structure out of DMA-buf into this new whatever_ prefix.
3. Ping Thomas, LKML, me and probably a couple of other core people if this is the right idea or not.
4. Work on dropping the map parameter from dma_buf_vunmap(). This is basically why we can't modify the pointers returned from dma_buf_vmap() and has already cause a few problems with dma_buf_map_incr().
Regards,
Christian.
Quoted 2 lines
Lucas De Marchi
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 12 lines · Christian König
Am 27.01.22 um 09:18 schrieb Lucas De Marchi:
Quoted 11 lines · Christian König
Quoted 10 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 4 lines · Christian König
Quoted 2 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 1 line
[SNIP]
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
s/you guys/you/ if you have to blame anyone - I'm the only s-o-b in these patches. I'm sending these to
_buildconsensus_on what may be a good use for it showing a real problem it's helping to fix.Well a cover letter would have been helpful, my impression was that you have a larger set and just want to upstream some minor DMA-buf changes necessary for it.
I missed adding this sentence to the cover letter, as my impression was that dma-buf-map was already used outside inter-driver framework. But there is actually a cover letter:
https://lore.kernel.org/all/[email protected]/
And looking at it now, it seems I missed adding Thomas Zimmermann to Cc.
Quoted 17 lines
Now I know why people are bugging me all the time to add cover letters to add more context to my sets.
Quoted 11 lines
From its documentation:
* The type :c:type:
struct dma_buf_map <dma_buf_map>and its helpers are
* actually independent from the dma-buf infrastructure. When sharing buffers
* among devices, drivers have to know the location of the memory to access
* the buffers in a safe way. :c:type:struct dma_buf_map <dma_buf_map>
* solves this problem for dma-buf and its users. If other drivers or
* sub-systems require similar functionality, the type could be generalized
* and moved to a more prominent header file.Quoted 2 lines
if there is no consensus and a better alternative, I'm perfectly fine in throwing it out and using the better approach.
Quoted 6 lines
When Thomas Zimmermann upstreamed the
dma_buf_mapwork we had a discussion if that shouldn't be independent of the DMA-buf framework.The consensus was that as soon as we have more widely use for it this should be made independent. So basically that is what's happening now.
I suggest the following approach:
1. Find a funky name for this, something likeiomem_,kiomap_or similar.
iosys_map?
Quoted 1 line
2. Separate this from all you driver dependent work and move the
dma_buf_mapstructure out of DMA-buf into this newwhatever_prefix.
should this be a follow up to the driver work or a prerequisite?
thanks
Lucas De Marchi
Quoted 9 lines
3. Ping Thomas, LKML, me and probably a couple of other core people if this is the right idea or not.
4. Work on dropping the map parameter fromdma_buf_vunmap(). This is basically why we can't modify the pointers returned fromdma_buf_vmap()and has already cause a few problems withdma_buf_map_incr().Regards,
Christian.Quoted 2 lines
Lucas De Marchi
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 27.01.22 um 10:12 schrieb Lucas De Marchi:
Quoted 47 lines · Christian König
Quoted 12 lines
Am 27.01.22 um 09:18 schrieb Lucas De Marchi:
Quoted 11 lines · Christian König
Quoted 10 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 4 lines · Christian König
Quoted 2 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 1 line
[SNIP]
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
s/you guys/you/ if you have to blame anyone - I'm the only s-o-b in these patches. I'm sending these to
_buildconsensus_on what may be a good use for it showing a real problem it's helping to fix.Well a cover letter would have been helpful, my impression was that you have a larger set and just want to upstream some minor DMA-buf changes necessary for it.
I missed adding this sentence to the cover letter, as my impression was that dma-buf-map was already used outside inter-driver framework. But there is actually a cover letter:
And looking at it now, it seems I missed adding Thomas Zimmermann to Cc.
Quoted 17 lines
Now I know why people are bugging me all the time to add cover letters to add more context to my sets.
Quoted 13 lines
From its documentation:
* The type :c:type:
struct dma_buf_map <dma_buf_map>and its helpers are
* actually independent from the dma-buf infrastructure. When sharing buffers
* among devices, drivers have to know the location of the memory to access
* the buffers in a safe way. :c:type:struct dma_buf_map <dma_buf_map>
* solves this problem for dma-buf and its users. If other drivers or
* sub-systems require similar functionality, the type could be generalized
* and moved to a more prominent header file.if there is no consensus and a better alternative, I'm perfectly fine in throwing it out and using the better approach.
Quoted 8 lines
Quoted 6 lines
When Thomas Zimmermann upstreamed the
dma_buf_mapwork we had a discussion if that shouldn't be independent of the DMA-buf framework.The consensus was that as soon as we have more widely use for it this should be made independent. So basically that is what's happening now.
I suggest the following approach:
1. Find a funky name for this, something likeiomem_,kiomap_or similar.
iosys_map?
Works for me.
Quoted 4 lines
Quoted 2 lines
2. Separate this from all you driver dependent work and move the
dma_buf_mapstructure out of DMA-buf into this newwhatever_prefix.should this be a follow up to the driver work or a prerequisite?
Prerequisite. Structural changes like this always separate to the actually work switching over to them because the later needs a much fewer audience for review.
Regards,
Christian.
Quoted 13 lines
thanks
Lucas De MarchiQuoted 9 lines
3. Ping Thomas, LKML, me and probably a couple of other core people if this is the right idea or not.
4. Work on dropping the map parameter fromdma_buf_vunmap(). This is basically why we can't modify the pointers returned fromdma_buf_vmap()and has already cause a few problems withdma_buf_map_incr().Regards,
Christian.Quoted 2 lines
Lucas De Marchi
Re: [PATCH 02/19] dma-buf-map: Add helper to initialize second map
In reply to Christian KönigQuoted 18 lines · Christian König
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 9 lines · Christian König
Quoted 8 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Quoted 7 lines
Quoted 5 lines
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.humn... not sure if I was clear. There is no importer and exporter here.
Quoted 7 lines
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Uh I suggested this, also we're already using dma_buf_map all over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.
Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
Quoted 18 lines
Quoted 18 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }
fill_bar(structdma_buf_map*bla_map) { ... }
Quoted 7 lines
Quoted 7 lines
and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));
Wrt the issue at hand I think the above is perfectly fine code. The idea with dma_buf_map is really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff like container_of and all that with typechecking in the macros.
-Daniel
Quoted 10 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De Marchi
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 27 lines · Daniel Vetter
Quoted 18 lines · Christian König
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 9 lines · Christian König
Quoted 8 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Quoted 7 lines
Quoted 5 lines
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.humn... not sure if I was clear. There is no importer and exporter here.
Quoted 7 lines
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest iosys_map since it abstracts access to IO and system memory.
Quoted 27 lines
Quoted 19 lines
Quoted 19 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }
fill_bar(structdma_buf_map*bla_map) { ... }Quoted 7 lines
Quoted 7 lines
and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));
Quoted 6 lines
Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.
I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */
is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));
Lucas De Marchi
Quoted 17 lines
-Daniel
Quoted 10 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Daniel Vetter
Acked-byRe: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 90 lines · Lucas De Marchi
Quoted 27 lines · Daniel Vetter
Quoted 18 lines · Christian König
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 9 lines · Christian König
Quoted 8 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Quoted 7 lines
Quoted 5 lines
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.humn... not sure if I was clear. There is no importer and exporter here.
Quoted 7 lines
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 27 lines
Quoted 19 lines
Quoted 19 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }
fill_bar(structdma_buf_map*bla_map) { ... }Quoted 7 lines
Quoted 7 lines
and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Quoted 6 lines
Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()
Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));
Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
-Daniel
Quoted 20 lines
Lucas De Marchi
Quoted 17 lines
-Daniel
Quoted 10 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 91 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Quoted 8 lines
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is dma_buf_vunmap():
void dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);
Here we expect the original pointer as returned by dma_buf_map(), otherwise we vunmap() the wrong area!
For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Christian.
Quoted 19 lines
-Daniel
Quoted 17 lines
Lucas De Marchi
Quoted 15 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 103 lines · Christian König
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 91 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Quoted 8 lines
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():
Quoted 8 lines
void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Yeah but isn't that the same if it's just a void *?
If you pass the wrong pointer to an unmap function and not exactly what you go from the map function, then things go boom. This is like complaining that the following code wont work
u32 *stuff stuff = kmap_local(some_page); *stuff++ = 0; *stuff = 1; kunmap_locak(stuff);
It's just ... don't do that :-) Also since we pass dma_buf_map by value and not by pointer anywhere, the risk of this happening is pretty low since you tend to work on a copy. Same with void * pointers really.
Now if people start to pass around struct dma_buf_map * as pointers for anything else than out parameters, then we're screwed. But that's like passing around void ** for lolz, which is just wrong (except when it's an out parameter or actually an array of pointers ofc).
Or I really don't get your concern and you mean something else? -Daniel
Quoted 22 lines
Christian.
Quoted 19 lines
-Daniel
Quoted 17 lines
Lucas De Marchi
Quoted 15 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [Linaro-mm-sig] Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Am 27.01.22 um 12:16 schrieb Daniel Vetter:
Quoted 128 lines · Christian König
Quoted 102 lines
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 91 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct dma_buf_map map = *bla_map; dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Quoted 8 lines
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():Quoted 8 lines
void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Yeah but isn't that the same if it's just a void *?
If you pass the wrong pointer to an unmap function and not exactly what you go from the map function, then things go boom. This is like complaining that the following code wont work
u32 *stuff stuff = kmap_local(some_page); *stuff++ = 0; *stuff = 1; kunmap_locak(stuff);It's just ... don't do that :-) Also since we pass
dma_buf_mapby value and not by pointer anywhere, the risk of this happening is pretty low since you tend to work on a copy. Same with void * pointers really.
Quoted 6 lines
Now if people start to pass around struct
dma_buf_map* as pointers for anything else than out parameters, then we're screwed. But that's like passing around void ** for lolz, which is just wrong (except when it's an out parameter or actually an array of pointers ofc).Or I really don't get your concern and you mean something else?
No that's pretty much it. It's just that we hide the pointer inside a structure and it is absolutely not obvious to a driver dev that you can't do:
dma_buf_vmap(.., &map);dma_buf_map_inr(&map, x);dma_buf_vunmap(.., &map);
As bare minimum I strongly suggest that we add some WARN_ONs to the framework to check that the pointer given to dma_buf_vunmap() is at least page aligned.
Christian.
Quoted 24 lines
-Daniel
Quoted 21 lines
Christian.
Quoted 19 lines
-Daniel
Quoted 17 lines
Lucas De Marchi
Quoted 15 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Re: [Linaro-mm-sig] Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 140 lines · Christian König
Am 27.01.22 um 12:16 schrieb Daniel Vetter:
Quoted 128 lines · Christian König
Quoted 102 lines
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 91 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct dma_buf_map map = *bla_map; dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Quoted 8 lines
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():Quoted 8 lines
void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Yeah but isn't that the same if it's just a void *?
If you pass the wrong pointer to an unmap function and not exactly what you go from the map function, then things go boom. This is like complaining that the following code wont work
u32 *stuff stuff = kmap_local(some_page); *stuff++ = 0; *stuff = 1; kunmap_locak(stuff);It's just ... don't do that :-) Also since we pass
dma_buf_mapby value and not by pointer anywhere, the risk of this happening is pretty low since you tend to work on a copy. Same with void * pointers really.Quoted 6 lines
Now if people start to pass around struct
dma_buf_map* as pointers for anything else than out parameters, then we're screwed. But that's like passing around void ** for lolz, which is just wrong (except when it's an out parameter or actually an array of pointers ofc).Or I really don't get your concern and you mean something else?
No that's pretty much it. It's just that we hide the pointer inside a structure and it is absolutely not obvious to a driver dev that you can't do:
Quoted 7 lines
dma_buf_vmap(.., &map);dma_buf_map_inr(&map, x);dma_buf_vunmap(.., &map);As bare minimum I strongly suggest that we add some
WARN_ONsto the framework to check that the pointer given todma_buf_vunmap()is at least page aligned.
Yeah that might be a good idea. But then we also have to add that check to dma_buf_vmap, just in case a driver does something really funny :-) -Daniel
Quoted 28 lines
Christian.
Quoted 24 lines
-Daniel
Quoted 21 lines
Christian.
Quoted 19 lines
-Daniel
Quoted 17 lines
Lucas De Marchi
Quoted 15 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Re: [Linaro-mm-sig] Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
In reply to Christian KönigQuoted 136 lines · Christian König
Am 27.01.22 um 12:16 schrieb Daniel Vetter:
Quoted 128 lines · Christian König
Quoted 102 lines
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 91 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Quoted 8 lines
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():Quoted 8 lines
void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Yeah but isn't that the same if it's just a void *?
If you pass the wrong pointer to an unmap function and not exactly what you go from the map function, then things go boom. This is like complaining that the following code wont work
u32 *stuff stuff = kmap_local(some_page); *stuff++ = 0; *stuff = 1; kunmap_locak(stuff);It's just ... don't do that :-) Also since we pass
dma_buf_mapby value and not by pointer anywhere, the risk of this happening is pretty low since you tend to work on a copy. Same with void * pointers really.Quoted 6 lines
Now if people start to pass around struct
dma_buf_map* as pointers for anything else than out parameters, then we're screwed. But that's like passing around void ** for lolz, which is just wrong (except when it's an out parameter or actually an array of pointers ofc).Or I really don't get your concern and you mean something else?
Quoted 7 lines
No that's pretty much it. It's just that we hide the pointer inside a structure and it is absolutely not obvious to a driver dev that you can't do:
dma_buf_vmap(.., &map);dma_buf_map_inr(&map, x);dma_buf_vunmap(.., &map);As bare minimum I strongly suggest that we add some
WARN_ONsto the framework to check that the pointer given todma_buf_vunmap()is at least page aligned.
Agreed, that should cover most of the cases. I can add a patch doing that.
thanks
Lucas De Marchi
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
In reply to Christian KönigHi
Am 27.01.22 um 11:21 schrieb Christian König:
Quoted 98 lines
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 97 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }fill_bar(struct dma_buf_map *bla_map){ ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct
dma_buf_mapother_map=*bla_map;
/* poor Lucas forgettingdma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map;
...
other_map =INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct
dma_buf_mapother_map=INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>
Quoted 8 lines
Quoted 2 lines
I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!
Indeed. It's always been a problem with that API, even when it still took raw pointers.
The IMHO correct solution would distinguish between a buffer (struct dma_buf_map) and a pointer into that buffer (struct dma_buf_ptr).
I don't feel like typing that.
Best regards
Thomas
Quoted 26 lines
For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Christian.
Quoted 20 lines
-Daniel
Quoted 18 lines
Lucas De Marchi
Quoted 16 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
In reply to Christian KönigQuoted 98 lines · Christian König
Am 27.01.22 um 11:00 schrieb Daniel Vetter:
Quoted 97 lines · Lucas De Marchi
Quoted 82 lines · Daniel Vetter
Quoted 23 lines · Christian König
Quoted 14 lines
Am 27.01.22 um 08:57 schrieb Lucas De Marchi:
Quoted 13 lines · Christian König
Quoted 12 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 6 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Well what you propose here can lead to all kind of problems and is rather bad design as far as I can see.
The struct
dma_buf_mapis only to be filled in by the exporter and should not be modified in this way by the importer.Quoted 8 lines
Quoted 1 line
humn... not sure if I was clear. There is no importer and exporter here.
Yeah, and exactly that's what I'm pointing out as problem here.
You are using the inter driver framework for something internal to the driver. That is an absolutely clear NAK!
We could discuss that, but you guys are just sending around patches to do this without any consensus that this is a good idea.
Quoted 8 lines
Uh I suggested this, also we're already using
dma_buf_mapall over the place as a convenient abstraction. So imo that's all fine, it should allow drivers to simplify some code where on igpu it's in normal kernel memory and on dgpu it's behind some pci bar.Maybe we should have a better name for that struct (and maybe also a better place), but way back when we discussed that bikeshed I didn't come up with anything better really.
I suggest
iosys_mapsince it abstracts access to IO and system memory.Quoted 23 lines
Quoted 23 lines
Quoted 23 lines
There is a role delegation on filling out and reading a buffer when that buffer represents a struct layout.
struct bla {
int a;
int b;
int c;
struct foo foo;
struct bar bar;
int d;
}This implementation allows you to have:
fill_foo(struct
dma_buf_map*bla_map) { ... }
fill_bar(structdma_buf_map*bla_map) { ... }and the first thing these do is to make sure the map it's pointing to is relative to the struct it's supposed to write/read. Otherwise you're suggesting everything to be relative to struct bla, or to do the same I'm doing it, but IMO more prone to error:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
struct
dma_buf_mapmap =*bla_map;
dma_buf_map_incr(map, offsetof(...));Wrt the issue at hand I think the above is perfectly fine code. The idea with
dma_buf_mapis really that it's just a special pointer, so writing the code exactly as pointer code feels best. Unfortunately you cannot make them typesafe (because of C), so the code sometimes looks a bit ugly. Otherwise we could do stuff likecontainer_ofand all that with typechecking in the macros.I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map; /* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map; ... other_map = INITIALIZER()Quoted 5 lines
I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));Hm yeah that's a good point that this allows us to rely on the compiler to check for uninitialized variables.
Maybe include the above (with editing, but keeping the examples) in the kerneldoc to explain why/how to use this? With that the concept at least has my
Acked-by Daniel Vetter <[email protected]>
Quoted 8 lines
Quoted 2 lines
I'll leave it up to you & Christian to find a prettier color choice for the naming bikeshed.
There is one major issue remaining with this and that is
dma_buf_vunmap():void
dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);Here we expect the original pointer as returned by
dma_buf_map(), otherwise wevunmap()the wrong area!
yeah... I think the most confusing aspect here is about the name.
void dma_buf_vunmap(struct dma_buf *dmabuf, struct dma_buf_map *map);
this function is the implementation of the dma_buf, not dma_buf_map, which is another thing entirely. I think the rename will be benefitial for this to be cleared out, because then it's more obvious the shallow copy of the map is the equivalent of having
u8 *p = buffer; ... p += 10;
Etc. You can't kfree(p) and expect it to work.
Lucas De Marchi
Quoted 24 lines
For all TTM based driver this doesn't matter since we keep the vmap base separately in the BO anyway (IIRC), but we had at least one case where this made boom last year.
Christian.
Quoted 19 lines
-Daniel
Quoted 17 lines
Lucas De Marchi
Quoted 15 lines
-Daniel
Quoted 9 lines
Quoted 9 lines
IMO this construct is worse because at a point in time in the function the map was pointing to the wrong thing the function was supposed to read/write.
It's also useful when the function has double duty, updating a global part of the struct and a table inside it (see example in patch 6)
thanks
Lucas De MarchiSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.ffwll.ch%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C0654a16ea3444271d7c308d9e17bd35d%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637788744226808874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Q6soluBglaZLhLszdapaWuUVsqMq5qvJOKiJjO%2B9BTg%3D&reserved=0
Re: [PATCH 02/19] dma-buf-map: Add helper to initialize second map
In reply to Lucas De MarchiAm 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 45 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)include/linux/dma-buf-map.h +19
-0@@ -131,6 +131,35 @@ struct dma_buf_map { .is_iomem = false, \ } +/** +* DMA_BUF_MAP_INIT_OFFSET - Initializes struct dma_buf_map from another dma_buf_map +* @map_: The dma-buf mapping structure to copy from +* @offset: Offset to add to the other mapping +* +* Initializes a new dma_buf_struct based on another. This is the equivalent of doing: +* +* .. code-block: c +* +* dma_buf_map map = other_map; +* dma_buf_map_incr(&map, &offset); +* +* Example usage: +* +* .. code-block: c +* +* void foo(struct device *dev, struct dma_buf_map *base_map) +* { +* ...
include/linux/dma-buf-map.h struct dma_buf_map { · line 162
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* struct dma_buf_map = DMA_BUF_MAP_INIT_OFFSET(base_map, FIELD_OFFSET); +* ... +* } +*/ +#define DMA_BUF_MAP_INIT_OFFSET (map_, offset_) (struct dma_buf_map) \ + { \ + .vaddr = (map_)->vaddr + (offset_), \ + .is_iomem = (map_)->is_iomem, \ + } +
It's illegal to access .vaddr with raw pointer. Always use a dma_buf_memcpy_() interface. So why would you need this macro when you have dma_buf_memcpy_*() with an offset parameter?
I've also been very careful to distinguish between .vaddr and .vaddr_iomem, even in places where I wouldn't have to. This macro breaks the assumption.
Best regards
Thomas
Quoted 3 lines
include/linux/dma-buf-map.h +0
-0/** * dma_buf_map_set_vaddr - Sets a dma-buf mapping structure to an address in system memory * @map: The dma-buf mapping structure
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Quoted 51 lines · Thomas Zimmermann
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 48 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)include/linux/dma-buf-map.h +23
-0@@ -131,6 +131,35 @@ struct dma_buf_map { .is_iomem = false, \ } +/** +* DMA_BUF_MAP_INIT_OFFSET - Initializes struct dma_buf_map from another dma_buf_map +* @map_: The dma-buf mapping structure to copy from +* @offset: Offset to add to the other mapping +* +* Initializes a new dma_buf_struct based on another. This is the equivalent of doing: +* +* .. code-block: c +* +* dma_buf_map map = other_map; +* dma_buf_map_incr(&map, &offset); +* +* Example usage: +* +* .. code-block: c +* +* void foo(struct device *dev, struct dma_buf_map *base_map) +* { +* ... +* struct dma_buf_map = DMA_BUF_MAP_INIT_OFFSET(base_map, FIELD_OFFSET); +* ... +* } +*/
Quoted 8 lines
include/linux/dma-buf-map.h struct dma_buf_map { · line 162
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+#define DMA_BUF_MAP_INIT_OFFSET (map_, offset_) (struct dma_buf_map) \ + { \ + .vaddr = (map_)->vaddr + (offset_), \ + .is_iomem = (map_)->is_iomem, \ + } +It's illegal to access .vaddr with raw pointer. Always use a
dma_buf_memcpy_()interface. So why would you need this macro when you have dma_buf_memcpy_*() with an offset parameter?
I did a better job with an example in 20220127093332.wnkd2qy4tvwg5i5l@ldmartin-desk2
While doing this series I had code like this when using the API in a function to parse/update part of the struct mapped:
int bla_parse_foo(struct dma_buf_map *bla_map)
{
struct dma_buf_map foo_map = *bla_map;
...
dma_buf_map_incr(&foo_map, offsetof(struct bla, foo));
...
}Pasting the rest of the reply here:
I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
struct dma_buf_map other_map = *bla_map;
/* poor Lucas forgetting dma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
While with the construct below
other_map;
...
other_map = INITIALIZER()I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct dma_buf_map other_map = INITIALIZER(bla_map, offsetof(..));
This is useful when you have several small functions in charge of updating/reading inner struct members.
Quoted 2 lines
I've also been very careful to distinguish between .vaddr and .vaddr_iomem, even in places where I wouldn't have to. This macro breaks the assumption.
That's one reason I think if we have this macro, it should be in the dma_buf_map.h header (or whatever we rename these APIs to). It's the only place where we can safely add code that relies on the implementation of the "private" fields in struct dma_buf_map.
Lucas De Marchi
Quoted 15 lines
Best regards
ThomasQuoted 3 lines
include/linux/dma-buf-map.h +0
-0/** * dma_buf_map_set_vaddr - Sets a dma-buf mapping structure to an address in system memory * @map: The dma-buf mapping structure Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Hi
Am 27.01.22 um 16:59 schrieb Lucas De Marchi:
Quoted 87 lines · Thomas Zimmermann
Quoted 55 lines
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 52 lines
When
dma_buf_mapstruct is passed around, it's useful to be able to initialize a second map that takes care of reading/writing to an offset of the original map.Add a helper that copies the struct and add the offset to the proper address.
Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>---
include/linux/dma-buf-map.h | 29 +++++++++++++++++++++++++++++1 file changed, 29 insertions(+)include/linux/dma-buf-map.h +2
-0@@ -131,6 +131,35 @@ struct dma_buf_map { .is_iomem = false, \ } +/** +* DMA_BUF_MAP_INIT_OFFSET - Initializes struct dma_buf_map from another
dma_buf_map
+ * @map_: The dma-buf mapping structure to copy from
+ * @offset: Offset to add to the other mapping
+ *
+ * Initializes a newdma_buf_structbased on another. This is the equivalent of doing:
+ *
+ * .. code-block: c
+ *
+ *dma_buf_mapmap =other_map;
+ *dma_buf_map_incr(&map, &offset);
+ *
+ * Example usage:
+ *
+ * .. code-block: c
+ *
+ * voidfoo(struct device *dev, struct dma_buf_map *base_map)
+ * {
+ * ...
+ * structdma_buf_map=DMA_BUF_MAP_INIT_OFFSET(base_map, FIELD_OFFSET);
+ * ...
+ * }
+ */
+#defineDMA_BUF_MAP_INIT_OFFSET(map_, offset_)(structQuoted 8 lines
Quoted 6 lines
dma_buf_map) \
+ { \
+ .vaddr = (map_)->vaddr + (offset_), \
+ .is_iomem = (map_)->is_iomem, \
+ }
+It's illegal to access .vaddr with raw pointer. Always use a
dma_buf_memcpy_()interface. So why would you need this macro when you have dma_buf_memcpy_*() with an offset parameter?I did a better job with an example in 20220127093332.wnkd2qy4tvwg5i5l@ldmartin-desk2
While doing this series I had code like this when using the API in a function to parse/update part of the struct mapped:
int
bla_parse_foo(struct dma_buf_map *bla_map){
structdma_buf_mapfoo_map=*bla_map;
...
dma_buf_map_incr(&foo_map, offsetof(struct bla, foo));...
}Pasting the rest of the reply here:
I had exactly this code above, but after writting quite a few patches using it, particularly with functions that have to write to 2 maps (see patch 6 for example), it felt much better to have something to initialize correctly from the start
Quoted 5 lines
struct
dma_buf_mapother_map=*bla_map;
/* poor Lucas forgettingdma_buf_map_incr(map, offsetof(...)); */is error prone and hard to debug since you will be reading/writting from/to another location rather than exploding
Indeed. We have soem very specific use cases in graphics code, when dma_buf_map_incr() makes sense. But it's really bad for others. I guess that the docs should talk about this.
Quoted 11 lines
While with the construct below
other_map;
...
other_map=INITIALIZER()I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
Quoted 5 lines
struct
dma_buf_mapother_map=INITIALIZER(bla_map, offsetof(..));This is useful when you have several small functions in charge of updating/reading inner struct members.
You won't need an extra variable or the initializer macro if you add an offset parameter to dma_buf_memcpy_{from,to}. Simple pass offsetof(..) to that parameter and it will do the right thing.
It avoids the problems of the current macro and is even more flexible. On top of that, you can build whatever convenience macros you need for i915.
Best regards
Thomas
Quoted 29 lines
Quoted 3 lines
I've also been very careful to distinguish between .vaddr and .vaddr_iomem, even in places where I wouldn't have to. This macro breaks the assumption.
That's one reason I think if we have this macro, it should be in the
dma_buf_map.hheader (or whatever we rename these APIs to). It's the only place where we can safely add code that relies on the implementation of the "private" fields in structdma_buf_map.Lucas De Marchi
Quoted 15 lines
Best regards
ThomasQuoted 3 lines
/**
*dma_buf_map_set_vaddr- Sets a dma-buf mapping structure to an address in system memory
* @map: The dma-buf mapping structureSignature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 02/19] dma-buf-map: Add helper to initialize second map
Hi
Am 28.01.22 um 09:15 schrieb Thomas Zimmermann:
...
Quoted 15 lines
Quoted 15 lines
While with the construct below
other_map;
...
other_map=INITIALIZER()I can rely on the compiler complaining about uninitialized var. And in most of the cases I can just have this single line in the beggining of the function when the offset is constant:
struct
dma_buf_mapother_map=INITIALIZER(bla_map, offsetof(..));
Quoted 6 lines
Quoted 2 lines
This is useful when you have several small functions in charge of updating/reading inner struct members.
You won't need an extra variable or the initializer macro if you add an offset parameter to dma_buf_memcpy_{from,to}. Simple pass offsetof(..) to that parameter and it will do the right thing.
It avoids the problems of the current macro and is even more flexible. On top of that, you can build whatever convenience macros you need for i915.
And maybe put all changes to the dma_buf_map interface into a single patch. It makes it easier to review and discuss.
Best regards
Thomas
Quoted 34 lines
Best regards
ThomasQuoted 29 lines
Quoted 3 lines
I've also been very careful to distinguish between .vaddr and .vaddr_iomem, even in places where I wouldn't have to. This macro breaks the assumption.
That's one reason I think if we have this macro, it should be in the
dma_buf_map.hheader (or whatever we rename these APIs to). It's the only place where we can safely add code that relies on the implementation of the "private" fields in structdma_buf_map.Lucas De Marchi
Quoted 15 lines
Best regards
ThomasQuoted 3 lines
/**
*dma_buf_map_set_vaddr- Sets a dma-buf mapping structure to an address in system memory
* @map: The dma-buf mapping structureSignature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
PATCH 3/19 drm/i915/gt: Add helper for shmem copy to dma_buf_map
In reply to Lucas De MarchiAdd a variant of shmem_read() that takes a dma_buf_map pointer rather than a plain pointer as argument. It's mostly a copy __shmem_rw() but adapting the api and removing the write support since there's currently only need to use dma_buf_map as destination.
Reworking __shmem_rw() to share the implementation was tempting, but finding a good balance between reuse and clarity pushed towards a little code duplication. Since the function is small, just add the similar function with a copy/paste/adapt approach.
--- drivers/gpu/drm/i915/gt/shmem_utils.c | 32 +++++++++++++++++++++++++++ drivers/gpu/drm/i915/gt/shmem_utils.h | 3 +++ 2 files changed, 35 insertions(+)
drivers/gpu/drm/i915/gt/shmem_utils.c +32 -0
@@ -3,6 +3,7 @@* Copyright © 2020 Intel Corporation */ +#include <linux/dma-buf-map.h> #include <linux/mm.h> #include <linux/pagemap.h> #include <linux/shmem_fs.h>
@@ -123,6 +124,37 @@ static int __shmem_rw(struct file *file, loff_t off,return 0 ; } +int shmem_read_to_dma_buf_map (struct file *file,loff_t off, +struct dma_buf_map *map,size_t len) +{ +struct dma_buf_map map_iter = *map; +unsigned long pfn; + +for (pfn = off >>PAGE_SHIFT ; len; pfn++) { +unsigned int this = +min_t (size_t,PAGE_SIZE -offset_in_page (off), len); +struct page *page; +void *vaddr; + + page =shmem_read_mapping_page_gfp (file->f_mapping, pfn, +GFP_KERNEL ); +if (IS_ERR (page)) +return PTR_ERR (page); + + vaddr =kmap (page); +dma_buf_map_memcpy_to (&map_iter, vaddr +offset_in_page (off), this); +mark_page_accessed (page); +kunmap (page); +put_page (page); + + len -= this; +dma_buf_map_incr (&map_iter, this); + off =0 ; + } + +return 0 ; +} +int shmem_read (struct file *file,loff_t off,void *dst,size_t len) {return __shmem_rw (file, off, dst, len, false);
drivers/gpu/drm/i915/gt/shmem_utils.h +3 -0
@@ -8,6 +8,7 @@#include <linux/types.h> +struct dma_buf_map ;struct drm_i915_gem_object ;struct file ;
@@ -17,6 +18,8 @@ struct file *shmem_create_from_object(struct drm_i915_gem_object *obj);void *shmem_pin_map (struct file *file);void shmem_unpin_map (struct file *file,void *ptr); +int shmem_read_to_dma_buf_map (struct file *file,loff_t off, +struct dma_buf_map *map,size_t len);int shmem_read (struct file *file,loff_t off,void *dst,size_t len);int shmem_write (struct file *file,loff_t off,void *src,size_t len);
Signature · 1 line
2.35.0
PATCH 4/19 drm/i915/guc: Keep dma_buf_map of ads_blob around
In reply to Lucas De MarchiConvert intel_guc_ads_create() and initialization to use dma_buf_map rather than plain pointer and save it in the guc struct. This will help with additional updates to the ads_blob after the creation/initialization by abstracting the IO vs system memory.
--- drivers/gpu/drm/i915/gt/uc/intel_guc.h | 4 +++- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 6 ++++++ 2 files changed, 9 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/uc/intel_guc.h +3 -1
@@ -6,8 +6,9 @@#ifndef _INTEL_GUC_H_#define _INTEL_GUC_H_ -#include <linux/xarray.h> #include <linux/delay.h> +#include <linux/dma-buf.h> +#include <linux/xarray.h> #include "intel_uncore.h" #include "intel_guc_fw.h"
@@ -148,6 +149,7 @@ struct intel_guc {struct i915_vma *ads_vma;/** @ads_blob: contents of the GuC ADS */ struct __guc_ads_blob *ads_blob; +struct dma_buf_map ads_map;/** @ads_regset_size: size of the save/restore regsets in the ADS */ u32 ads_regset_size;/** @ads_golden_ctxt_size: size of the golden contexts in the ADS */
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +6 -0
@@ -623,6 +623,11 @@ int intel_guc_ads_create(struct intel_guc *guc)if (ret)return ret; +if (i915_gem_object_is_lmem (guc->ads_vma->obj)) +dma_buf_map_set_vaddr_iomem (&guc->ads_map, (void __iomem *)guc->ads_blob); +else +dma_buf_map_set_vaddr (&guc->ads_map, guc->ads_blob); +__guc_ads_init (guc);return 0 ;
@@ -644,6 +649,7 @@ void intel_guc_ads_destroy(struct intel_guc *guc) {i915_vma_unpin_and_release (&guc->ads_vma,I915_VMA_RELEASE_MAP ); guc->ads_blob =NULL ; +dma_buf_map_clear (&guc->ads_map); }static void guc_ads_private_data_reset (struct intel_guc *guc)
Signature · 1 line
2.35.0
PATCH 5/19 drm/i915/guc: Add read/write helpers for ADS blob
In reply to Lucas De MarchiAdd helpers on top of dma_buf_map_read_field() / dma_buf_map_write_field() functions so they always use the right arguments and make code easier to read.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +8 -0
@@ -59,6 +59,14 @@ struct __guc_ads_blob {struct guc_mmio_reg regset[0 ]; } __packed; +#define ads_blob_read (guc_, field_) \ + dma_buf_map_read_field(&(guc_)->ads_map, struct __guc_ads_blob, \ + field_) + +#define ads_blob_write (guc_, field_, val_) \ + dma_buf_map_write_field(&(guc_)->ads_map, struct __guc_ads_blob,\ + field_, val_) +static u32 guc_ads_regset_size (struct intel_guc *guc) {GEM_BUG_ON (!guc->ads_regset_size);
Signature · 1 line
2.35.0
PATCH 6/19 drm/i915/guc: Convert golden context init to dma_buf_map
In reply to Lucas De MarchiNow the map is saved during creation, so use it to initialize the golden context, reading from shmem and writing to either system or IO memory.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 25 +++++++++++----------- 1 file changed, 13 insertions(+), 12 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +13 -12
@@ -473,18 +473,17 @@ static struct intel_engine_cs *find_engine_state(struct intel_gt *gt, u8 engine_static void guc_init_golden_context (struct intel_guc *guc) { -struct __guc_ads_blob *blob = guc->ads_blob;struct intel_engine_cs *engine;struct intel_gt *gt =guc_to_gt (guc); +struct dma_buf_map golden_context_map;u32 addr_ggtt, offset;u32 total_size =0 , alloc_size, real_size;u8 engine_class, guc_class; -u8 *ptr;if (!intel_uc_uses_guc_submission (>->uc))return ; -GEM_BUG_ON (!blob); +GEM_BUG_ON (dma_buf_map_is_null (&guc->ads_map));/* * Go back and fill in the golden context data now that it is
@@ -492,15 +491,15 @@ static void guc_init_golden_context(struct intel_guc *guc)*/ offset =guc_ads_golden_ctxt_offset (guc); addr_ggtt =intel_guc_ggtt_offset (guc, guc->ads_vma) + offset; - ptr = ((u8 *)blob) + offset; + + golden_context_map =DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, offset);for (engine_class =0 ; engine_class <=MAX_ENGINE_CLASS ; ++engine_class) {if (engine_class ==OTHER_CLASS )continue ; guc_class =engine_class_to_guc_class (engine_class); - -if (!blob->system_info.engine_enabled_masks[guc_class]) +if (!ads_blob_read (guc, system_info.engine_enabled_masks[guc_class]))continue ; real_size =intel_engine_context_size (gt, engine_class);
@@ -511,18 +510,20 @@ static void guc_init_golden_context(struct intel_guc *guc)if (!engine) {drm_err (>->i915->drm,"No engine state recorded for class %d!\n" , engine_class); - blob->ads.eng_state_size[guc_class] =0 ; - blob->ads.golden_context_lrca[guc_class] =0 ; +ads_blob_write (guc, ads.eng_state_size[guc_class],0 ); +ads_blob_write (guc, ads.golden_context_lrca[guc_class],0 );continue ; } -GEM_BUG_ON (blob->ads.eng_state_size[guc_class] != +GEM_BUG_ON (ads_blob_read (guc, ads.eng_state_size[guc_class]) != real_size -LRC_SKIP_SIZE ); -GEM_BUG_ON (blob->ads.golden_context_lrca[guc_class] != addr_ggtt); +GEM_BUG_ON (ads_blob_read (guc, ads.golden_context_lrca[guc_class]) != addr_ggtt); + addr_ggtt += alloc_size; -shmem_read (engine->default_state,0 , ptr, real_size); - ptr += alloc_size; +shmem_read_to_dma_buf_map (engine->default_state,0 , + &golden_context_map, real_size); +dma_buf_map_incr (&golden_context_map, alloc_size); }GEM_BUG_ON (guc->ads_golden_ctxt_size != total_size);
Signature · 1 line
2.35.0
PATCH 7/19 drm/i915/guc: Convert policies update to dma_buf_map
In reply to Lucas De MarchiUse dma_buf_map to write the policies update so access to IO and system memory is abstracted away.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 41 ++++++++++++---------- 1 file changed, 23 insertions(+), 18 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +23 -18
@@ -130,33 +130,37 @@ static u32 guc_ads_blob_size(struct intel_guc *guc)guc_ads_private_data_size (guc); } -static void guc_policies_init (struct intel_guc *guc,struct guc_policies *policies) +static void guc_policies_init (struct intel_guc *guc) {struct intel_gt *gt =guc_to_gt (guc);struct drm_i915_private *i915 = gt->i915; +u32 global_flags =0 ; - policies->dpc_promote_time =GLOBAL_POLICY_DEFAULT_DPC_PROMOTE_TIME_US ; - policies->max_num_work_items =GLOBAL_POLICY_MAX_NUM_WI ; +ads_blob_write (guc, policies.dpc_promote_time, +GLOBAL_POLICY_DEFAULT_DPC_PROMOTE_TIME_US ); +ads_blob_write (guc, policies.max_num_work_items, +GLOBAL_POLICY_MAX_NUM_WI ); - policies->global_flags =0 ;if (i915->params.reset <2 ) - policies->global_flags |=GLOBAL_POLICY_DISABLE_ENGINE_RESET ; + global_flags |=GLOBAL_POLICY_DISABLE_ENGINE_RESET ; - policies->is_valid =1 ; +ads_blob_write (guc, policies.global_flags, global_flags); +ads_blob_write (guc, policies.is_valid,1 ); }void intel_guc_ads_print_policy_info (struct intel_guc *guc,struct drm_printer *dp) { -struct __guc_ads_blob *blob = guc->ads_blob; - -if (unlikely (!blob)) +if (unlikely (dma_buf_map_is_null (&guc->ads_map)))return ;drm_printf (dp,"Global scheduling policies:\n" ); -drm_printf (dp," DPC promote time = %u\n" , blob->policies.dpc_promote_time); -drm_printf (dp," Max num work items = %u\n" , blob->policies.max_num_work_items); -drm_printf (dp," Flags = %u\n" , blob->policies.global_flags); +drm_printf (dp," DPC promote time = %u\n" , +ads_blob_read (guc, policies.dpc_promote_time)); +drm_printf (dp," Max num work items = %u\n" , +ads_blob_read (guc, policies.max_num_work_items)); +drm_printf (dp," Flags = %u\n" , +ads_blob_read (guc, policies.global_flags)); }static int guc_action_policies_update (struct intel_guc *guc,u32 policy_offset)
@@ -171,23 +175,24 @@ static int guc_action_policies_update(struct intel_guc *guc, u32 policy_offset)int intel_guc_global_policies_update (struct intel_guc *guc) { -struct __guc_ads_blob *blob = guc->ads_blob;struct intel_gt *gt =guc_to_gt (guc); +u32 scheduler_policies;intel_wakeref_t wakeref;int ret; -if (!blob) +if (dma_buf_map_is_null (&guc->ads_map))return -EOPNOTSUPP ; -GEM_BUG_ON (!blob->ads.scheduler_policies); + scheduler_policies =ads_blob_read (guc, ads.scheduler_policies); +GEM_BUG_ON (!scheduler_policies); -guc_policies_init (guc, &blob->policies); +guc_policies_init (guc);if (!intel_guc_is_ready (guc))return 0 ;with_intel_runtime_pm (>->i915->runtime_pm, wakeref) - ret = guc_action_policies_update(guc, blob->ads.scheduler_policies); + ret = guc_action_policies_update(guc, scheduler_policies);return ret; }
@@ -557,7 +562,7 @@ static void __guc_ads_init(struct intel_guc *guc)u32 base;/* GuC scheduling policies */ -guc_policies_init (guc, &blob->policies); +guc_policies_init (guc);/* System info */ fill_engine_enable_masks (gt, &blob->system_info);
Signature · 1 line
2.35.0
PATCH 8/19 drm/i915/guc: Convert engine record to dma_buf_map
In reply to Lucas De MarchiUse dma_buf_map to read fields from the dma_blob so access to IO and system memory is abstracted away.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 14 ++++++-------- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.h | 3 ++- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 11 +++++++---- 3 files changed, 15 insertions(+), 13 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +6 -8
@@ -698,18 +698,16 @@ void intel_guc_ads_reset(struct intel_guc *guc)u32 intel_guc_engine_usage_offset (struct intel_guc *guc) { -struct __guc_ads_blob *blob = guc->ads_blob; -u32 base =intel_guc_ggtt_offset (guc, guc->ads_vma); -u32 offset = base +ptr_offset (blob, engine_usage); - -return offset; +return intel_guc_ggtt_offset (guc, guc->ads_vma) + + offsetof(struct __guc_ads_blob , engine_usage); } -struct guc_engine_usage_record *intel_guc_engine_usage (struct intel_engine_cs *engine) +struct dma_buf_map intel_guc_engine_usage_record_map (struct intel_engine_cs *engine) {struct intel_guc *guc = &engine->gt->uc.guc; -struct __guc_ads_blob *blob = guc->ads_blob;u8 guc_class =engine_class_to_guc_class (engine->class); +size_t offset = offsetof(struct __guc_ads_blob , + engine_usage.engines[guc_class][ilog2(engine->logical_mask)]); -return &blob->engine_usage.engines[guc_class][ilog2 (engine->logical_mask)]; +return DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, offset); }
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.h +2 -1
@@ -7,6 +7,7 @@#define _INTEL_GUC_ADS_H_#include <linux/types.h> +#include <linux/dma-buf-map.h> struct intel_guc ;struct drm_printer ;
@@ -18,7 +19,7 @@ void intel_guc_ads_init_late(struct intel_guc *guc);void intel_guc_ads_reset (struct intel_guc *guc);void intel_guc_ads_print_policy_info (struct intel_guc *guc,struct drm_printer *p); -struct guc_engine_usage_record *intel_guc_engine_usage (struct intel_engine_cs *engine); +struct dma_buf_map intel_guc_engine_usage_record_map (struct intel_engine_cs *engine);u32 intel_guc_engine_usage_offset (struct intel_guc *guc);#endif
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +7 -4
@@ -1125,14 +1125,17 @@ __extend_last_switch(struct intel_guc *guc, u64 *prev_start, u32 new_start) *prev_start = ((u64 )gt_stamp_hi <<32 ) | new_start; } +#define record_read (map_, field_) \ + dma_buf_map_read_field(map_, struct guc_engine_usage_record, field_) +static void guc_update_engine_gt_clks (struct intel_engine_cs *engine) { -struct guc_engine_usage_record *rec =intel_guc_engine_usage (engine); +struct dma_buf_map rec_map =intel_guc_engine_usage_record_map (engine);struct intel_engine_guc_stats *stats = &engine->stats.guc;struct intel_guc *guc = &engine->gt->uc.guc; -u32 last_switch = rec->last_switch_in_stamp; -u32 ctx_id = rec->current_context_index; -u32 total = rec->total_runtime; +u32 last_switch =record_read (&rec_map, last_switch_in_stamp); +u32 ctx_id =record_read (&rec_map, current_context_index); +u32 total =record_read (&rec_map, total_runtime);lockdep_assert_held (&guc->timestamp.lock);
Signature · 1 line
2.35.0
PATCH 9/19 dma-buf-map: Add wrapper over memset
In reply to Lucas De MarchiJust like memcpy_toio(), there is also need to write a direct value to a memory block. Add dma_buf_map_memset() to abstract memset() vs memset_io()
--- include/linux/dma-buf-map.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
include/linux/dma-buf-map.h +17 -0
@@ -317,6 +317,23 @@ static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *srmemcpy (dst->vaddr, src, len); } +/** +* dma_buf_map_memset - Memset into dma-buf mapping +* @dst: The dma-buf mapping structure +* @value: The value to set +* @len: The number of bytes to set in dst +* +* Set value in dma-buf mapping. Depending on the buffer's location, the helper +* picks the correct method of accessing the memory. +*/ +static inline void dma_buf_map_memset (struct dma_buf_map *dst,int value,size_t len) +{ +if (dst->is_iomem) +memset_io (dst->vaddr_iomem, value, len); +else +memset (dst->vaddr, value, len); +} +/** * dma_buf_map_incr - Increments the address stored in a dma-buf mapping * @map: The dma-buf mapping structure
Signature · 1 line
2.35.0
Re: [PATCH 09/19] dma-buf-map: Add wrapper over memset
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 30 lines
Just like
memcpy_toio(), there is also need to write a direct value to a memory block. Adddma_buf_map_memset()to abstractmemset()vsmemset_io()Cc Matt Roper <[email protected]>Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)include/linux/dma-buf-map.h +7
-0@@ -317,6 +317,23 @@ static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *srmemcpy (dst->vaddr, src, len); } +/** +* dma_buf_map_memset - Memset into dma-buf mapping +* @dst: The dma-buf mapping structure +* @value: The value to set +* @len: The number of bytes to set in dst +* +* Set value in dma-buf mapping. Depending on the buffer's location, the helper
include/linux/dma-buf-map.h static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *sr · line 336
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* picks the correct method of accessing the memory. +*/ +static inline void dma_buf_map_memset (struct dma_buf_map *dst,int value,size_t len) +{ +if (dst->is_iomem) +memset_io (dst->vaddr_iomem, value, len); +else +memset (dst->vaddr, value, len); +} +
Yeah, that's certainly a valid use case. But maybe directly add a dma_buf_map_memset_with_offset() variant as well when that helps to avoid patch #2.
Regards,
Christian.
Quoted 3 lines
include/linux/dma-buf-map.h +0
-0/** * dma_buf_map_incr - Increments the address stored in a dma-buf mapping * @map: The dma-buf mapping structure
Re: [PATCH 09/19] dma-buf-map: Add wrapper over memset
In reply to Lucas De MarchiHi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 29 lines
Just like
memcpy_toio(), there is also need to write a direct value to a memory block. Adddma_buf_map_memset()to abstractmemset()vsmemset_io()Cc Matt Roper <[email protected]>Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)include/linux/dma-buf-map.h +6
-0@@ -317,6 +317,23 @@ static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *srmemcpy (dst->vaddr, src, len); } +/** +* dma_buf_map_memset - Memset into dma-buf mapping +* @dst: The dma-buf mapping structure +* @value: The value to set +* @len: The number of bytes to set in dst +*
include/linux/dma-buf-map.h static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *sr · line 335
Quoted 10 lines
include/linux/dma-buf-map.h +10
-0+* Set value in dma-buf mapping. Depending on the buffer's location, the helper +* picks the correct method of accessing the memory. +*/ +static inline void dma_buf_map_memset (struct dma_buf_map *dst,int value,size_t len) +{ +if (dst->is_iomem) +memset_io (dst->vaddr_iomem, value, len); +else +memset (dst->vaddr, value, len); +}
Maybe add an offset parameter here.
Best regards
Thomas
Quoted 4 lines
include/linux/dma-buf-map.h +1
-0+/** * dma_buf_map_incr - Increments the address stored in a dma-buf mapping * @map: The dma-buf mapping structure
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 09/19] dma-buf-map: Add wrapper over memset
Quoted 35 lines · Thomas Zimmermann
Hi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 32 lines
Just like
memcpy_toio(), there is also need to write a direct value to a memory block. Adddma_buf_map_memset()to abstractmemset()vsmemset_io()Cc Matt Roper <[email protected]>Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- include/linux/dma-buf-map.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)include/linux/dma-buf-map.h +10
-0@@ -317,6 +317,23 @@ static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *srmemcpy (dst->vaddr, src, len); } +/** +* dma_buf_map_memset - Memset into dma-buf mapping +* @dst: The dma-buf mapping structure +* @value: The value to set +* @len: The number of bytes to set in dst +* +* Set value in dma-buf mapping. Depending on the buffer's location, the helper +* picks the correct method of accessing the memory. +*/ +static inline void dma_buf_map_memset (struct dma_buf_map *dst,int value,size_t len)
Quoted 8 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *sr · line 335
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+{ +if (dst->is_iomem) +memset_io (dst->vaddr_iomem, value, len); +else +memset (dst->vaddr, value, len); +}Maybe add an offset parameter here.
yep, on v2 I will have 2 APIs, one with and one without offset.
thanks
Lucas De Marchi
Quoted 16 lines
Best regards
ThomasQuoted 4 lines
include/linux/dma-buf-map.h +1
-0+/** * dma_buf_map_incr - Increments the address stored in a dma-buf mapping * @map: The dma-buf mapping structure Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Re: [Intel-gfx] [PATCH 09/19] dma-buf-map: Add wrapper over memset
Am 27.01.22 um 16:38 schrieb Lucas De Marchi:
Quoted 48 lines · Thomas Zimmermann
Quoted 38 lines
Hi
Am 26.01.22 um 21:36 schrieb Lucas De Marchi:
Quoted 35 lines
Just like
memcpy_toio(), there is also need to write a direct value to a memory block. Adddma_buf_map_memset()to abstractmemset()vsmemset_io()Cc Matt Roper <[email protected]>Cc Sumit Semwal <[email protected]>Cc Christian König <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>---
include/linux/dma-buf-map.h | 17 +++++++++++++++++1 file changed, 17 insertions(+)include/linux/dma-buf-map.h +0
-0@@ -317,6 +317,23 @@ static inline void dma_buf_map_memcpy_to(struct
dma_buf_map*dst, const void *sr
memcpy(dst->vaddr, src, len);
}
+/**
+ *dma_buf_map_memset- Memset into dma-buf mapping
+ * @dst: The dma-buf mapping structure
+ * @value: The value to set
+ * @len: The number of bytes to set in dst
+ *
+ * Set value in dma-buf mapping. Depending on the buffer's location, the helper
+ * picks the correct method of accessing the memory.
+ */
+static inline voiddma_buf_map_memset(struct dma_buf_map *dst, int value, size_t len)Quoted 8 lines
include/linux/dma-buf-map.h static inline void dma_buf_map_memcpy_to(struct dma_buf_map *dst, const void *sr · line 335
Quoted 6 lines
include/linux/dma-buf-map.h +6
-0+{ + if (dst->is_iomem) + memset_io(dst->vaddr_iomem, value, len); + else + memset(dst->vaddr, value, len); +}Maybe add an offset parameter here.
Quoted 1 line
yep, on v2 I will have 2 APIs, one with and one without offset.
Please, no. Just add the parameter here and pass 0 if yo don't need it.
Best regards
Thomas
Quoted 23 lines
thanks
Lucas De MarchiQuoted 16 lines
Best regards
ThomasQuoted 4 lines
+
/**
*dma_buf_map_incr- Increments the address stored in a dma-buf mapping
* @map: The dma-buf mapping structureSignature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
Signature · 6 lines
Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev
PATCH 10/19 drm/i915/guc: Convert guc_ads_private_data_reset to dma_buf_map
In reply to Lucas De MarchiUse dma_buf_map_memset() to zero the private data as ADS may be either on system or IO memory.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +3 -2
@@ -668,14 +668,15 @@ void intel_guc_ads_destroy(struct intel_guc *guc)static void guc_ads_private_data_reset (struct intel_guc *guc) { +struct dma_buf_map map = +DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map,guc_ads_private_data_offset (guc));u32 size; size =guc_ads_private_data_size (guc);if (!size)return ; -memset ((void *)guc->ads_blob +guc_ads_private_data_offset (guc),0 , - size); +dma_buf_map_memset (&map,0 , size); }/**
Signature · 1 line
2.35.0
PATCH 11/19 drm/i915/guc: Convert golden context prep to dma_buf_map
In reply to Lucas De MarchiUse the saved ads_map to prepare the golden context. One difference from the init context is that this function can be called before there is a gem object (and thus the guc->ads_map) to calculare the size of the golden context that should be allocated for that object.
So in this case the function needs to be prepared for not having the system_info with enabled engines filled out. To accomplish that an info_map is prepared on the side to point either to the gem object or the local variable on the stack. This allows making fill_engine_enable_masks() operate always with a dma_buf_map argument.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 52 +++++++++++++--------- 1 file changed, 32 insertions(+), 20 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +32 -20
@@ -67,6 +67,12 @@ struct __guc_ads_blob { dma_buf_map_write_field(&(guc_)->ads_map, struct __guc_ads_blob,\ field_, val_) +#define info_map_write (map_, field_, val_) \ + dma_buf_map_write_field(map_, struct guc_gt_system_info, field_, val_) + +#define info_map_read (map_, field_) \ + dma_buf_map_read_field(map_, struct guc_gt_system_info, field_) +static u32 guc_ads_regset_size (struct intel_guc *guc) {GEM_BUG_ON (!guc->ads_regset_size);
@@ -378,24 +384,24 @@ static void guc_mmio_reg_state_init(struct intel_guc *guc, }static void fill_engine_enable_masks (struct intel_gt *gt, -struct guc_gt_system_info *info) +struct dma_buf_map *info_map) { - info->engine_enabled_masks[GUC_RENDER_CLASS ] =1 ; - info->engine_enabled_masks[GUC_BLITTER_CLASS ] =1 ; - info->engine_enabled_masks[GUC_VIDEO_CLASS ] =VDBOX_MASK (gt); - info->engine_enabled_masks[GUC_VIDEOENHANCE_CLASS ] =VEBOX_MASK (gt); +info_map_write (info_map, engine_enabled_masks[GUC_RENDER_CLASS ],1 ); +info_map_write (info_map, engine_enabled_masks[GUC_BLITTER_CLASS ],1 ); +info_map_write (info_map, engine_enabled_masks[GUC_VIDEO_CLASS ],VDBOX_MASK (gt)); +info_map_write (info_map, engine_enabled_masks[GUC_VIDEOENHANCE_CLASS ],VEBOX_MASK (gt)); }#define LR_HW_CONTEXT_SIZE (80 * sizeof(u32))#define LRC_SKIP_SIZE (LRC_PPHWSP_SZ * PAGE_SIZE + LR_HW_CONTEXT_SIZE) -static int guc_prep_golden_context (struct intel_guc *guc, -struct __guc_ads_blob *blob) +static int guc_prep_golden_context (struct intel_guc *guc) {struct intel_gt *gt =guc_to_gt (guc);u32 addr_ggtt, offset;u32 total_size =0 , alloc_size, real_size;u8 engine_class, guc_class; -struct guc_gt_system_info *info, local_info; +struct guc_gt_system_info local_info; +struct dma_buf_map info_map;/* * Reserve the memory for the golden contexts and point GuC at it but
@@ -409,14 +415,15 @@ static int guc_prep_golden_context(struct intel_guc *guc,* GuC will also validate that the LRC base + size fall within the * allowed GGTT range. */ -if (blob) { +if (!dma_buf_map_is_null (&guc->ads_map)) { offset =guc_ads_golden_ctxt_offset (guc); addr_ggtt =intel_guc_ggtt_offset (guc, guc->ads_vma) + offset; - info = &blob->system_info; + info_map =DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, + offsetof(struct __guc_ads_blob , system_info)); }else {memset (&local_info,0 ,sizeof (local_info)); - info = &local_info; -fill_engine_enable_masks (gt, info); +dma_buf_map_set_vaddr (&info_map, &local_info); +fill_engine_enable_masks (gt, &info_map); }for (engine_class =0 ; engine_class <=MAX_ENGINE_CLASS ; ++engine_class) {
@@ -425,14 +432,14 @@ static int guc_prep_golden_context(struct intel_guc *guc, guc_class =engine_class_to_guc_class (engine_class); -if (!info->engine_enabled_masks[guc_class]) +if (!info_map_read (&info_map, engine_enabled_masks[guc_class]))continue ; real_size =intel_engine_context_size (gt, engine_class); alloc_size =PAGE_ALIGN (real_size); total_size += alloc_size; -if (!blob) +if (dma_buf_map_is_null (&guc->ads_map))continue ;/*
@@ -446,12 +453,15 @@ static int guc_prep_golden_context(struct intel_guc *guc,* what comes before it in the context image (which is identical * on all engines). */ - blob->ads.eng_state_size[guc_class] = real_size -LRC_SKIP_SIZE ; - blob->ads.golden_context_lrca[guc_class] = addr_ggtt; +ads_blob_write (guc, ads.eng_state_size[guc_class], + real_size -LRC_SKIP_SIZE ); +ads_blob_write (guc, ads.golden_context_lrca[guc_class], + addr_ggtt); + addr_ggtt += alloc_size; } -if (!blob) +if (dma_buf_map_is_null (&guc->ads_map))return total_size;GEM_BUG_ON (guc->ads_golden_ctxt_size != total_size);
@@ -559,13 +569,15 @@ static void __guc_ads_init(struct intel_guc *guc)struct intel_gt *gt =guc_to_gt (guc);struct drm_i915_private *i915 = gt->i915;struct __guc_ads_blob *blob = guc->ads_blob; +struct dma_buf_map info_map =DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, + offsetof(struct __guc_ads_blob , system_info));u32 base;/* GuC scheduling policies */ guc_policies_init (guc);/* System info */ -fill_engine_enable_masks (gt, &blob->system_info); +fill_engine_enable_masks (gt, &info_map); blob->system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_SLICE_ENABLED ] =hweight8 (gt->info.sseu.slice_mask);
@@ -581,7 +593,7 @@ static void __guc_ads_init(struct intel_guc *guc) }/* Golden contexts for re-initialising after a watchdog reset */ -guc_prep_golden_context (guc, blob); +guc_prep_golden_context (guc);guc_mapping_table_init (guc_to_gt (guc), &blob->system_info);
@@ -624,7 +636,7 @@ int intel_guc_ads_create(struct intel_guc *guc) guc->ads_regset_size = ret;/* Likewise the golden contexts: */ - ret =guc_prep_golden_context (guc,NULL ); + ret =guc_prep_golden_context (guc);if (ret <0 )return ret; guc->ads_golden_ctxt_size = ret;
Signature · 1 line
2.35.0
PATCH 12/19 drm/i915/guc: Replace check for golden context size
In reply to Lucas De MarchiIn the other places in this function, guc->ads_map is being protected from access when it's not yet set. However the last check is actually about guc->ads_golden_ctxt_size been set before. These checks should always match as the size is initialized on the first call to guc_prep_golden_context(), but it's clearer if we have a single return and check for guc->ads_golden_ctxt_size.
This is just a readability improvement, no change in behavior.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +3 -3
@@ -461,10 +461,10 @@ static int guc_prep_golden_context(struct intel_guc *guc) addr_ggtt += alloc_size; } -if (dma_buf_map_is_null (&guc->ads_map)) -return total_size; +/* Make sure current size matches what we calculated previously */ +if (guc->ads_golden_ctxt_size) +GEM_BUG_ON (guc->ads_golden_ctxt_size != total_size); -GEM_BUG_ON (guc->ads_golden_ctxt_size != total_size);return total_size; }
Signature · 1 line
2.35.0
PATCH 13/19 drm/i915/guc: Convert mapping table to dma_buf_map
In reply to Lucas De MarchiUse dma_buf_map to write the fields system_info.mapping_table[][]. Since we already have the info_map around where needed, just use it instead of going through guc->ads_map.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +6 -6
@@ -204,7 +204,7 @@ int intel_guc_global_policies_update(struct intel_guc *guc) }static void guc_mapping_table_init (struct intel_gt *gt, -struct guc_gt_system_info *system_info) +struct dma_buf_map *info_map) {unsigned int i, j;struct intel_engine_cs *engine;
@@ -213,14 +213,14 @@ static void guc_mapping_table_init(struct intel_gt *gt,/* Table must be set to invalid values for entries not used */ for (i =0 ; i <GUC_MAX_ENGINE_CLASSES ; ++i)for (j =0 ; j <GUC_MAX_INSTANCES_PER_CLASS ; ++j) - system_info->mapping_table[i][j] = -GUC_MAX_INSTANCES_PER_CLASS ; +info_map_write (info_map, mapping_table[i][j], +GUC_MAX_INSTANCES_PER_CLASS );for_each_engine (engine, gt, id) {u8 guc_class =engine_class_to_guc_class (engine->class); - system_info->mapping_table[guc_class][ilog2 (engine->logical_mask)] = - engine->instance; +info_map_write (info_map, mapping_table[guc_class][ilog2 (engine->logical_mask)], + engine->instance); } }
@@ -595,7 +595,7 @@ static void __guc_ads_init(struct intel_guc *guc)/* Golden contexts for re-initialising after a watchdog reset */ guc_prep_golden_context (guc); -guc_mapping_table_init (guc_to_gt (guc), &blob->system_info); +guc_mapping_table_init (guc_to_gt (guc), &info_map); base =intel_guc_ggtt_offset (guc, guc->ads_vma);
Signature · 1 line
2.35.0
PATCH 14/19 drm/i915/guc: Convert capture list to dma_buf_map
In reply to Lucas De MarchiUse dma_buf_map to write the fields ads.capture_*.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +5 -5
@@ -544,7 +544,7 @@ static void guc_init_golden_context(struct intel_guc *guc)GEM_BUG_ON (guc->ads_golden_ctxt_size != total_size); } -static void guc_capture_list_init (struct intel_guc *guc,struct __guc_ads_blob *blob) +static void guc_capture_list_init (struct intel_guc *guc) {int i, j;u32 addr_ggtt, offset;
@@ -556,11 +556,11 @@ static void guc_capture_list_init(struct intel_guc *guc, struct __guc_ads_blob *for (i =0 ; i <GUC_CAPTURE_LIST_INDEX_MAX ; i++) {for (j =0 ; j <GUC_MAX_ENGINE_CLASSES ; j++) { - blob->ads.capture_instance[i][j] = addr_ggtt; - blob->ads.capture_class[i][j] = addr_ggtt; +ads_blob_write (guc, ads.capture_instance[i][j], addr_ggtt); +ads_blob_write (guc, ads.capture_class[i][j], addr_ggtt); } - blob->ads.capture_global[i] = addr_ggtt; +ads_blob_write (guc, ads.capture_global[i], addr_ggtt); } }
@@ -600,7 +600,7 @@ static void __guc_ads_init(struct intel_guc *guc) base =intel_guc_ggtt_offset (guc, guc->ads_vma);/* Capture list for hang debug */ -guc_capture_list_init (guc, blob); +guc_capture_list_init (guc);/* ADS */ blob->ads.scheduler_policies = base +ptr_offset (blob, policies);
Signature · 1 line
2.35.0
PATCH 15/19 drm/i915/guc: Prepare for error propagation
In reply to Lucas De MarchiCurrently guc_mmio_reg_add() relies on having enough memory available in the array to add a new slot. It usesGEM_BUG_ON(count >= regset->size); to protect going above the threshold.
In order to allow guc_mmio_reg_add() to handle the memory allocation by itself, it must return an error in case of failures. Adjust return code so this error can be propagated to the callers of guc_mmio_reg_add() and guc_mmio_regset_init().
No intended change in behavior.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 31 +++++++++++++--------- 1 file changed, 18 insertions(+), 13 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +18 -13
@@ -244,8 +244,8 @@ static int guc_mmio_reg_cmp(const void *a, const void *b)return (int )ra->offset - (int )rb->offset; } -static void guc_mmio_reg_add (struct temp_regset *regset, -u32 offset,u32 flags) +static long __must_check guc_mmio_reg_add (struct temp_regset *regset, +u32 offset,u32 flags) {u32 count = regset->used;struct guc_mmio_reg reg = {
@@ -264,7 +264,7 @@ static void guc_mmio_reg_add(struct temp_regset *regset,*/ if (bsearch (®, regset->registers, count,sizeof (reg), guc_mmio_reg_cmp)) -return ; +return 0 ; slot = ®set->registers[count]; regset->used++;
@@ -277,6 +277,8 @@ static void guc_mmio_reg_add(struct temp_regset *regset,swap (slot[1 ], slot[0 ]); } + +return 0 ; }#define GUC_MMIO_REG_ADD (regset, reg, masked) \
@@ -284,32 +286,35 @@ static void guc_mmio_reg_add(struct temp_regset *regset, i915_mmio_reg_offset((reg)), \ (masked) ? GUC_REGSET_MASKED : 0) -static void guc_mmio_regset_init (struct temp_regset *regset, -struct intel_engine_cs *engine) +static int guc_mmio_regset_init (struct temp_regset *regset, +struct intel_engine_cs *engine) {const u32 base = engine->mmio_base;struct i915_wa_list *wal = &engine->wa_list;struct i915_wa *wa;unsigned int i; +int ret =0 ; regset->used =0 ; -GUC_MMIO_REG_ADD (regset,RING_MODE_GEN7 (base), true); -GUC_MMIO_REG_ADD (regset,RING_HWS_PGA (base), false); -GUC_MMIO_REG_ADD (regset,RING_IMR (base), false); + ret |=GUC_MMIO_REG_ADD (regset,RING_MODE_GEN7 (base), true); + ret |=GUC_MMIO_REG_ADD (regset,RING_HWS_PGA (base), false); + ret |=GUC_MMIO_REG_ADD (regset,RING_IMR (base), false);for (i =0 , wa = wal->list; i < wal->count; i++, wa++) -GUC_MMIO_REG_ADD (regset, wa->reg, wa->masked_reg); + ret |=GUC_MMIO_REG_ADD (regset, wa->reg, wa->masked_reg);/* Be extra paranoid and include all whitelist registers. */ for (i =0 ; i <RING_MAX_NONPRIV_SLOTS ; i++) -GUC_MMIO_REG_ADD (regset, -RING_FORCE_TO_NONPRIV (base, i), - false); + ret |=GUC_MMIO_REG_ADD (regset, +RING_FORCE_TO_NONPRIV (base, i), + false);/* add in local MOCS registers */ for (i =0 ; i <GEN9_LNCFCMOCS_REG_COUNT ; i++) -GUC_MMIO_REG_ADD (regset,GEN9_LNCFCMOCS (i), false); + ret |=GUC_MMIO_REG_ADD (regset,GEN9_LNCFCMOCS (i), false); + +return ret ?-1 :0 ; }static int guc_mmio_reg_state_query (struct intel_guc *guc)
Signature · 1 line
2.35.0
PATCH 16/19 drm/i915/guc: Use a single pass to calculate regset
In reply to Lucas De MarchiThe ADS initialitazion was using 2 passes to calculate the regset sent to GuC to initialize each engine: the first pass to just have the final object size and the second to set each register in place in the final gem object.
However in order to maintain an ordered set of registers to pass to guc, each register needs to be added and moved in the final array. The second phase may actually happen in IO memory rather than system memory and accessing IO memory by simply dereferencing the pointer doesn't work on all architectures. Other places of the ADS initializaition were converted to use the dma_buf_map API, but here there may be a lot more accesses to IO memory. So, instead of following that same approach, convert the regset initialization to calculate the final array in 1 pass and in the second pass that array is just copied to its final location, updating the pointers for each engine written to the ADS blob.
One important thing is that struct temp_regset now have different semantics: registers continues to track the registers of a single engine, however the other fields are updated together, according to the newly added storage, which tracks the memory allocated for all the registers. So rename some of these fields and add a __mmio_reg_add(): this function (possibly) allocates memory and operates on the storage pointer while guc_mmio_reg_add() continues to manage the registers pointer.
On a Tiger Lake system using enable_guc=3, the following log message is now seen:
[ 187.334310] i915 0000:00:02.0: [drm:intel_guc_ads_create [i915]] Used 4 KB for temporary ADS regset
This change has also been tested on an ARM64 host with DG2 and other discrete graphics cards.
--- drivers/gpu/drm/i915/gt/uc/intel_guc.h | 7 ++ drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 117 +++++++++++++-------- 2 files changed, 79 insertions(+), 45 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc.h +7 -0
@@ -152,6 +152,13 @@ struct intel_guc {struct dma_buf_map ads_map;/** @ads_regset_size: size of the save/restore regsets in the ADS */ u32 ads_regset_size; +/** +* @ads_regset_count: number of save/restore registers in the ADS for +* each engine +*/ +u32 ads_regset_count[I915_NUM_ENGINES ]; +/** @ads_regset: save/restore regsets in the ADS */ +struct guc_mmio_reg *ads_regset;/** @ads_golden_ctxt_size: size of the golden contexts in the ADS */ u32 ads_golden_ctxt_size;/** @ads_engine_usage_size: size of engine usage in the ADS */
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +72 -45
206 lines not on this page · raw message
Signature · 1 line
2.35.0
kernel test robot
build botRe: [PATCH 16/19] drm/i915/guc: Use a single pass to calculate regset
Thank you for the patch! Perhaps something to improve:
Hi Lucas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on next-20220125]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next drm/drm-next tegra-drm/drm/tegra/for-next linus/master airlied/drm-next v5.17-rc1] [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/Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip config: i386-randconfig-m021-20220124 (https://download.01.org/0day-ci/archive/20220127/202201270827.CLIhfdPe-lkp(a)intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce (this is a W=1 build): # https://github.com/0day-ci/linux/commit/313757d9ed833acea4ee2bb0e3f3565d6efcf3cc git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 git checkout 313757d9ed833acea4ee2bb0e3f3565d6efcf3cc # save the config file to linux build tree mkdir build_dir make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag as appropriate
All warnings (new ones prefixed by >>):
In file included from include/drm/drm_mm.h:51,
from drivers/gpu/drm/i915/i915_vma.h:31,
from drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h:13,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:20,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:18,
from drivers/gpu/drm/i915/gt/intel_gt.h:10,
from drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:9:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c: In function 'guc_mmio_reg_state_create':
>> drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:38: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'u32' {aka 'unsigned int'} [-Wformat=]
369 | drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
370 | (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| u32 {aka unsigned int}
include/drm/drm_print.h:461:56: note: in definition of macro 'drm_dbg'
461 | drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
| ^~~
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:46: note: format string is defined here
369 | drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
| ~~^
| |
| long unsigned int
| %uvim +369 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c
348
349 static long guc_mmio_reg_state_create(struct intel_guc *guc)
350 {
351 struct intel_gt *gt = guc_to_gt(guc);
352 struct intel_engine_cs *engine;
353 enum intel_engine_id id;
354 struct temp_regset temp_set = {};
355 long total = 0;
356
357 for_each_engine(engine, gt, id) {
358 u32 used = temp_set.storage_used;
359
360 if (guc_mmio_regset_init(&temp_set, engine) < 0)
361 return -1;
362
363 guc->ads_regset_count[id] = temp_set.storage_used - used;
364 total += guc->ads_regset_count[id];
365 }
366
367 guc->ads_regset = temp_set.storage;
368
> 369 drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
370 (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
371
372 return total * sizeof(struct guc_mmio_reg);
373 }
374
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
kernel test robot
build botRe: [PATCH 16/19] drm/i915/guc: Use a single pass to calculate regset
In reply to Lucas De MarchiThank you for the patch! Perhaps something to improve:
Hi Lucas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on next-20220125]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next drm/drm-next tegra-drm/drm/tegra/for-next linus/master airlied/drm-next v5.17-rc1] [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/Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip config: i386-randconfig-a011 (https://download.01.org/0day-ci/archive/20220127/202201270902.HcRe2frP-lkp(a)intel.com/config) compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 2a1b7aa016c0f4b5598806205bdfbab1ea2d92c4)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/313757d9ed833acea4ee2bb0e3f3565d6efcf3cc
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 git checkout 313757d9ed833acea4ee2bb0e3f3565d6efcf3cc
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag as appropriate
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:370:3: warning: format specifies type 'unsigned long' but the argument has type 'unsigned int' [-Wformat]
(temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/drm/drm_print.h:461:63: note: expanded from macro 'drm_dbg'
drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
~~~ ^~~~~~~~~~~1 warning generated.
vim +370 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c
348
349 static long guc_mmio_reg_state_create(struct intel_guc *guc)
350 {
351 struct intel_gt *gt = guc_to_gt(guc);
352 struct intel_engine_cs *engine;
353 enum intel_engine_id id;
354 struct temp_regset temp_set = {};
355 long total = 0;
356
357 for_each_engine(engine, gt, id) {
358 u32 used = temp_set.storage_used;
359
360 if (guc_mmio_regset_init(&temp_set, engine) < 0)
361 return -1;
362
363 guc->ads_regset_count[id] = temp_set.storage_used - used;
364 total += guc->ads_regset_count[id];
365 }
366
367 guc->ads_regset = temp_set.storage;
368
369 drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
> 370 (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
371
372 return total * sizeof(struct guc_mmio_reg);
373 }
374
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
kernel test robot
build botRe: [PATCH 16/19] drm/i915/guc: Use a single pass to calculate regset
In reply to Lucas De MarchiThank you for the patch! Yet something to improve:
Hi Lucas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[also build test ERROR on next-20220125]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next drm/drm-next tegra-drm/drm/tegra/for-next linus/master airlied/drm-next v5.17-rc1] [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/Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220127/202201271208.kELpe3Mn-lkp(a)intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/313757d9ed833acea4ee2bb0e3f3565d6efcf3cc
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Lucas-De-Marchi/drm-i915-guc-Refactor-ADS-access-to-use-dma_buf_map/20220127-043912 git checkout 313757d9ed833acea4ee2bb0e3f3565d6efcf3cc
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
All errors (new ones prefixed by >>):
In file included from include/drm/drm_mm.h:51,
from drivers/gpu/drm/i915/i915_vma.h:31,
from drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h:13,
from drivers/gpu/drm/i915/gt/uc/intel_guc.h:20,
from drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from drivers/gpu/drm/i915/gt/intel_gt_types.h:18,
from drivers/gpu/drm/i915/gt/intel_gt.h:10,
from drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:9:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c: In function 'guc_mmio_reg_state_create':
>> drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:38: error: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'u32' {aka 'unsigned int'} [-Werror=format=]
369 | drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
370 | (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| u32 {aka unsigned int}
include/drm/drm_print.h:461:56: note: in definition of macro 'drm_dbg'
461 | drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
| ^~~
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:46: note: format string is defined here
369 | drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
| ~~^
| |
| long unsigned int
| %ucc1: all warnings being treated as errors
vim +369 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c
348
349 static long guc_mmio_reg_state_create(struct intel_guc *guc)
350 {
351 struct intel_gt *gt = guc_to_gt(guc);
352 struct intel_engine_cs *engine;
353 enum intel_engine_id id;
354 struct temp_regset temp_set = {};
355 long total = 0;
356
357 for_each_engine(engine, gt, id) {
358 u32 used = temp_set.storage_used;
359
360 if (guc_mmio_regset_init(&temp_set, engine) < 0)
361 return -1;
362
363 guc->ads_regset_count[id] = temp_set.storage_used - used;
364 total += guc->ads_regset_count[id];
365 }
366
367 guc->ads_regset = temp_set.storage;
368
> 369 drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
370 (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
371
372 return total * sizeof(struct guc_mmio_reg);
373 }
374
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Re: [PATCH 16/19] drm/i915/guc: Use a single pass to calculate regset
In reply to Lucas De MarchiQuoted 71 lines · Lucas De Marchi
The ADS initialitazion was using 2 passes to calculate the regset sent to GuC to initialize each engine: the first pass to just have the final object size and the second to set each register in place in the final gem object.
However in order to maintain an ordered set of registers to pass to guc, each register needs to be added and moved in the final array. The second phase may actually happen in IO memory rather than system memory and accessing IO memory by simply dereferencing the pointer doesn't work on all architectures. Other places of the ADS initializaition were converted to use the
dma_buf_mapAPI, but here there may be a lot more accesses to IO memory. So, instead of following that same approach, convert the regset initialization to calculate the final array in 1 pass and in the second pass that array is just copied to its final location, updating the pointers for each engine written to the ADS blob.One important thing is that struct
temp_regsetnow have different semantics:registerscontinues to track the registers of a single engine, however the other fields are updated together, according to the newly addedstorage, which tracks the memory allocated for all the registers. So rename some of these fields and add a__mmio_reg_add(): this function (possibly) allocates memory and operates on the storage pointer whileguc_mmio_reg_add()continues to manage the registers pointer.On a Tiger Lake system using enable_guc=3, the following log message is now seen:
[ 187.334310] i915 0000:00:02.0: [drm:intel_guc_ads_create [i915]] Used 4 KB for temporary ADS regsetThis change has also been tested on an ARM64 host with DG2 and other discrete graphics cards.
Cc Matt Roper <[email protected]>Cc Thomas Hellström <[email protected]>Cc Daniel Vetter <[email protected]>Cc John Harrison <[email protected]>Cc Matthew Brost <[email protected]>Cc Daniele Ceraolo Spurio <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- drivers/gpu/drm/i915/gt/uc/intel_guc.h | 7 ++ drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 117 +++++++++++++-------- 2 files changed, 79 insertions(+), 45 deletions(-)drivers/gpu/drm/i915/gt/uc/intel_guc.h +7
-0@@ -152,6 +152,13 @@ struct intel_guc {struct dma_buf_map ads_map;/** @ads_regset_size: size of the save/restore regsets in the ADS */ u32 ads_regset_size; +/** +* @ads_regset_count: number of save/restore registers in the ADS for +* each engine +*/ +u32 ads_regset_count[I915_NUM_ENGINES ]; +/** @ads_regset: save/restore regsets in the ADS */ +struct guc_mmio_reg *ads_regset;/** @ads_golden_ctxt_size: size of the golden contexts in the ADS */ u32 ads_golden_ctxt_size;/** @ads_engine_usage_size: size of engine usage in the ADS */ drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +0
-0@@ -226,14 +226,13 @@ static void guc_mapping_table_init(struct intel_gt *gt,/* * The save/restore register list must be pre-calculated to a temporary
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c static void guc_mapping_table_init(struct intel_gt *gt, · line 233
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +2
-5-* buffer of driver defined size before it can be generated in place -* inside the ADS. +* buffer before it can be copied inside the ADS. */ -#define MAX_MMIO_REGS 128/* Arbitrary size, increase as needed */ struct temp_regset {struct guc_mmio_reg *registers; -u32 used; -u32 size; +struct guc_mmio_reg *storage;
I think this could use a comment to distinguish between registers and storage. Something like.:
/* ptr to the base of the allocated storage for all engines */ struct guc_mmio_reg *storage;
/* ptr to the section of the storage for the engine currently being worked on */ struct guc_mmio_reg *registers;
Quoted 103 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +42
-19+u32 storage_used; +u32 storage_max; };static int guc_mmio_reg_cmp (const void *a,const void *b)@@ -244,18 +243,44 @@ static int guc_mmio_reg_cmp(const void *a, const void *b)return (int )ra->offset - (int )rb->offset; } +static struct guc_mmio_reg *__must_check +__mmio_reg_add (struct temp_regset *regset,struct guc_mmio_reg *reg) +{ +u32 pos = regset->storage_used; +struct guc_mmio_reg *slot; + +if (pos >= regset->storage_max) { +size_t size =ALIGN ((pos +1 ) *sizeof (*slot),PAGE_SIZE ); +struct guc_mmio_reg *r =krealloc (regset->storage, + size,GFP_KERNEL ); +if (!r) { +WARN_ONCE (1 ,"Incomplete regset list: can't add register (%d)\n" , + -ENOMEM ); +return ERR_PTR (-ENOMEM ); + } + + regset->registers = r + (regset->registers - regset->storage); + regset->storage = r; + regset->storage_max = size /sizeof (*slot); + } + + slot = ®set->storage[pos]; + regset->storage_used++; + *slot = *reg; + +return slot; +} +static long __must_check guc_mmio_reg_add (struct temp_regset *regset,u32 offset,u32 flags) { -u32 count = regset->used; +u32 count = regset->storage_used - (regset->registers - regset->storage);struct guc_mmio_reg reg = { .offset = offset, .flags = flags, };struct guc_mmio_reg *slot; -GEM_BUG_ON (count >= regset->size); -/* * The mmio list is built using separate lists within the driver. * It's possible that at some point we may attempt to add the same @@ -266,9 +291,9 @@ static long __must_check guc_mmio_reg_add(struct temp_regset *regset, sizeof(reg), guc_mmio_reg_cmp))return 0 ; - slot = ®set->registers[count]; - regset->used++; - *slot = reg; + slot =__mmio_reg_add (regset, ®); +if (IS_ERR (slot)) +return PTR_ERR (slot);while (slot-- > regset->registers) {GEM_BUG_ON (slot[0 ].offset == slot[1 ].offset);@@ -295,7 +320,11 @@ static int guc_mmio_regset_init(struct temp_regset *regset,unsigned int i;int ret =0 ; - regset->used =0 ; +/* +* Each engine's registers point to a new start relative to +* storage +*/ + regset->registers = regset->storage + regset->storage_used; ret |=GUC_MMIO_REG_ADD (regset,RING_MODE_GEN7 (base), true); ret |=GUC_MMIO_REG_ADD (regset,RING_HWS_PGA (base), false);@@ -317,32 +346,28 @@ static int guc_mmio_regset_init(struct temp_regset *regset,return ret ?-1 :0 ; } -static int guc_mmio_reg_state_query (struct intel_guc *guc) +static long guc_mmio_reg_state_create (struct intel_guc *guc) {struct intel_gt *gt =guc_to_gt (guc);struct intel_engine_cs *engine;enum intel_engine_id id; -struct temp_regset temp_set; -u32 total; +struct temp_regset temp_set = {}; +long total =0 ; -/* -* Need to actually build the list in order to filter out -* duplicates and other such data dependent constructions. -*/ - temp_set.size =MAX_MMIO_REGS ; - temp_set.registers =kmalloc_array (temp_set.size, -sizeof (*temp_set.registers), -GFP_KERNEL ); -if (!temp_set.registers)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c static int guc_mmio_regset_init(struct temp_regset *regset, · line 361
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +4
-5-return -ENOMEM ; - - total =0 ;for_each_engine (engine, gt, id) { -guc_mmio_regset_init (&temp_set, engine); - total += temp_set.used; +u32 used = temp_set.storage_used; + +if (guc_mmio_regset_init (&temp_set, engine) <0 ) +return -1 ;
If you fail here you're leaking temp_set.storage.
Also, any reason not to just return the return code from guc_mmio_regset_init?
Apart from these minor comments, the change LGTM. IMO we could also merge this patch on its own ahead of the rest of the dma_buf code, because not having to recreate the regset on every reset/resume is still helpful.
Daniele
Quoted 87 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +24
-16+ + guc->ads_regset_count[id] = temp_set.storage_used - used; + total += guc->ads_regset_count[id]; } -kfree (temp_set.registers); + guc->ads_regset = temp_set.storage; + +drm_dbg (&guc_to_gt (guc)->i915->drm,"Used %lu KB for temporary ADS regset\n" , + (temp_set.storage_max *sizeof (struct guc_mmio_reg )) >>10 );return total *sizeof (struct guc_mmio_reg ); }@@ -352,40 +377,38 @@ static void guc_mmio_reg_state_init(struct intel_guc *guc, {struct intel_gt *gt =guc_to_gt (guc);struct intel_engine_cs *engine; +struct guc_mmio_reg *ads_registers;enum intel_engine_id id; -struct temp_regset temp_set; -struct guc_mmio_reg_set *ads_reg_set;u32 addr_ggtt, offset; -u8 guc_class; offset =guc_ads_regset_offset (guc); addr_ggtt =intel_guc_ggtt_offset (guc, guc->ads_vma) + offset; - temp_set.registers = (struct guc_mmio_reg *)(((u8 *)blob) + offset); - temp_set.size = guc->ads_regset_size /sizeof (temp_set.registers[0 ]); + ads_registers = (struct guc_mmio_reg *)(((u8 *)blob) + offset); + +memcpy (ads_registers, guc->ads_regset, guc->ads_regset_size);for_each_engine (engine, gt, id) { +u32 count = guc->ads_regset_count[id]; +struct guc_mmio_reg_set *ads_reg_set; +u8 guc_class; +/* Class index is checked in class converter */ GEM_BUG_ON (engine->instance >=GUC_MAX_INSTANCES_PER_CLASS ); guc_class =engine_class_to_guc_class (engine->class); ads_reg_set = &blob->ads.reg_state_list[guc_class][engine->instance]; -guc_mmio_regset_init (&temp_set, engine); -if (!temp_set.used) { +if (!count) { ads_reg_set->address =0 ; ads_reg_set->count =0 ;continue ; } ads_reg_set->address = addr_ggtt; - ads_reg_set->count = temp_set.used; + ads_reg_set->count = count; - temp_set.size -= temp_set.used; - temp_set.registers += temp_set.used; - addr_ggtt += temp_set.used *sizeof (struct guc_mmio_reg ); + addr_ggtt += count *sizeof (struct guc_mmio_reg ); } - -GEM_BUG_ON (temp_set.size); } static void fill_engine_enable_masks(struct intel_gt *gt,@@ -634,8 +657,11 @@ int intel_guc_ads_create(struct intel_guc *guc)GEM_BUG_ON (guc->ads_vma); -/* Need to calculate the reg state size dynamically: */ - ret =guc_mmio_reg_state_query (guc); +/* +* Create reg state size dynamically on system memory to be copied to +* the final ads blob on gt init/reset +*/ + ret =guc_mmio_reg_state_create (guc);if (ret <0 )return ret; guc->ads_regset_size = ret;@@ -681,6 +707,7 @@ void intel_guc_ads_destroy(struct intel_guc *guc)i915_vma_unpin_and_release (&guc->ads_vma,I915_VMA_RELEASE_MAP ); guc->ads_blob =NULL ;dma_buf_map_clear (&guc->ads_map); +kfree (guc->ads_regset); }static void guc_ads_private_data_reset (struct intel_guc *guc)
Re: [PATCH 16/19] drm/i915/guc: Use a single pass to calculate regset
Quoted 86 lines · Daniele Ceraolo Spurio
Quoted 70 lines · Lucas De Marchi
The ADS initialitazion was using 2 passes to calculate the regset sent to GuC to initialize each engine: the first pass to just have the final object size and the second to set each register in place in the final gem object.
However in order to maintain an ordered set of registers to pass to guc, each register needs to be added and moved in the final array. The second phase may actually happen in IO memory rather than system memory and accessing IO memory by simply dereferencing the pointer doesn't work on all architectures. Other places of the ADS initializaition were converted to use the
dma_buf_mapAPI, but here there may be a lot more accesses to IO memory. So, instead of following that same approach, convert the regset initialization to calculate the final array in 1 pass and in the second pass that array is just copied to its final location, updating the pointers for each engine written to the ADS blob.One important thing is that struct
temp_regsetnow have different semantics:registerscontinues to track the registers of a single engine, however the other fields are updated together, according to the newly addedstorage, which tracks the memory allocated for all the registers. So rename some of these fields and add a__mmio_reg_add(): this function (possibly) allocates memory and operates on the storage pointer whileguc_mmio_reg_add()continues to manage the registers pointer.On a Tiger Lake system using enable_guc=3, the following log message is now seen:
[ 187.334310] i915 0000:00:02.0: [drm:intel_guc_ads_create [i915]] Used 4 KB for temporary ADS regsetThis change has also been tested on an ARM64 host with DG2 and other discrete graphics cards.
Cc Matt Roper <[email protected]>Cc Thomas Hellström <[email protected]>Cc Daniel Vetter <[email protected]>Cc John Harrison <[email protected]>Cc Matthew Brost <[email protected]>Cc Daniele Ceraolo Spurio <[email protected]>Signed-off-by Lucas De Marchi <[email protected]>--- drivers/gpu/drm/i915/gt/uc/intel_guc.h | 7 ++ drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 117 +++++++++++++-------- 2 files changed, 79 insertions(+), 45 deletions(-)drivers/gpu/drm/i915/gt/uc/intel_guc.h +7
-0@@ -152,6 +152,13 @@ struct intel_guc {struct dma_buf_map ads_map;/** @ads_regset_size: size of the save/restore regsets in the ADS */ u32 ads_regset_size; +/** +* @ads_regset_count: number of save/restore registers in the ADS for +* each engine +*/ +u32 ads_regset_count[I915_NUM_ENGINES ]; +/** @ads_regset: save/restore regsets in the ADS */ +struct guc_mmio_reg *ads_regset;/** @ads_golden_ctxt_size: size of the golden contexts in the ADS */ u32 ads_golden_ctxt_size;/** @ads_engine_usage_size: size of engine usage in the ADS */ drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +0
-0@@ -226,14 +226,13 @@ static void guc_mapping_table_init(struct intel_gt *gt,/* * The save/restore register list must be pre-calculated to a temporary drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c static void guc_mapping_table_init(struct intel_gt *gt, · line 232
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +2
-5-* buffer of driver defined size before it can be generated in place -* inside the ADS. +* buffer before it can be copied inside the ADS. */ -#define MAX_MMIO_REGS 128/* Arbitrary size, increase as needed */ struct temp_regset {struct guc_mmio_reg *registers; -u32 used; -u32 size; +struct guc_mmio_reg *storage;I think this could use a comment to distinguish between registers and storage. Something like.:
Quoted 5 lines
/* ptr to the base of the allocated storage for all engines */ struct
guc_mmio_reg*storage;/* ptr to the section of the storage for the engine currently being worked on */ struct
guc_mmio_reg*registers;
agreed, I will add that
Quoted 100 lines
Quoted 100 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +42
-22+u32 storage_used; +u32 storage_max; };static int guc_mmio_reg_cmp (const void *a,const void *b)@@ -244,18 +243,44 @@ static int guc_mmio_reg_cmp(const void *a, const void *b)return (int )ra->offset - (int )rb->offset; } +static struct guc_mmio_reg *__must_check +__mmio_reg_add (struct temp_regset *regset,struct guc_mmio_reg *reg) +{ +u32 pos = regset->storage_used; +struct guc_mmio_reg *slot; + +if (pos >= regset->storage_max) { +size_t size =ALIGN ((pos +1 ) *sizeof (*slot),PAGE_SIZE ); +struct guc_mmio_reg *r =krealloc (regset->storage, + size,GFP_KERNEL ); +if (!r) { +WARN_ONCE (1 ,"Incomplete regset list: can't add register (%d)\n" , + -ENOMEM ); +return ERR_PTR (-ENOMEM ); + } + + regset->registers = r + (regset->registers - regset->storage); + regset->storage = r; + regset->storage_max = size /sizeof (*slot); + } + + slot = ®set->storage[pos]; + regset->storage_used++; + *slot = *reg; + +return slot; +} +static long __must_check guc_mmio_reg_add (struct temp_regset *regset,u32 offset,u32 flags) { -u32 count = regset->used; +u32 count = regset->storage_used - (regset->registers - regset->storage);struct guc_mmio_reg reg = { .offset = offset, .flags = flags, };struct guc_mmio_reg *slot; -GEM_BUG_ON (count >= regset->size); -/* * The mmio list is built using separate lists within the driver. * It's possible that at some point we may attempt to add the same @@ -266,9 +291,9 @@ static long __must_check guc_mmio_reg_add(struct temp_regset *regset, sizeof(reg), guc_mmio_reg_cmp))return 0 ; - slot = ®set->registers[count]; - regset->used++; - *slot = reg; + slot =__mmio_reg_add (regset, ®); +if (IS_ERR (slot)) +return PTR_ERR (slot);while (slot-- > regset->registers) {GEM_BUG_ON (slot[0 ].offset == slot[1 ].offset);@@ -295,7 +320,11 @@ static int guc_mmio_regset_init(struct temp_regset *regset,unsigned int i;int ret =0 ; - regset->used =0 ; +/* +* Each engine's registers point to a new start relative to +* storage +*/ + regset->registers = regset->storage + regset->storage_used; ret |=GUC_MMIO_REG_ADD (regset,RING_MODE_GEN7 (base), true); ret |=GUC_MMIO_REG_ADD (regset,RING_HWS_PGA (base), false);@@ -317,32 +346,28 @@ static int guc_mmio_regset_init(struct temp_regset *regset,return ret ?-1 :0 ; } -static int guc_mmio_reg_state_query (struct intel_guc *guc) +static long guc_mmio_reg_state_create (struct intel_guc *guc) {struct intel_gt *gt =guc_to_gt (guc);struct intel_engine_cs *engine;enum intel_engine_id id; -struct temp_regset temp_set; -u32 total; +struct temp_regset temp_set = {}; +long total =0 ; -/* -* Need to actually build the list in order to filter out -* duplicates and other such data dependent constructions. -*/ - temp_set.size =MAX_MMIO_REGS ; - temp_set.registers =kmalloc_array (temp_set.size, -sizeof (*temp_set.registers), -GFP_KERNEL ); -if (!temp_set.registers) -return -ENOMEM ; - - total =0 ;for_each_engine (engine, gt, id) {
Quoted 8 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c static int guc_mmio_regset_init(struct temp_regset *regset, · line 361
Quoted 6 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +4
-2-guc_mmio_regset_init (&temp_set, engine); - total += temp_set.used; +u32 used = temp_set.storage_used; + +if (guc_mmio_regset_init (&temp_set, engine) <0 ) +return -1 ;If you fail here you're leaking temp_set.storage.
thanks for catching this. I fixed it for next version
Quoted 1 line
Also, any reason not to just return the return code from
guc_mmio_regset_init?
no
Quoted 1 line
Apart from these minor comments, the change LGTM. IMO we could also merge this patch on its own ahead of the rest of the
dma_bufcode, because not having to recreate the regset on every reset/resume is still helpful.
now the dma_buf_map (renamed to iosys_map) is more settled. I will send everything together once more and than probably split on next versions if needed.
thanks
Lucas De Marchi
PATCH 17/19 drm/i915/guc: Convert guc_mmio_reg_state_init to dma_buf_map
In reply to Lucas De MarchiNow that the regset list is prepared, convert guc_mmio_reg_state_init() to use dma_buf_map to copy the array to the final location and initialize additional fields in ads.reg_state_list.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 30 +++++++++++++--------- 1 file changed, 18 insertions(+), 12 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +18 -12
@@ -372,40 +372,46 @@ static long guc_mmio_reg_state_create(struct intel_guc *guc)return total *sizeof (struct guc_mmio_reg ); } -static void guc_mmio_reg_state_init (struct intel_guc *guc, -struct __guc_ads_blob *blob) +static void guc_mmio_reg_state_init (struct intel_guc *guc) { +struct dma_buf_map ads_regset_map;struct intel_gt *gt =guc_to_gt (guc);struct intel_engine_cs *engine; -struct guc_mmio_reg *ads_registers;enum intel_engine_id id;u32 addr_ggtt, offset; offset =guc_ads_regset_offset (guc); addr_ggtt =intel_guc_ggtt_offset (guc, guc->ads_vma) + offset; - ads_registers = (struct guc_mmio_reg *)(((u8 *)blob) + offset); + ads_regset_map =DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, offset); -memcpy (ads_registers, guc->ads_regset, guc->ads_regset_size); +dma_buf_map_memcpy_to (&ads_regset_map, guc->ads_regset, + guc->ads_regset_size);for_each_engine (engine, gt, id) {u32 count = guc->ads_regset_count[id]; -struct guc_mmio_reg_set *ads_reg_set;u8 guc_class;/* Class index is checked in class converter */ GEM_BUG_ON (engine->instance >=GUC_MAX_INSTANCES_PER_CLASS ); guc_class =engine_class_to_guc_class (engine->class); - ads_reg_set = &blob->ads.reg_state_list[guc_class][engine->instance];if (!count) { - ads_reg_set->address =0 ; - ads_reg_set->count =0 ; +ads_blob_write (guc, + ads.reg_state_list[guc_class][engine->instance].address, +0 ); +ads_blob_write (guc, + ads.reg_state_list[guc_class][engine->instance].count, +0 );continue ; } - ads_reg_set->address = addr_ggtt; - ads_reg_set->count = count; +ads_blob_write (guc, + ads.reg_state_list[guc_class][engine->instance].address, + addr_ggtt); +ads_blob_write (guc, + ads.reg_state_list[guc_class][engine->instance].count, + count); addr_ggtt += count *sizeof (struct guc_mmio_reg ); }
@@ -635,7 +641,7 @@ static void __guc_ads_init(struct intel_guc *guc) blob->ads.gt_system_info = base +ptr_offset (blob, system_info);/* MMIO save/restore list */ -guc_mmio_reg_state_init (guc, blob); +guc_mmio_reg_state_init (guc);/* Private Data */ blob->ads.private_data = base +guc_ads_private_data_offset (guc);
Signature · 1 line
2.35.0
PATCH 18/19 drm/i915/guc: Convert __guc_ads_init to dma_buf_map
In reply to Lucas De MarchiNow that all the called functions from __guc_ads_init() are converted to use ads_map, stop using ads_blob in __guc_ads_init().
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 25 ++++++++++++---------- 1 file changed, 14 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +14 -11
@@ -602,7 +602,6 @@ static void __guc_ads_init(struct intel_guc *guc) {struct intel_gt *gt =guc_to_gt (guc);struct drm_i915_private *i915 = gt->i915; -struct __guc_ads_blob *blob = guc->ads_blob;struct dma_buf_map info_map =DMA_BUF_MAP_INIT_OFFSET (&guc->ads_map, offsetof(struct __guc_ads_blob , system_info));u32 base;
@@ -613,17 +612,18 @@ static void __guc_ads_init(struct intel_guc *guc)/* System info */ fill_engine_enable_masks (gt, &info_map); - blob->system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_SLICE_ENABLED ] = -hweight8 (gt->info.sseu.slice_mask); - blob->system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_VDBOX_SFC_SUPPORT_MASK ] = - gt->info.vdbox_sfc_access; +ads_blob_write (guc, system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_SLICE_ENABLED ], +hweight8 (gt->info.sseu.slice_mask)); +ads_blob_write (guc, system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_VDBOX_SFC_SUPPORT_MASK ], + gt->info.vdbox_sfc_access);if (GRAPHICS_VER (i915) >=12 && !IS_DGFX (i915)) {u32 distdbreg =intel_uncore_read (gt->uncore,GEN12_DIST_DBS_POPULATED ); - blob->system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_DOORBELL_COUNT_PER_SQIDI ] = - ((distdbreg >>GEN12_DOORBELLS_PER_SQIDI_SHIFT ) & -GEN12_DOORBELLS_PER_SQIDI ) +1 ; +ads_blob_write (guc, + system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_DOORBELL_COUNT_PER_SQIDI ], + ((distdbreg >>GEN12_DOORBELLS_PER_SQIDI_SHIFT ) + &GEN12_DOORBELLS_PER_SQIDI ) +1 ); }/* Golden contexts for re-initialising after a watchdog reset */
@@ -637,14 +637,17 @@ static void __guc_ads_init(struct intel_guc *guc)guc_capture_list_init (guc);/* ADS */ - blob->ads.scheduler_policies = base +ptr_offset (blob, policies); - blob->ads.gt_system_info = base +ptr_offset (blob, system_info); +ads_blob_write (guc, ads.scheduler_policies, base + + offsetof(struct __guc_ads_blob , policies)); +ads_blob_write (guc, ads.gt_system_info, base + + offsetof(struct __guc_ads_blob , system_info));/* MMIO save/restore list */ guc_mmio_reg_state_init (guc);/* Private Data */ - blob->ads.private_data = base +guc_ads_private_data_offset (guc); +ads_blob_write (guc, ads.private_data, base + +guc_ads_private_data_offset (guc));i915_gem_object_flush_map (guc->ads_vma->obj); }
Signature · 1 line
2.35.0
PATCH 19/19 drm/i915/guc: Remove plain ads_blob pointer
In reply to Lucas De MarchiNow we have the access to content of GuC ADS either using dma_buf_map API or using a temporary buffer. Remove guc->ads_blob as there shouldn't be updates using the bare pointer anymore.
--- drivers/gpu/drm/i915/gt/uc/intel_guc.h | 3 +-- drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 8 ++++---- 2 files changed, 5 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc.h +1 -2
@@ -147,8 +147,7 @@ struct intel_guc {/** @ads_vma: object allocated to hold the GuC ADS */ struct i915_vma *ads_vma; -/** @ads_blob: contents of the GuC ADS */ -struct __guc_ads_blob *ads_blob; +/** @ads_map: contents of the GuC ADS */ struct dma_buf_map ads_map;/** @ads_regset_size: size of the save/restore regsets in the ADS */ u32 ads_regset_size;
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c +4 -4
@@ -661,6 +661,7 @@ static void __guc_ads_init(struct intel_guc *guc)*/ int intel_guc_ads_create (struct intel_guc *guc) { +void *ads_blob;u32 size;int ret;
@@ -685,14 +686,14 @@ int intel_guc_ads_create(struct intel_guc *guc) size =guc_ads_blob_size (guc); ret =intel_guc_allocate_and_map_vma (guc, size, &guc->ads_vma, - (void **)&guc->ads_blob); + &ads_blob);if (ret)return ret;if (i915_gem_object_is_lmem (guc->ads_vma->obj)) -dma_buf_map_set_vaddr_iomem (&guc->ads_map, (void __iomem *)guc->ads_blob); +dma_buf_map_set_vaddr_iomem (&guc->ads_map, (void __iomem *)ads_blob);else -dma_buf_map_set_vaddr (&guc->ads_map, guc->ads_blob); +dma_buf_map_set_vaddr (&guc->ads_map, ads_blob);__guc_ads_init (guc);
@@ -714,7 +715,6 @@ void intel_guc_ads_init_late(struct intel_guc *guc)void intel_guc_ads_destroy (struct intel_guc *guc) {i915_vma_unpin_and_release (&guc->ads_vma,I915_VMA_RELEASE_MAP ); - guc->ads_blob =NULL ;dma_buf_map_clear (&guc->ads_map);kfree (guc->ads_regset); }
Signature · 1 line
2.35.0
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Refactor ADS access to use dma_buf_map
In reply to Lucas De Marchi== Series Details ==
== Series Details ==
Series: drm/i915/guc: Refactor ADS access to use dma_buf_map
URL : https://patchwork.freedesktop.org/series/99378/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
65454816ee9c dma-buf-map: Add read/write helpers
-:105: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'type__' may be better as '(type__)' to avoid precedence issues
#105: FILE: include/linux/dma-buf-map.h:319:
+#define dma_buf_map_read_field(map__, type__, field__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val__; \
+ dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \
+ sizeof(t__->field__)); \
+ val__; \
+})-:105: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'field__' - possible side-effects? #105: FILE: include/linux/dma-buf-map.h:319:
+#define dma_buf_map_read_field(map__, type__, field__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val__; \
+ dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \
+ sizeof(t__->field__)); \
+ val__; \
+})
-:105: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'field__' may be better as '(field__)' to avoid precedence issues #105: FILE: include/linux/dma-buf-map.h:319:
+#define dma_buf_map_read_field(map__, type__, field__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val__; \
+ dma_buf_map_memcpy_from_offset(&val__, map__, offsetof(type__, field__), \
+ sizeof(t__->field__)); \
+ val__; \
+})
-:126: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'type__' may be better as '(type__)' to avoid precedence issues #126: FILE: include/linux/dma-buf-map.h:340:
+#define dma_buf_map_write_field(map__, type__, field__, val__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val____ = val__; \
+ dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \
+ &val____, sizeof(t__->field__)); \
+})
-:126: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'field__' - possible side-effects? #126: FILE: include/linux/dma-buf-map.h:340:
+#define dma_buf_map_write_field(map__, type__, field__, val__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val____ = val__; \
+ dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \
+ &val____, sizeof(t__->field__)); \
+})
-:126: CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'field__' may be better as '(field__)' to avoid precedence issues #126: FILE: include/linux/dma-buf-map.h:340:
+#define dma_buf_map_write_field(map__, type__, field__, val__) ({ \
+ type__ *t__; \
+ typeof(t__->field__) val____ = val__; \
+ dma_buf_map_memcpy_to_offset(map__, offsetof(type__, field__), \
+ &val____, sizeof(t__->field__)); \
+})
total: 0 errors, 0 warnings, 6 checks, 97 lines checked3e1d98022b1e dma-buf-map: Add helper to initialize second map
-:55: ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses #55: FILE: include/linux/dma-buf-map.h:157:
+#define DMA_BUF_MAP_INIT_OFFSET(map_, offset_) (struct dma_buf_map) \
+ { \
+ .vaddr = (map_)->vaddr + (offset_), \
+ .is_iomem = (map_)->is_iomem, \
+ }
-:55: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'map_' - possible side-effects? #55: FILE: include/linux/dma-buf-map.h:157:
+#define DMA_BUF_MAP_INIT_OFFSET(map_, offset_) (struct dma_buf_map) \
+ { \
+ .vaddr = (map_)->vaddr + (offset_), \
+ .is_iomem = (map_)->is_iomem, \
+ }
total: 1 errors, 0 warnings, 1 checks, 35 lines checked 2d41494bd5b1 drm/i915/gt: Add helper for shmem copy to dma_buf_map 99e46a0dde3e drm/i915/guc: Keep dma_buf_map of ads_blob around 85b2d92083f4 drm/i915/guc: Add read/write helpers for ADS blob 7be0be3302b4 drm/i915/guc: Convert golden context init to dma_buf_map f6c5dcbe95f6 drm/i915/guc: Convert policies update to dma_buf_map 5100676b5102 drm/i915/guc: Convert engine record to dma_buf_map 2231431579a3 dma-buf-map: Add wrapper over memseta69351212152 drm/i915/guc: Convert guc_ads_private_data_reset to dma_buf_map 04d2c4cf7a69 drm/i915/guc: Convert golden context prep to dma_buf_map 824e76096416 drm/i915/guc: Replace check for golden context size 1df5683fe05f drm/i915/guc: Convert mapping table to dma_buf_map 1f7b57620e07 drm/i915/guc: Convert capture list to dma_buf_map a3cbf5b2fd0b drm/i915/guc: Prepare for error propagation f6a9b1574461 drm/i915/guc: Use a single pass to calculate regset dbd1faca50e7 drm/i915/guc: Convert guc_mmio_reg_state_init to dma_buf_map 5e92c399bbf6 drm/i915/guc: Convert __guc_ads_init to dma_buf_map -:42: WARNING:LONG_LINE: line length of 106 exceeds 100 columns #42: FILE: drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:617:
+ ads_blob_write(guc, system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_VDBOX_SFC_SUPPORT_MASK],
-:52: WARNING:LONG_LINE: line length of 111 exceeds 100 columns #52: FILE: drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:624:
+ system_info.generic_gt_sysinfo[GUC_GENERIC_GT_SYSINFO_DOORBELL_COUNT_PER_SQIDI],
total: 0 errors, 2 warnings, 0 checks, 52 lines checked 2788e054f9ce drm/i915/guc: Remove plain ads_blob pointer
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Refactor ADS access to use dma_buf_map
In reply to Lucas De Marchi== Series Details ==
== Series Details ==
Series: drm/i915/guc: Refactor ADS access to use dma_buf_map
URL : https://patchwork.freedesktop.org/series/99378/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Refactor ADS access to use dma_buf_map
In reply to Lucas De Marchi== Series Details ==
== Series Details ==
Series: drm/i915/guc: Refactor ADS access to use dma_buf_map
URL : https://patchwork.freedesktop.org/series/99378/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11147 -> Patchwork_22116
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/index.html
Participating hosts (48 -> 31)
------------------------------
Missing (17): fi-kbl-soraka fi-bxt-dsi fi-bdw-5557u fi-bsw-n3050 fi-hsw-4200u fi-glk-dsi fi-icl-u2 fi-bsw-cyan fi-apl-guc fi-snb-2520m fi-ctg-p8600 fi-kbl-x1275 fi-kbl-8809g fi-elk-e7500 fi-bsw-kefka fi-bsw-nick fi-bdw-samus
Known issues
------------
Here are the changes found in Patchwork_22116 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@sync-fork-compute0:
- fi-snb-2600: NOTRUN -> [SKIP][1] ([fdo#109271]) +17 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-snb-2600/igt@amdgpu/[email protected]
* igt@gem_exec_suspend@basic-s3@smem:
- fi-skl-6600u: NOTRUN -> [INCOMPLETE][2] ([i915#4547])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-skl-6600u/igt@gem_exec_suspend@[email protected]
* igt@runner@aborted:
- fi-pnv-d510: NOTRUN -> [FAIL][3] ([i915#2403] / [i915#4312])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-pnv-d510/igt@[email protected]
- fi-skl-6600u: NOTRUN -> [FAIL][4] ([i915#4312])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-skl-6600u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@gt_pm:
- {fi-jsl-1}: [DMESG-FAIL][5] ([i915#1886]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/fi-jsl-1/igt@i915_selftest@live@gt_pm.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-jsl-1/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@hangcheck:
- bat-dg1-6: [DMESG-FAIL][7] ([i915#4494] / [i915#4957]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/bat-dg1-6/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/bat-dg1-6/igt@i915_selftest@[email protected]
- fi-snb-2600: [INCOMPLETE][9] ([i915#3921]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/fi-snb-2600/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/fi-snb-2600/igt@i915_selftest@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#3194]: https://gitlab.freedesktop.org/drm/intel/issues/3194
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4547]: https://gitlab.freedesktop.org/drm/intel/issues/4547
[i915#4898]: https://gitlab.freedesktop.org/drm/intel/issues/4898
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
Build changes
-------------
* Linux: CI_DRM_11147 -> Patchwork_22116
CI-20190529: 20190529
CI_DRM_11147: ad57bf1ff13e1c4462f947398fbfb861f1b2e345 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6335: 2b30115edd692b60d16cb10375730a87f51f0e37 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22116: 2788e054f9ce2eff704b9c331c3881bf035ee68f @ git://anongit.freedesktop.org/gfx-ci/linux
== Kernel 32bit build ==
Warning: Kernel 32bit buildtest failed:
https://intel-gfx-ci.01.org/Patchwork_22116/build_32bit.log
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o
In file included from ./include/drm/drm_mm.h:51,
from ./drivers/gpu/drm/i915/i915_vma.h:31,
from ./drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h:13,
from ./drivers/gpu/drm/i915/gt/uc/intel_guc.h:20,
from ./drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from ./drivers/gpu/drm/i915/gt/intel_gt_types.h:18,
from ./drivers/gpu/drm/i915/gt/intel_gt.h:10,
from drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:9:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c: In function ‘guc_mmio_reg_state_create’:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:38: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘u32’ {aka ‘unsigned int’} [-Werror=format=]
drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~./include/drm/drm_print.h:461:56: note: in definition of macro ‘drm_dbg’
drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
^~~
cc1: all warnings being treated as errorsscripts/Makefile.build:288: recipe for target 'drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o' failed make[4]: *** [drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o] Error 1 scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm/i915' failed make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:550: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1831: recipe for target 'drivers' failed
make: *** [drivers] Error 2
== Linux commits ==
2788e054f9ce drm/i915/guc: Remove plain ads_blob pointer 5e92c399bbf6 drm/i915/guc: Convert __guc_ads_init to dma_buf_map dbd1faca50e7 drm/i915/guc: Convert guc_mmio_reg_state_init to dma_buf_map f6a9b1574461 drm/i915/guc: Use a single pass to calculate regset a3cbf5b2fd0b drm/i915/guc: Prepare for error propagation 1f7b57620e07 drm/i915/guc: Convert capture list to dma_buf_map 1df5683fe05f drm/i915/guc: Convert mapping table to dma_buf_map 824e76096416 drm/i915/guc: Replace check for golden context size 04d2c4cf7a69 drm/i915/guc: Convert golden context prep to dma_buf_map a69351212152 drm/i915/guc: Convert guc_ads_private_data_reset to dma_buf_map 2231431579a3 dma-buf-map: Add wrapper over memset5100676b5102 drm/i915/guc: Convert engine record to dma_buf_map f6c5dcbe95f6 drm/i915/guc: Convert policies update to dma_buf_map 7be0be3302b4 drm/i915/guc: Convert golden context init to dma_buf_map 85b2d92083f4 drm/i915/guc: Add read/write helpers for ADS blob 99e46a0dde3e drm/i915/guc: Keep dma_buf_map of ads_blob around 2d41494bd5b1 drm/i915/gt: Add helper for shmem copy to dma_buf_map 3e1d98022b1e dma-buf-map: Add helper to initialize second map 65454816ee9c dma-buf-map: Add read/write helpers
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: warning for drm/i915/guc: Refactor ADS access to use dma_buf_map
In reply to Lucas De Marchi== Series Details ==
== Series Details ==
Series: drm/i915/guc: Refactor ADS access to use dma_buf_map
URL : https://patchwork.freedesktop.org/series/99378/
State : warning
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o
In file included from ./include/drm/drm_mm.h:51,
from ./drivers/gpu/drm/i915/i915_vma.h:31,
from ./drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h:13,
from ./drivers/gpu/drm/i915/gt/uc/intel_guc.h:20,
from ./drivers/gpu/drm/i915/gt/uc/intel_uc.h:9,
from ./drivers/gpu/drm/i915/gt/intel_gt_types.h:18,
from ./drivers/gpu/drm/i915/gt/intel_gt.h:10,
from drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:9:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c: In function ‘guc_mmio_reg_state_create’:
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:369:38: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘u32’ {aka ‘unsigned int’} [-Werror=format=]
drm_dbg(&guc_to_gt(guc)->i915->drm, "Used %lu KB for temporary ADS regset\n",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (temp_set.storage_max * sizeof(struct guc_mmio_reg)) >> 10);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~./include/drm/drm_print.h:461:56: note: in definition of macro ‘drm_dbg’
drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_DRIVER, fmt, ##__VA_ARGS__)
^~~
cc1: all warnings being treated as errorsscripts/Makefile.build:288: recipe for target 'drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o' failed make[4]: *** [drivers/gpu/drm/i915/gt/uc/intel_guc_ads.o] Error 1 scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm/i915' failed make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:550: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1831: recipe for target 'drivers' failed
make: *** [drivers] Error 2
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/build_32bit.log
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Refactor ADS access to use dma_buf_map
In reply to Lucas De Marchi== Series Details ==
== Series Details ==
Series: drm/i915/guc: Refactor ADS access to use dma_buf_map
URL : https://patchwork.freedesktop.org/series/99378/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11147_full -> Patchwork_22116_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_22116_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_22116_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22116_full:
### IGT changes ###
#### Possible regressions ####
* igt@i915_pm_rpm@modeset-lpsp-stress:
- shard-iclb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb7/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb4/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_22116_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@legacy-engines-queued:
- shard-snb: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1099])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb6/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][4] -> [TIMEOUT][5] ([i915#2481] / [i915#3070])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb2/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-tglb: NOTRUN -> [FAIL][6] ([i915#2842]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2842])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl6/igt@gem_exec_fair@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_suspend@basic-s3@smem:
- shard-apl: [PASS][9] -> [DMESG-WARN][10] ([i915#180]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-apl2/igt@gem_exec_suspend@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl3/igt@gem_exec_suspend@[email protected]
* igt@gem_exec_whisper@basic-fds-forked-all:
- shard-glk: [PASS][11] -> [DMESG-WARN][12] ([i915#118])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-glk1/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk4/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- shard-kbl: NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#4613])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl6/igt@[email protected]
* igt@gem_lmem_swapping@heavy-random:
- shard-glk: NOTRUN -> [SKIP][14] ([fdo#109271] / [i915#4613])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@[email protected]
* igt@gem_lmem_swapping@parallel-multi:
- shard-tglb: NOTRUN -> [SKIP][15] ([i915#4613])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@gem_pwrite@basic-exhaustion:
- shard-snb: NOTRUN -> [WARN][16] ([i915#2658])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb6/igt@[email protected]
* igt@gem_pxp@create-regular-context-1:
- shard-tglb: NOTRUN -> [SKIP][17] ([i915#4270]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@gem_pxp@verify-pxp-execution-after-suspend-resume:
- shard-iclb: NOTRUN -> [SKIP][18] ([i915#4270])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@gem_softpin@allocator-evict-all-engines:
- shard-glk: [PASS][19] -> [FAIL][20] ([i915#4171])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-glk5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk7/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][21] -> [DMESG-WARN][22] ([i915#1436] / [i915#716])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-skl8/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl6/igt@[email protected]
* igt@gen9_exec_parse@bb-large:
- shard-iclb: NOTRUN -> [SKIP][23] ([i915#2856])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@gen9_exec_parse@secure-batches:
- shard-tglb: NOTRUN -> [SKIP][24] ([i915#2527] / [i915#2856])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-tglb: NOTRUN -> [SKIP][25] ([fdo#109506] / [i915#2411])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][26] ([i915#1886] / [i915#2291])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl5/igt@i915_selftest@live@gt_pm.html
* igt@kms_async_flips@crc:
- shard-skl: NOTRUN -> [FAIL][27] ([i915#4272])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl7/igt@[email protected]
* igt@kms_atomic@plane-primary-overlay-mutable-zpos:
- shard-tglb: NOTRUN -> [SKIP][28] ([i915#404])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][29] ([fdo#111614]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [SKIP][30] ([fdo#109271]) +122 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl1/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_big_fb@yf-tiled-64bpp-rotate-180:
- shard-tglb: NOTRUN -> [SKIP][31] ([fdo#111615]) +2 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@yf-tiled-8bpp-rotate-0:
- shard-iclb: NOTRUN -> [SKIP][32] ([fdo#110723])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][33] ([fdo#109271] / [i915#3886]) +3 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl2/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#3886]) +7 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl7/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
- shard-tglb: NOTRUN -> [SKIP][35] ([i915#3689] / [i915#3886]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb3/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#3886]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][37] ([fdo#109278] / [i915#3886])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#3886]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl6/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][39] ([i915#3689]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb3/igt@kms_ccs@pipe-d-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-random-ccs-data-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][40] ([fdo#111615] / [i915#3689]) +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@kms_ccs@pipe-d-random-ccs-data-yf_tiled_ccs.html
* igt@kms_chamelium@vga-hpd-after-suspend:
- shard-skl: NOTRUN -> [SKIP][41] ([fdo#109271] / [fdo#111827]) +10 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl1/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-green-to-red:
- shard-glk: NOTRUN -> [SKIP][42] ([fdo#109271] / [fdo#111827]) +2 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@[email protected]
* igt@kms_color_chamelium@pipe-b-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +4 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl2/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl6/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-snb: NOTRUN -> [SKIP][45] ([fdo#109271] / [fdo#111827]) +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb6/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-ctm-0-75:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-ctm-red-to-blue:
- shard-tglb: NOTRUN -> [SKIP][47] ([fdo#109284] / [fdo#111827]) +7 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][48] ([i915#1319]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl2/igt@[email protected]
* igt@kms_content_protection@uevent:
- shard-tglb: NOTRUN -> [SKIP][49] ([i915#1063])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-512x170-onscreen:
- shard-tglb: NOTRUN -> [SKIP][50] ([fdo#109279] / [i915#3359]) +1 similar issue
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-32x32-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][51] ([i915#3319])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-32x10-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#3359]) +3 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-32x32-sliding:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109278]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-skl: NOTRUN -> [FAIL][54] ([i915#2346])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl5/igt@[email protected]
* igt@kms_dsc@xrgb8888-dsc-compression:
- shard-apl: NOTRUN -> [SKIP][55] ([fdo#109271]) +26 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl2/igt@[email protected]
* igt@kms_flip@2x-plain-flip-ts-check:
- shard-tglb: NOTRUN -> [SKIP][56] ([fdo#109274] / [fdo#111825]) +3 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-skl: [PASS][57] -> [INCOMPLETE][58] ([i915#4839])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-skl10/igt@kms_flip@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl8/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling:
- shard-glk: NOTRUN -> [FAIL][59] ([i915#4911])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-snb: [PASS][60] -> [SKIP][61] ([fdo#109271]) +2 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-snb5/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb5/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite:
- shard-snb: NOTRUN -> [SKIP][62] ([fdo#109271]) +34 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen:
- shard-tglb: NOTRUN -> [SKIP][63] ([fdo#109280] / [fdo#111825]) +10 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-fullscreen.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109280]) +2 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt:
- shard-kbl: NOTRUN -> [SKIP][65] ([fdo#109271]) +31 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl6/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][66] -> [DMESG-WARN][67] ([i915#180]) +8 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl4/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
* igt@kms_hdr@static-toggle-suspend:
- shard-tglb: NOTRUN -> [SKIP][68] ([i915#1187])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c:
- shard-glk: NOTRUN -> [SKIP][69] ([fdo#109271]) +38 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@[email protected]
* igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes:
- shard-tglb: NOTRUN -> [SKIP][70] ([fdo#109289])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: NOTRUN -> [FAIL][71] ([fdo#108145] / [i915#265]) +2 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][72] ([i915#265])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl2/igt@[email protected]
- shard-skl: NOTRUN -> [FAIL][73] ([i915#265])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl9/igt@[email protected]
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-tglb: NOTRUN -> [SKIP][74] ([i915#2920])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-skl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#658]) +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl5/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][76] -> [SKIP][77] ([fdo#109441]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb8/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_psr@psr2_suspend:
- shard-tglb: NOTRUN -> [FAIL][78] ([i915#132] / [i915#3467])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@kms_psr@psr2_suspend.html
* igt@kms_sysfs_edid_timing:
- shard-skl: NOTRUN -> [FAIL][79] ([IGT#2])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl9/igt@kms_sysfs_edid_timing.html
* igt@kms_writeback@writeback-fb-id:
- shard-glk: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#2437])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@[email protected]
* igt@nouveau_crc@pipe-a-ctx-flip-skip-current-frame:
- shard-tglb: NOTRUN -> [SKIP][81] ([i915#2530])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@[email protected]
* igt@prime_nv_api@i915_nv_import_twice:
- shard-tglb: NOTRUN -> [SKIP][82] ([fdo#109291])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@prime_nv_api@i915_nv_import_twice.html
* igt@sysfs_clients@busy:
- shard-skl: NOTRUN -> [SKIP][83] ([fdo#109271] / [i915#2994]) +2 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl5/igt@[email protected]
* igt@sysfs_clients@fair-7:
- shard-glk: NOTRUN -> [SKIP][84] ([fdo#109271] / [i915#2994])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk8/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_balancer@parallel-contexts:
- shard-iclb: [SKIP][85] ([i915#4525]) -> [PASS][86] +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb3/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb2/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][87] ([i915#2842]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-tglb5/igt@gem_exec_fair@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][89] ([i915#2842]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-apl4/igt@gem_exec_fair@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [FAIL][91] ([i915#2842]) -> [PASS][92] +2 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl6/igt@gem_exec_fair@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][93] ([i915#2849]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb5/igt@gem_exec_fair@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb5/igt@gem_exec_fair@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][95] ([i915#454]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb6/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb1/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- shard-snb: [INCOMPLETE][97] ([i915#3921]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-snb6/igt@i915_selftest@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-snb6/igt@i915_selftest@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-skl: [INCOMPLETE][99] ([i915#4939]) -> [PASS][100] +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-skl7/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl1/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a1:
- shard-glk: [FAIL][101] ([i915#79]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-glk8/igt@kms_flip@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: [DMESG-WARN][103] ([i915#180]) -> [PASS][104] +4 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-apl6/igt@kms_flip@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-apl8/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
- shard-iclb: [SKIP][105] ([i915#3701]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [FAIL][107] ([i915#1188]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-skl7/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl1/igt@[email protected]
* igt@kms_setmode@basic:
- shard-glk: [FAIL][109] ([i915#31]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-glk1/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-glk4/igt@[email protected]
* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-kbl: [DMESG-WARN][111] ([i915#180]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl4/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl6/igt@[email protected]
#### Warnings ####
* igt@gem_eio@unwedge-stress:
- shard-tglb: [TIMEOUT][113] ([i915#3063] / [i915#3648]) -> [FAIL][114] ([i915#232])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-tglb6/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-tglb5/igt@[email protected]
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [SKIP][115] ([i915#4525]) -> [FAIL][116] ([i915#4916])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb8/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb1/igt@[email protected]
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][117] ([i915#658]) -> [SKIP][118] ([i915#588])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb3/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb2/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [FAIL][119] ([i915#2680]) -> [WARN][120] ([i915#1804] / [i915#2684])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb1/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb3/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-32x10-offscreen:
- shard-skl: [INCOMPLETE][121] -> [SKIP][122] ([fdo#109271])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-skl9/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-skl7/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-iclb: [SKIP][123] ([i915#2920]) -> [SKIP][124] ([fdo#111068] / [i915#658])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb2/igt@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb1/igt@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: [SKIP][125] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [FAIL][126] ([i915#4148])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-iclb5/igt@kms_psr2_su@page_flip-xrgb8888.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-iclb2/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][127], [FAIL][128], [FAIL][129], [FAIL][130], [FAIL][131]) ([fdo#109271] / [i915#1436] / [i915#1814] / [i915#3002] / [i915#4312] / [i915#602] / [i915#716]) -> ([FAIL][132], [FAIL][133], [FAIL][134], [FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#4312] / [i915#716])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl4/igt@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl7/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl4/igt@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl4/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11147/shard-kbl3/igt@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl3/igt@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@[email protected]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/shard-kbl4/igt@run
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22116/index.html