From: Matthew Brost <matthew.brost@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 01/10] drm/i915/guc: Update GuC ADS size for error capture lists
Date: Thu, 3 Feb 2022 11:03:24 -0800 [thread overview]
Message-ID: <20220203190324.GA4413@jons-linux-dev-box> (raw)
In-Reply-To: <20220126224619.lyftw7w3okka4lfg@ldmartin-desk2>
On Wed, Jan 26, 2022 at 02:46:19PM -0800, Lucas De Marchi wrote:
> On Wed, Jan 26, 2022 at 02:48:13AM -0800, Alan Previn wrote:
> > Update GuC ADS size allocation to include space for
> > the lists of error state capture register descriptors.
> >
> > Also, populate the lists of registers we want GuC to report back to
> > Host on engine reset events. This list should include global,
> > engine-class and engine-instance registers for every engine-class
> > type on the current hardware.
> >
> > NOTE: Start with a sample table of register lists to layout the
> > framework before adding real registers in subsequent patch.
> >
> > Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> > ---
>
> ...
>
> > static void __guc_ads_init(struct intel_guc *guc)
> > {
> > struct intel_gt *gt = guc_to_gt(guc);
> > @@ -573,9 +553,9 @@ 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);
> > -
> > + /* Lists for error capture debug */
> > + intel_guc_capture_prep_lists(guc, (struct guc_ads *)blob, base,
>
> no, please don't cast/export struct guc_ads like this. We can't really
> dereference it since it may be in IO memory.
>
> See https://patchwork.freedesktop.org/series/99378/ with the huge
> refactor in this file to make it conform to the rules of accessing IO
> memory.
>
> Maybe this list could be appended in the same reglist buffer and we just
> copy it once to its final location, like we are doing with the reglist?
>
Agree with Lucas here, let's create the capture list on probe and store
it somewhere in the device data. On ADS population this more or less
turns into a memcpy (or after Lucas's series a dma-buf-map call). And on
fini, just free to stored data. The create capture list IMO is fine to
be done in an external file and return the data to the ADS code but
let's make sure everyone is on board with that. Maybe ping Lucas
directly about this?
Specific patch Lucas's is referencing:
https://patchwork.freedesktop.org/patch/471051/?series=99378&rev=1
Matt
> Lucas De Marchi
next prev parent reply other threads:[~2022-02-03 19:09 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 10:48 [Intel-gfx] [PATCH v5 00/10] Add GuC Error Capture Support Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 01/10] drm/i915/guc: Update GuC ADS size for error capture lists Alan Previn
2022-01-26 18:09 ` Jani Nikula
2022-01-26 18:15 ` Jani Nikula
2022-01-26 22:46 ` Lucas De Marchi
2022-02-03 19:03 ` Matthew Brost [this message]
2022-02-03 20:04 ` Lucas De Marchi
2022-02-03 20:37 ` Teres Alexis, Alan Previn
2022-02-03 20:40 ` Teres Alexis, Alan Previn
2022-02-03 21:40 ` Lucas De Marchi
2022-02-03 21:58 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 02/10] drm/i915/guc: Add XE_LP registers for GuC error state capture Alan Previn
2022-01-26 18:13 ` Jani Nikula
2022-01-26 21:46 ` Teres Alexis, Alan Previn
2022-01-27 9:30 ` Jani Nikula
2022-01-28 16:54 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 03/10] drm/i915/guc: Add DG2 " Alan Previn
2022-02-05 1:28 ` Umesh Nerlige Ramappa
2022-02-10 5:17 ` Teres Alexis, Alan Previn
2022-02-11 19:24 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 04/10] drm/i915/guc: Add Gen9 " Alan Previn
2022-02-07 19:14 ` Umesh Nerlige Ramappa
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 05/10] drm/i915/guc: Add GuC's error state capture output structures Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 06/10] drm/i915/guc: Update GuC's log-buffer-state access for error capture Alan Previn
2022-01-27 4:26 ` Teres Alexis, Alan Previn
2022-02-04 18:19 ` Matthew Brost
2022-02-08 19:38 ` Teres Alexis, Alan Previn
2022-02-08 22:18 ` Matthew Brost
2022-02-08 22:55 ` Teres Alexis, Alan Previn
2022-02-09 3:34 ` Matthew Brost
2022-02-09 3:41 ` Matthew Brost
2022-02-09 3:51 ` Teres Alexis, Alan Previn
2022-02-14 19:20 ` Teres Alexis, Alan Previn
2022-02-15 1:22 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 07/10] drm/i915/guc: Extract GuC error capture lists on G2H notification Alan Previn
2022-02-11 1:36 ` Umesh Nerlige Ramappa
2022-02-13 19:47 ` Teres Alexis, Alan Previn
2022-02-17 19:21 ` Umesh Nerlige Ramappa
2022-02-25 7:21 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 08/10] drm/i915/guc: Plumb GuC-capture into gpu_coredump Alan Previn
2022-02-11 2:11 ` Umesh Nerlige Ramappa
2022-02-12 0:31 ` Teres Alexis, Alan Previn
2022-02-12 0:38 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 09/10] drm/i915/guc: Follow legacy register names Alan Previn
2022-02-03 19:09 ` Matthew Brost
2022-02-04 18:53 ` Teres Alexis, Alan Previn
2022-01-26 10:48 ` [Intel-gfx] [PATCH v5 10/10] drm/i915/guc: Print the GuC error capture output register list Alan Previn
2022-02-07 21:43 ` Umesh Nerlige Ramappa
2022-01-26 18:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add GuC Error Capture Support (rev5) Patchwork
2022-01-26 18:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-26 19:25 ` [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=20220203190324.GA4413@jons-linux-dev-box \
--to=matthew.brost@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@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