From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v11 1/5] drm/xe/guc: Prepare GuC register list and update ADS size for error capture
Date: Fri, 28 Jun 2024 16:06:59 -0400 [thread overview]
Message-ID: <fb510ccd-1d3c-4fef-b365-01765f8e672d@intel.com> (raw)
In-Reply-To: <i6u5mewr37v7ujevqsevvjcdq3g56jmn4zyquv6qym42i2anvq@ve57hgm3xovu>
As guc double-load will be changed in the future, the comment will be
removed to avoid misleading.
Regards,
Zhanjun Dong
On 2024-06-28 12:05 p.m., Lucas De Marchi wrote:
> On Mon, Jun 24, 2024 at 02:54:00PM GMT, Zhanjun Dong wrote:
>> @@ -398,6 +401,12 @@ int xe_guc_ads_init(struct xe_guc_ads *ads)
>> struct xe_bo *bo;
>>
>> ads->golden_lrc_size = calculate_golden_lrc_size(ads);
>> + /*
>> + * At time of ads init, hwconfig was not loaded, engine info like
>> + * engine mask is not ready.
>
> pass by comment: this never really mattered and was just artificially
> done due to delaying the engine_mask initialization. engine_mask comes
> from fuses and possible engines from platform, not from hwconfig.
> This is gone since commit d69c3d4b5382 ("drm/xe/ads: Use flexible-array")
>
> For ADS initialization I believe we still want size 0 when loading guc
> for hwconfig and only calculate it when it's for real. This guc double-load
> is something we may get rid of in future.
>
> Lucas De Marchi
next prev parent reply other threads:[~2024-06-28 20:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 21:53 [PATCH v11 0/5] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-06-24 21:54 ` [PATCH v11 1/5] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-06-27 0:13 ` Teres Alexis, Alan Previn
2024-06-28 20:05 ` Dong, Zhanjun
2024-06-27 18:45 ` Michal Wajdeczko
2024-06-28 23:00 ` Dong, Zhanjun
2024-06-28 16:05 ` Lucas De Marchi
2024-06-28 20:06 ` Dong, Zhanjun [this message]
2024-06-28 20:17 ` Lucas De Marchi
2024-06-24 21:54 ` [PATCH v11 2/5] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-06-24 21:54 ` [PATCH v11 3/5] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-06-27 18:56 ` Michal Wajdeczko
2024-06-28 23:15 ` Dong, Zhanjun
2024-07-03 3:10 ` Teres Alexis, Alan Previn
2024-07-04 20:27 ` Dong, Zhanjun
2024-06-24 21:54 ` [PATCH v11 4/5] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-06-28 0:01 ` Teres Alexis, Alan Previn
2024-06-24 21:54 ` [PATCH v11 5/5] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-06-24 21:59 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev11) Patchwork
2024-06-24 21:59 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-24 22:00 ` ✓ CI.KUnit: success " Patchwork
2024-06-24 22:12 ` ✓ CI.Build: " Patchwork
2024-06-24 22:14 ` ✗ CI.Hooks: failure " Patchwork
2024-06-24 22:16 ` ✓ CI.checksparse: success " Patchwork
2024-06-24 22:39 ` ✓ CI.BAT: " Patchwork
2024-06-25 0:52 ` ✗ CI.FULL: 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=fb510ccd-1d3c-4fef-b365-01765f8e672d@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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