amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Revert "drm/amd/display: Revalidate bandwidth before commiting DC updates"
Date: Mon, 29 Jun 2020 12:20:36 -0400	[thread overview]
Message-ID: <CADnq5_PmHGXXxocZeXCOW-rESXNo9aStpT4eb4Zg+jRRmoONkg@mail.gmail.com> (raw)
In-Reply-To: <5f57c33d-dfd7-1f1f-f448-e05963caa9ec@amd.com>

On Mon, Jun 29, 2020 at 12:13 PM Kazlauskas, Nicholas
<nicholas.kazlauskas@amd.com> wrote:
>
> On 2020-06-29 11:40 a.m., Kazlauskas, Nicholas wrote:
> > On 2020-06-29 11:36 a.m., Alex Deucher wrote:
> >> Seems to cause stability issues for some users.
> >>
> >> This reverts commit a24eaa5c51255b344d5a321f1eeb3205f2775498.
> >>
> >> Bug:
> >> https://gitlab.freedesktop.org/drm/amd/-/issues/1191
> >>
> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >
> > I don't see the error in their log. How do we know this commit is
> > actually causing the issue?
> >
> > I don't really want to revert this commit because it means that we
> > missed rejecting a commit during atomic check, meaning we're either
> > going to get underflow on the screen or a pipe hang.
> >
> > Regards,
> > Nicholas Kazlauskas
>
> Actually, we only want to be doing this on full updates - it's not a
> very fast operation. Not sure if this is causing their stability issue
> though.

Maybe.  Several people have reported reverting it fixes hangs.  Maybe
something in the validation code hangs?  Maybe some sort of software
deadlock?

Alex


>
> Regards,
> Nicholas Kazlauskas
>
> >
> >> ---
> >>   drivers/gpu/drm/amd/display/dc/core/dc.c | 6 ------
> >>   1 file changed, 6 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c
> >> b/drivers/gpu/drm/amd/display/dc/core/dc.c
> >> index 67402d75e67e..94230bb3195d 100644
> >> --- a/drivers/gpu/drm/amd/display/dc/core/dc.c
> >> +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
> >> @@ -2607,12 +2607,6 @@ void dc_commit_updates_for_stream(struct dc *dc,
> >>       copy_stream_update_to_stream(dc, context, stream, stream_update);
> >> -    if (!dc->res_pool->funcs->validate_bandwidth(dc, context, false)) {
> >> -        DC_ERROR("Mode validation failed for stream update!\n");
> >> -        dc_release_state(context);
> >> -        return;
> >> -    }
> >> -
> >>       commit_planes_for_stream(
> >>                   dc,
> >>                   srf_updates,
> >>
> >
> > _______________________________________________
> > amd-gfx mailing list
> > amd-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
> >
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      reply	other threads:[~2020-06-29 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 15:36 [PATCH] Revert "drm/amd/display: Revalidate bandwidth before commiting DC updates" Alex Deucher
2020-06-29 15:40 ` Kazlauskas, Nicholas
2020-06-29 16:13   ` Kazlauskas, Nicholas
2020-06-29 16:20     ` Alex Deucher [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=CADnq5_PmHGXXxocZeXCOW-rESXNo9aStpT4eb4Zg+jRRmoONkg@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=nicholas.kazlauskas@amd.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;
as well as URLs for NNTP newsgroup(s).