search for: bo_offset

...and the resulting mappings as implemented + * by drm_gpuva_sm_map() - it doesn't cover any arbitrary combinations of these. + * + * 1) Requested mapping is identical. Replace it, but indicate the backing PTEs + * could be kept. + * + * :: + * + * 0 a 1 + * old: |-----------| (bo_offset=n) + * + * 0 a 1 + * req: |-----------| (bo_offset=n) + * + * 0 a 1 + * new: |-----------| (bo_offset=n) + * + * + * 2) Requested mapping is identical, except for the BO offset, hence replace + * the mapping. + * + * :: + * + * 0 a 1 + * old: |----------...

...and the resulting mappings as implemented + * by drm_gpuva_sm_map() - it doesn't cover any arbitrary combinations of these. + * + * 1) Requested mapping is identical. Replace it, but indicate the backing PTEs + * could be kept. + * + * :: + * + * 0 a 1 + * old: |-----------| (bo_offset=n) + * + * 0 a 1 + * req: |-----------| (bo_offset=n) + * + * 0 a 1 + * new: |-----------| (bo_offset=n) + * + * + * 2) Requested mapping is identical, except for the BO offset, hence replace + * the mapping. + * + * :: + * + * 0 a 1 + * old: |----------...

...and the resulting mappings as implemented + * by drm_gpuva_sm_map() - it doesn't cover any arbitrary combinations of these. + * + * 1) Requested mapping is identical. Replace it, but indicate the backing PTEs + * could be kept. + * + * :: + * + * 0 a 1 + * old: |-----------| (bo_offset=n) + * + * 0 a 1 + * req: |-----------| (bo_offset=n) + * + * 0 a 1 + * new: |-----------| (bo_offset=n) + * + * + * 2) Requested mapping is identical, except for the BO offset, hence replace + * the mapping. + * + * :: + * + * 0 a 1 + * old: |----------...

...directly >>>>>> execute this operation within the callback. >>>>>> >>>>>> Let's have a look at the following example: >>>>>> >>>>>> 0 a 2 >>>>>> old: |-----------| (bo_offset=n) >>>>>> >>>>>> 1 b 3 >>>>>> req: |-----------| (bo_offset=m) >>>>>> >>>>>> 0 a' 1 b 3 >>>>>> new: |-----|-----------| (a.bo_offset=n,b.bo_of...

...s can also implement the callback, such that they directly >>>> execute this operation within the callback. >>>> >>>> Let's have a look at the following example: >>>> >>>> 0 a 2 >>>> old: |-----------| (bo_offset=n) >>>> >>>> 1 b 3 >>>> req: |-----------| (bo_offset=m) >>>> >>>> 0 a' 1 b 3 >>>> new: |-----|-----------| (a.bo_offset=n,b.bo_offset=m) >>>> >>>> This wou...

...s it in a list. >> >> However, drivers can also implement the callback, such that they directly >> execute this operation within the callback. >> >> Let's have a look at the following example: >> >> 0 a 2 >> old: |-----------| (bo_offset=n) >> >> 1 b 3 >> req: |-----------| (bo_offset=m) >> >> 0 a' 1 b 3 >> new: |-----|-----------| (a.bo_offset=n,b.bo_offset=m) >> >> This would result in the following operations. >> >> __drm_gpu...

...??? __u32 op; >> #define DRM_NOUVEAU_VM_BIND_OP_MAP 0x0; >> #define DRM_NOUVEAU_VM_BIND_OP_UNMAP 0x1; >> ???? __u32 flags; >> #define DRM_NOUVEAU_VM_BIND_SPARSE (1 << 8); >> ???? __u32 handle; >> ???? __u32 pad; >> ???? __u64 addr; >> ???? __u64 bo_offset; >> ???? __u64 range; >> }; > > Do we actually ever want preprocessor directives to appear inside > definitions in the output? If not, I think this should work: Not necessarily. > diff --git a/scripts/kernel-doc b/scripts/kernel-doc > index 3cdc7dba37e3..61425fc9645e 1...

...@handle: the handle of the DRM GEM object to map >> + */ >> + __u32 handle; >> + /** >> + * @addr: >> + * >> + * the address the VA space region or (memory backed) mapping should be mapped to >> + */ >> + __u64 addr; >> + /** >> + * @bo_offset: the offset within the BO backing the mapping >> + */ >> + __u64 bo_offset; >> + /** >> + * @range: the size of the requested mapping in bytes >> + */ >> + __u64 range; >> +}; >> + >> +/** >> + * struct drm_nouveau_vm_bind - structure f...

...+??? __u32 handle; >>> +??? /** >>> +???? * @addr: >>> +???? * >>> +???? * the address the VA space region or (memory backed) mapping >>> should be mapped to >>> +???? */ >>> +??? __u64 addr; >>> +??? /** >>> +???? * @bo_offset: the offset within the BO backing the mapping >>> +???? */ >>> +??? __u64 bo_offset; >>> +??? /** >>> +???? * @range: the size of the requested mapping in bytes >>> +???? */ >>> +??? __u64 range; >>> +}; >>> + >>> +/**...

...*/ > +? ? ? ?__u32 pad; > +? ? ? ?/** > +? ? ? ? * @addr: > +? ? ? ? * > +? ? ? ? * the address the VA space region or (memory backed) > mapping should be mapped to > +? ? ? ? */ > +? ? ? ?__u64 addr; > +? ? ? ?/** > +? ? ? ? * @bo_offset: the offset within the BO backing the mapping > +? ? ? ? */ > +? ? ? ?__u64 bo_offset; > +? ? ? ?/** > +? ? ? ? * @range: the size of the requested mapping in bytes > +? ? ? ? */ > +? ? ? ?__u64 range; > +}; > + > +/** > + * stru...

...>> + __u32 handle; >>>> + /** >>>> + * @addr: >>>> + * >>>> + * the address the VA space region or (memory backed) mapping should be mapped to >>>> + */ >>>> + __u64 addr; >>>> + /** >>>> + * @bo_offset: the offset within the BO backing the mapping >>>> + */ >>>> + __u64 bo_offset; >>>> + /** >>>> + * @range: the size of the requested mapping in bytes >>>> + */ >>>> + __u64 range; >>>> +}; >>>> + &gt...

...have a ';' at the end of each line: struct drm_nouveau_vm_bind_op { __u32 op; #define DRM_NOUVEAU_VM_BIND_OP_MAP 0x0; #define DRM_NOUVEAU_VM_BIND_OP_UNMAP 0x1; __u32 flags; #define DRM_NOUVEAU_VM_BIND_SPARSE (1 << 8); __u32 handle; __u32 pad; __u64 addr; __u64 bo_offset; __u64 range; }; so something else to look into one of these days.... > --- > include/uapi/drm/nouveau_drm.h | 56 ++++++++++++++++------------------ > 1 file changed, 27 insertions(+), 29 deletions(-) > > diff --git a/include/uapi/drm/nouveau_drm.h b/include/uapi/drm/nouvea...

As of commit b77fdd6a48e6 ("scripts/kernel-doc: restore warning for Excess struct/union"), we see the following warnings when running 'make htmldocs': ./include/uapi/drm/nouveau_drm.h:292: warning: Excess struct member 'DRM_NOUVEAU_VM_BIND_OP_MAP' description in 'drm_nouveau_vm_bind_op' ./include/uapi/drm/nouveau_drm.h:292: warning: Excess struct member