From: "'gregkh@linuxfoundation.org'" <gregkh@linuxfoundation.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Cui, Flora" <Flora.Cui@amd.com>,
"Zhang, Jerry" <Jerry.Zhang@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: patch "[PATCH] drm/amdgpu: update golden setting for verde" was seriously submitted to be applied to the 4.9-stable tree?
Date: Fri, 6 Jan 2017 16:29:11 +0100 [thread overview]
Message-ID: <20170106152911.GB23843@kroah.com> (raw)
In-Reply-To: <BN6PR12MB165213790CF0C32CAA532800F7630@BN6PR12MB1652.namprd12.prod.outlook.com>
On Fri, Jan 06, 2017 at 03:18:25PM +0000, Deucher, Alexander wrote:
> > -----Original Message-----
> > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > Sent: Friday, January 06, 2017 8:47 AM
> > To: Cui, Flora; Zhang, Jerry; Deucher, Alexander
> > Cc: stable@vger.kernel.org
> > Subject: WTF: patch "[PATCH] drm/amdgpu: update golden setting for
> > verde" was seriously submitted to be applied to the 4.9-stable tree?
> >
> > The patch below was submitted to be applied to the 4.9-stable tree.
> >
> > I fail to see how this patch meets the stable kernel rules as found at
> > Documentation/stable_kernel_rules.txt.
> >
> > I could be totally wrong, and if so, please respond to
> > <stable@vger.kernel.org> and let me know why this patch should be
> > applied. Otherwise, it is now dropped from my patch queues, never to be
> > seen again.
>
> The golden settings and tiling settings are from the hardware validation teams and fix stability issues with the GPUs. The original golden settings and certain versions of firmware resulted in GPU hangs and incorrect tiling resulting in corrupted displays in come configurations. As for the corrected revision ids, userspace drivers use that information to determine certain factors when setting up commands buffers to send to kernel driver. If that is incorrect it can lead to incorrect state setup and GPU hangs or corrupted displays. These are not super critical as radeon is still the preferred driver for these asic families, but it would be nice to have the fixes in stable.
These are patches with no changelog text at all (I don't know how your
subsystem maintainer took them in the first place), so how are we
supposed to know what hey do?
Random tables of data is a bit suspicious for stable kernel patches, as
I'm sure you can imagine, especially ones as big as these. Having some
information as to exactly what the updates do would be greatly
appreciated. I suggest you do that for future patches.
If you really think these should be applied to the stable kernel
tree(s), can you send them as a patch series so I can apply them, with
the information in the changelog as to what they do, these are all now
long gone from my patch queue.
thanks,
greg k-h
prev parent reply other threads:[~2017-01-06 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 13:46 WTF: patch "[PATCH] drm/amdgpu: update golden setting for verde" was seriously submitted to be applied to the 4.9-stable tree? gregkh
2017-01-06 15:18 ` Deucher, Alexander
2017-01-06 15:29 ` 'gregkh@linuxfoundation.org' [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=20170106152911.GB23843@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=Flora.Cui@amd.com \
--cc=Jerry.Zhang@amd.com \
--cc=stable@vger.kernel.org \
/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.