Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/uapi: Document DRM_I915_QUERY_HWCONFIG_BLOB
Date: Fri, 25 Mar 2022 10:56:01 +0000	[thread overview]
Message-ID: <aad940f2-c064-a623-6c15-27171d268476@linux.intel.com> (raw)
In-Reply-To: <Yj2RMTTkQxC/vzre@phenom.ffwll.local>


On 25/03/2022 09:53, Daniel Vetter wrote:
> On Fri, Mar 25, 2022 at 09:49:16AM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> UAPI with absolutely no documentation should not have been added -
>> clarify blob format and content will be described externally.
>>
>> Fixes: 78e1fb3112c0 ("drm/i915/uapi: Add query for hwconfig blob")
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Co-developed-by: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Jon Bloomfield <jon.bloomfield@intel.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: John Harrison <john.c.harrison@intel.com>
>> Cc: Jon Ewins <jon.ewins@intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> ---
>>   include/uapi/drm/i915_drm.h | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>
>> diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
>> index 071ffd9d51f1..8d0719bee8fc 100644
>> --- a/include/uapi/drm/i915_drm.h
>> +++ b/include/uapi/drm/i915_drm.h
>> @@ -2683,6 +2683,9 @@ struct drm_i915_perf_oa_config {
>>    *
>>    * The behaviour is determined by the @query_id. Note that exactly what
>>    * @data_ptr is also depends on the specific @query_id.
>> + *
>> + * For specific queries see:
>> + *  * `GuC HWCONFIG blob uAPI`_
> 
> I'd put this into the @query_id section, and then make it an item list
> with the #define as the label, so that it becomes tidy and can neatly
> iterate them all.
> 
> Anyway we can bikeshed this all more in a follow-up.
> 
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Thanks, yes I wanted to do the minimal thing to close the gap.
>>    */
>>   struct drm_i915_query_item {
>>   	/** @query_id: The id for this query */
>> @@ -3135,6 +3138,16 @@ struct drm_i915_query_memory_regions {
>>   	struct drm_i915_memory_region_info regions[];
>>   };
>>   
>> +/**
>> + * DOC: GuC HWCONFIG blob uAPI
>> + *
>> + * The GuC produces a blob with information about the current device.
>> + * i915 reads this blob from GuC and makes it available via this uAPI.
>> + *
>> + * The format and meading of the blob content are documented in the

Meading? I will fix that up while merging.

Regards,

Tvrtko

>> + * Programmer's Reference Manual.
>> + */
>> +
>>   /**
>>    * struct drm_i915_gem_create_ext - Existing gem_create behaviour, with added
>>    * extension support using struct i915_user_extension.
>> -- 
>> 2.32.0
>>
> 

  reply	other threads:[~2022-03-25 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  9:49 [Intel-gfx] [PATCH] drm/i915/uapi: Document DRM_I915_QUERY_HWCONFIG_BLOB Tvrtko Ursulin
2022-03-25  9:53 ` Daniel Vetter
2022-03-25 10:56   ` Tvrtko Ursulin [this message]
2022-03-25 10:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-25 10:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-25 10:14 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-25 10:36 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-03-25 11:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/uapi: Document DRM_I915_QUERY_HWCONFIG_BLOB (rev2) Patchwork
2022-03-25 11:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-25 11:44 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-25 12:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aad940f2-c064-a623-6c15-27171d268476@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox