From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "dev@lankhorst.se" <dev@lankhorst.se>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 5/9] drm/xe: Nuke xe from xe_devcoredump
Date: Mon, 22 Jan 2024 15:40:18 -0500 [thread overview]
Message-ID: <Za7SskbqwItP8qRf@intel.com> (raw)
In-Reply-To: <38dfe3b065dc97df697ac5fb7bf51895ba503abc.camel@intel.com>
On Mon, Jan 22, 2024 at 03:26:57PM -0500, Souza, Jose wrote:
> On Mon, 2024-01-22 at 15:11 -0500, Rodrigo Vivi wrote:
> > On Mon, Jan 22, 2024 at 09:04:41AM -0800, José Roberto de Souza wrote:
> > > xe is never set in xe_devcoredump but if xe_device is needed
> > > devcoredump_to_xe_device() can be used.
> > >
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Cc: Maarten Lankhorst <dev@lankhorst.se>
> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > ---
> > > drivers/gpu/drm/xe/xe_devcoredump_types.h | 2 --
> > > drivers/gpu/drm/xe/xe_device.h | 5 +++++
> > > 2 files changed, 5 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/xe/xe_devcoredump_types.h b/drivers/gpu/drm/xe/xe_devcoredump_types.h
> > > index 9a12959ed6b14..d259119b2c980 100644
> > > --- a/drivers/gpu/drm/xe/xe_devcoredump_types.h
> > > +++ b/drivers/gpu/drm/xe/xe_devcoredump_types.h
> > > @@ -47,8 +47,6 @@ struct xe_devcoredump_snapshot {
> > > * for reading the information.
> > > */
> > > struct xe_devcoredump {
> > > - /** @xe: Xe device. */
> > > - struct xe_device *xe;
> >
> > good catch.
> >
> > > /** @captured: The snapshot of the first hang has already been taken. */
> > > bool captured;
> > > /** @snapshot: Snapshot is captured at time of the first crash */
> > > diff --git a/drivers/gpu/drm/xe/xe_device.h b/drivers/gpu/drm/xe/xe_device.h
> > > index ce20f6fe6219a..781a1aa164ecf 100644
> > > --- a/drivers/gpu/drm/xe/xe_device.h
> > > +++ b/drivers/gpu/drm/xe/xe_device.h
> > > @@ -35,6 +35,11 @@ static inline struct xe_device *ttm_to_xe_device(struct ttm_device *ttm)
> > > return container_of(ttm, struct xe_device, ttm);
> > > }
> > >
> > > +static inline struct xe_device *devcoredump_to_xe_device(struct xe_devcoredump *devcoredump)
> > > +{
> > > + return container_of(devcoredump, struct xe_device, devcoredump);
> > > +}
> > > +
> >
> > But now this is kind of duplicated with the coredump_to_xe that is in xe_devcoredump.c
> > itself.
>
> oh missed that, will drop devcoredump_to_xe_device() then.
with that feel free to already use:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> >
> > > struct xe_device *xe_device_create(struct pci_dev *pdev,
> > > const struct pci_device_id *ent);
> > > int xe_device_probe_early(struct xe_device *xe);
> > > --
> > > 2.43.0
> > >
>
next prev parent reply other threads:[~2024-01-22 20:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:04 [PATCH 1/9] drm/xe: Remove double new line in devcoredump José Roberto de Souza
2024-01-22 17:04 ` [PATCH 2/9] drm/xe: Change devcoredump functions parameters to xe_sched_job José Roberto de Souza
2024-01-22 18:39 ` Summers, Stuart
2024-01-22 17:04 ` [PATCH 3/9] drm/xe: Add functions to convert regular address to canonical address and back José Roberto de Souza
2024-01-22 18:38 ` Summers, Stuart
2024-01-22 18:43 ` Souza, Jose
2024-01-24 15:16 ` Summers, Stuart
2024-01-24 15:20 ` Souza, Jose
2024-01-29 17:54 ` Summers, Stuart
2024-01-23 17:48 ` Jani Nikula
2024-01-22 17:04 ` [PATCH 4/9] drm/xe: Add batch buffer addresses to devcoredump José Roberto de Souza
2024-01-22 20:13 ` Rodrigo Vivi
2024-01-22 17:04 ` [PATCH 5/9] drm/xe: Nuke xe from xe_devcoredump José Roberto de Souza
2024-01-22 20:11 ` Rodrigo Vivi
2024-01-22 20:26 ` Souza, Jose
2024-01-22 20:40 ` Rodrigo Vivi [this message]
2024-01-22 17:04 ` [PATCH 6/9] drm/xe: Stash GMD_ID value in xe_gt José Roberto de Souza
2024-01-22 17:04 ` [PATCH 7/9] drm/xe: Print more device information in devcoredump José Roberto de Souza
2024-01-22 20:18 ` Rodrigo Vivi
2024-01-22 21:12 ` Souza, Jose
2024-01-22 17:04 ` [PATCH 8/9] drm/xe: Print registers spread in 2 u32 as u64 José Roberto de Souza
2024-01-22 20:14 ` Rodrigo Vivi
2024-01-22 17:04 ` [PATCH 9/9] drm/xe: Remove addional spaces in devcoredump HW Engines section José Roberto de Souza
2024-01-22 20:18 ` Rodrigo Vivi
2024-01-22 17:32 ` ✓ CI.Patch_applied: success for series starting with [1/9] drm/xe: Remove double new line in devcoredump Patchwork
2024-01-22 17:32 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-22 17:33 ` ✓ CI.KUnit: success " Patchwork
2024-01-22 17:40 ` ✓ CI.Build: " Patchwork
2024-01-22 17:41 ` ✗ CI.Hooks: failure " Patchwork
2024-01-22 17:42 ` ✓ CI.checksparse: success " Patchwork
2024-01-22 18:05 ` ✓ CI.BAT: " Patchwork
2024-01-22 18:28 ` [PATCH 1/9] " Summers, Stuart
2024-01-22 18:40 ` Souza, Jose
2024-01-22 20:20 ` Rodrigo Vivi
2024-01-24 15:17 ` Summers, Stuart
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=Za7SskbqwItP8qRf@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.