From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ttm: soften TTM warnings
Date: Thu, 4 Mar 2021 19:02:57 +0100 [thread overview]
Message-ID: <a2191eb8-bfd5-b1fb-bd6d-d84c6561c076@gmail.com> (raw)
In-Reply-To: <20210304140509.u33mxittujxubaaj@sirius.home.kraxel.org>
Am 04.03.21 um 15:05 schrieb Gerd Hoffmann:
> On Wed, Mar 03, 2021 at 04:57:57PM +0100, Christian König wrote:
>> QXL indeed unrefs pinned BOs and the warnings are spamming peoples log files.
>>
>> Make sure we warn only once until the QXL driver is fixed.
>> - dma_resv_assert_held(bo->base.resv);
>> + if (!bo->deleted)
>> + dma_resv_assert_held(bo->base.resv);
> Hmm? I'm not aware of qxl having problems with this one.
> Did I miss something?
See the mail from Peter, but asserts were triggered when the pin_count
was non zero and destruction.
>
>> - if (WARN_ON(bo->pin_count)) {
>> + if (WARN_ON_ONCE(bo->pin_count)) {
> Well, as temporary thing this is rather pointless, qxl fix for this one
> is already queued in drm-misc-fixes so this would only land after the
> qxl fixes ...
>
> But I think using WARN_ON_ONCE() is a good idea in general, especially
> in a code path like this where a single bug can easily cause a flood of
> stack traces.
Well that flood of stack traces can also be helpful, cause it makes
people report such kind of issues immediately.
Anyway I'm going to keep that WARN_ON_ONCE for a cycle or two and if I
don't hear any more complains I'm going to completely remove this
"feature" and just always warn when we see a non zero pin_count on
destruction.
Christian.
>
> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
>
> take care,
> Gerd
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-03-04 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:57 [PATCH] drm/ttm: soften TTM warnings Christian König
2021-03-03 17:19 ` Daniel Vetter
2021-03-03 20:36 ` Christian König
2021-03-03 20:48 ` Daniel Vetter
2021-03-04 14:05 ` Gerd Hoffmann
2021-03-04 18:02 ` Christian König [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=a2191eb8-bfd5-b1fb-bd6d-d84c6561c076@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.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.