From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: kernel@pengutronix.de, patchwork-lst@pengutronix.de,
etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH] drm/etnaviv: fix dumping of active MMU context
Date: Wed, 19 Jul 2023 16:42:21 +0200 [thread overview]
Message-ID: <CAH9NwWd5TjfeYDCyaUDveGDz=QdUWKyB9UKpnDms3Hom-J3X5g@mail.gmail.com> (raw)
In-Reply-To: <CAH9NwWcf9tYG9Ua_b-TvvQHRY-j_VsAtGdkPBqwh4KH37B2qjQ@mail.gmail.com>
Hi Lucas,
Am Mi., 21. Juni 2023 um 17:44 Uhr schrieb Christian Gmeiner
<christian.gmeiner@gmail.com>:
>
> Hi Lucas,
>
> Am Mo., 17. Apr. 2023 um 19:42 Uhr schrieb Christian Gmeiner
> <christian.gmeiner@gmail.com>:
> >
> > Hi Lucas
> >
> > >
> > > gpu->mmu_context is the MMU context of the last job in the HW queue, which
> > > isn't necessarily the same as the context from the bad job. Dump the MMU
> > > context from the scheduler determined bad submit to make it work as intended.
> > >
> >
> > Good catch!
> >
>
> I think this patch did not land yet. Do you have plans to add it to
> etnaviv/next?
>
I have seen you added it today - great!
--
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info/privacypolicy
prev parent reply other threads:[~2023-07-19 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:38 [PATCH] drm/etnaviv: fix dumping of active MMU context Lucas Stach
2023-04-17 12:59 ` Sui Jingfeng
2023-04-17 17:42 ` [PATCH] " Christian Gmeiner
2023-06-21 15:44 ` Christian Gmeiner
2023-07-19 14:42 ` Christian Gmeiner [this message]
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='CAH9NwWd5TjfeYDCyaUDveGDz=QdUWKyB9UKpnDms3Hom-J3X5g@mail.gmail.com' \
--to=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=patchwork-lst@pengutronix.de \
/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.