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: <BN6PR12MB1809C04BB67BD6D95822E3EFF7E70@BN6PR12MB1809.namprd12.prod.outlook.com>
Date:   Tue, 9 Oct 2018 13:55:06 +0000
From:   "Deucher, Alexander" <Alexander.Deucher@....com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "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

> -----Original Message-----
> From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Sent: Tuesday, October 9, 2018 8:45 AM
> To: Deucher, Alexander <Alexander.Deucher@....com>
> Cc: linux-kernel@...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 06:01:50PM +0000, Deucher, Alexander wrote:
> > > -----Original Message-----
> > > From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > > Sent: Monday, October 8, 2018 1:11 PM
> > > To: Deucher, Alexander <Alexander.Deucher@....com>
> > > Cc: linux-kernel@...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 04:02:19PM +0000, Deucher, Alexander wrote:
> > > > > -----Original Message-----
> > > > > From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > > > > Sent: Monday, October 8, 2018 10:44 AM
> > > > > To: Deucher, Alexander <Alexander.Deucher@....com>
> > > > > Cc: linux-kernel@...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
> > > > >
> > > > > Is it reverted in "upstream" as well?  If not, please get the
> > > > > fix in there and then I will be glad to backport it here.
> > > > >
> > > >
> > > > There's no breakage in upstream.  This patch addressed breakages
> > > > in
> > > > 4.19 specifically due to some other refactoring we did in the driver.
> > > > I'll try and dig out the exact series of patches this addressed.
> > >
> > > So there is no problem in 4.19-rc7?  That contridicts the statement
> > > of looking in drm-next for the fixes.
> >
> > Sorry, what statement about drm-next?  This patch was for 4.19 and was
> not intended for 4.18.  It was picked up by Sasha's auto select system for
> stable.
> 
> I thought this thread said that.
> 
> Ok, so I should just revert it?

Yes, please.

Thanks,

Alex