public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-GFX@lists.freedesktop.org, DRI-Devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] Add support for querying hw info that UMDs need
Date: Tue, 27 Jul 2021 11:46:45 -0700	[thread overview]
Message-ID: <01479f2d-78be-fdf0-d3ef-c0de92e9a769@intel.com> (raw)
In-Reply-To: <YP/WudLoHxIx/h1B@phenom.ffwll.local>

On 7/27/2021 02:49, Daniel Vetter wrote:
> On Mon, Jul 26, 2021 at 07:21:43PM -0700, John.C.Harrison@Intel.com wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> Various UMDs require hardware configuration information about the
>> current platform. A bunch of static information is available in a
>> fixed table that can be retrieved from the GuC.
>>
>> Test-with: 20210727002812.43469-2-John.C.Harrison@Intel.com
>> UMD: https://github.com/intel/compute-runtime/pull/432/files
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> Can you pls submit this with all the usual suspect from the umd side (so
> also media-driver and mesa) cced?
Do you have a list of names that you would like included?

>
> Also do the mesa/media-driver patches exist somewhere? Afaiui this isn't
> very useful without those bits in place too.
I don't know about mesa but the media team have the support in place in 
their internal tree and (as per compute) are waiting for us to push the 
kernel side. This also comes under the headings of both new platforms 
and platforms which are POR for GuC submission. So I believe a lot of 
the UMD side changes for the config table are wrapped up in their 
support for the new platforms/GuC as a whole and thus not yet ready for 
upstream.

John.


> -Daniel
>
>>
>> John Harrison (1):
>>    drm/i915/guc: Add fetch of hwconfig table
>>
>> Rodrigo Vivi (1):
>>    drm/i915/uapi: Add query for hwconfig table
>>
>>   drivers/gpu/drm/i915/Makefile                 |   1 +
>>   .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h  |   1 +
>>   .../gpu/drm/i915/gt/uc/abi/guc_errors_abi.h   |   4 +
>>   drivers/gpu/drm/i915/gt/uc/intel_guc.c        |   3 +-
>>   drivers/gpu/drm/i915/gt/uc/intel_guc.h        |   2 +
>>   .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.c   | 156 ++++++++++++++++++
>>   .../gpu/drm/i915/gt/uc/intel_guc_hwconfig.h   |  19 +++
>>   drivers/gpu/drm/i915/gt/uc/intel_uc.c         |   6 +
>>   drivers/gpu/drm/i915/i915_query.c             |  23 +++
>>   include/uapi/drm/i915_drm.h                   |   1 +
>>   10 files changed, 215 insertions(+), 1 deletion(-)
>>   create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
>>   create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.h
>>
>> -- 
>> 2.25.1
>>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-07-27 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  2:21 [Intel-gfx] [PATCH 0/2] Add support for querying hw info that UMDs need John.C.Harrison
2021-07-27  2:21 ` [Intel-gfx] [PATCH 1/2] drm/i915/guc: Add fetch of hwconfig table John.C.Harrison
2021-07-27  2:21 ` [Intel-gfx] [PATCH 2/2] drm/i915/uapi: Add query for " John.C.Harrison
2021-07-27  2:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add support for querying hw info that UMDs need Patchwork
2021-07-27  3:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-27  7:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-27  9:49 ` [Intel-gfx] [PATCH 0/2] " Daniel Vetter
2021-07-27 18:46   ` John Harrison [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-16  0:06 John.C.Harrison
2021-09-03  0:53 John.C.Harrison
2021-07-27  1:09 John.C.Harrison

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=01479f2d-78be-fdf0-d3ef-c0de92e9a769@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=DRI-Devel@lists.freedesktop.org \
    --cc=Intel-GFX@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    /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