linux-kernel - Re: [PATCH] k10temp support for AMD Ryzen w/ Vega gfx

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4938bed8-e612-959a-1b72-29dba0839ceb@roeck-us.net>
Date:   Tue, 6 Mar 2018 02:06:45 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     René Rebe <rene@...ctcode.de>
Cc:     linux-hwmon@...r.kernel.org, Clemens Ladisch <clemens@...isch.de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] k10temp support for AMD Ryzen w/ Vega gfx

On 03/05/2018 10:48 PM, René Rebe wrote:
> Hi,
> 
> On 06 Mar 2018, at 00:03, Guenter Roeck <linux@...ck-us.net <mailto:linux@...ck-us.net>> wrote:
> 
>> On Mon, Mar 05, 2018 at 11:38:24PM +0100, René Rebe wrote:
>>> Hi,
>>>
>>> This enables k10temp for the new AMD Ryzen APUs w/ Vega Mobile Gfx.
>>> Tested on Ryzen 5 2500U, the temperature looked plausible.
>>>
>>>  Signed-off-by: René Rebe <rene@...ctcode.de <mailto:rene@...ctcode.de>>
>>>
>>> PS: 1st RFC - might get white-space damaged, will resend when ACKed.
>>> Sorry my Xemacs/Mew broke.
>>>
>>> --- linux-4.15/drivers/hwmon/k10temp.c.vanilla2018-03-05 22:22:30.974331180 +0000
>>> +++ linux-4.15/drivers/hwmon/k10temp.c2018-03-05 22:24:17.186327291 +0000
>>> @@ -40,6 +40,10 @@
>>> #define PCI_DEVICE_ID_AMD_17H_DF_F30x1463
>>> #endif
>>>
>>> +#ifndef PCI_DEVICE_ID_AMD_17H_RR_NB
>>> +#define PCI_DEVICE_ID_AMD_17H_RR_NB0x15d0
>>> +#endif
>>> +
>>> /* CPUID function 0x80000001, ebx */
>>> #define CPUID_PKGTYPE_MASK0xf0000000
>>> #define CPUID_PKGTYPE_F0x00000000
>>> @@ -89,6 +93,8 @@
>>> { 0x17, "AMD Ryzen Threadripper 1950", 10000 },
>>> { 0x17, "AMD Ryzen Threadripper 1920", 10000 },
>>> { 0x17, "AMD Ryzen Threadripper 1910", 10000 },
>>> +{ 0x17, "AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx", 20000 },
>>> +{ 0x17, "AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx", 20000 },
>>
>> Do you have a confirmation that the temperature offset is correct ?
> 
> I tried all of the three currently used offsets and this was looked the most plausible.
> For me having some indication of temperature is better than having none at all.
> Maybe some contact at AMD can shed some light on it, too?
> 

Per the information I got (not from AMD), those CPUs are not supposed to have an offset.

Does the system have a Super-IO chip ? If so, what temperature does it report ?
Also, what temperatures do you see with 0 offset ?

Thanks,
Guenter

>> Thanks,
>> Guenter
>>
>>> };
>>>
>>> static void read_tempreg_pci(struct pci_dev *pdev, u32 *regval)
>>> @@ -289,6 +2944,7 @@
>>> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_16H_NB_F3) },
>>> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_16H_M30H_NB_F3) },
>>> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_DF_F3) },
>>> +{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_17H_RR_NB) },
>>> {}
>>> };
>>> MODULE_DEVICE_TABLE(pci, k10temp_id_table);
>>>
>>> -- 
>>> ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
>>> http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
>>> the body of a message to majordomo@...r.kernel.org <mailto:majordomo@...r.kernel.org>
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> 
> -- 
>   ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
> http://exactcode.com <http://exactcode.com/> | http://exactscan.com <http://exactscan.com/> | http://ocrkit.com <http://ocrkit.com/> | http://t2-project.org <http://t2-project.org/> | http://rene.rebe.de
>