linux-kernel - Re: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to DC for smu7/8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181008144917.GE32006@sasha-vm>
Date:   Mon, 8 Oct 2018 10:49:17 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     "Deucher, Alexander" <Alexander.Deucher@....com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "Wentland, Harry" <Harry.Wentland@....com>,
        "Zhu, Rex" <Rex.Zhu@....com>,
        Sasha Levin <alexander.levin@...rosoft.com>
Subject: Re: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to DC for
 smu7/8

On Mon, Oct 08, 2018 at 02:33:56PM +0000, Deucher, Alexander wrote:
>> -----Original Message-----
>> From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> Sent: Monday, September 24, 2018 7:53 AM
>> To: linux-kernel@...r.kernel.org
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>;
>> stable@...r.kernel.org; Wentland, Harry <Harry.Wentland@....com>;
>> Deucher, Alexander <Alexander.Deucher@....com>; Zhu, Rex
>> <Rex.Zhu@....com>; Sasha Levin <alexander.levin@...rosoft.com>
>> Subject: [PATCH 4.18 222/235] drm/amd/pp: Send khz clock values to DC for
>> smu7/8
>>
>> 4.18-stable review patch.  If anyone has any objections, please let me know.
>>
>
>This regresses power usage on 4.18.  Please revert.
>https://bugzilla.kernel.org/show_bug.cgi?id=201275

Hi Alex,

Thank you for the report.

I'm working on improving this process, I'd be very grateful if you could
answer a few questions about this:

1. Is the same breakage seen upstream? (if so, it should be reverted
there as well and we can grab the revert into -stable).
2. Does the issue reported by this patch ("pipes seem to hang with a 4k
DP and 1080p HDMI display") exist in the 4.18 stable tree?
3. If not, could you briefly explain why?

The algorithm I use was very confident about this patch being stable
material, and when I looked at it back then (and again now) I was very
confident of the same. If I can understand where I was wrong I could
improve my process.

Thank you!