Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

On 04/29/2018 11:19 AM, Gabriel C wrote: 2018-04-29 19:46 GMT+02:00 Guenter Roeck : On 04/28/2018 06:54 PM, Guenter Roeck wrote: The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

On 04/29/2018 11:19 AM, Gabriel C wrote: 2018-04-29 19:46 GMT+02:00 Guenter Roeck : On 04/28/2018 06:54 PM, Guenter Roeck wrote: The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is racy. On top of that,

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

2018-04-29 19:46 GMT+02:00 Guenter Roeck : > On 04/28/2018 06:54 PM, Guenter Roeck wrote: >> >> The SMN (System Management Network) on Family 17h AMD CPUs is also >> accessed >> from other drivers, specifically EDAC. Accessing it directly is racy. >> On top of that, accessing

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

2018-04-29 19:46 GMT+02:00 Guenter Roeck : > On 04/28/2018 06:54 PM, Guenter Roeck wrote: >> >> The SMN (System Management Network) on Family 17h AMD CPUs is also >> accessed >> from other drivers, specifically EDAC. Accessing it directly is racy. >> On top of that, accessing the SMN through root

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

On 04/28/2018 06:54 PM, Guenter Roeck wrote: The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is racy. On top of that, accessing the SMN through root bridge 00:00 is wrong on multi-die CPUs and may result in

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

On 04/28/2018 06:54 PM, Guenter Roeck wrote: The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is racy. On top of that, accessing the SMN through root bridge 00:00 is wrong on multi-die CPUs and may result in

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

2018-04-29 3:54 GMT+02:00 Guenter Roeck : > The SMN (System Management Network) on Family 17h AMD CPUs is also accessed > from other drivers, specifically EDAC. Accessing it directly is racy. > On top of that, accessing the SMN through root bridge 00:00 is wrong on > multi-die

Re: [PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

2018-04-29 3:54 GMT+02:00 Guenter Roeck : > The SMN (System Management Network) on Family 17h AMD CPUs is also accessed > from other drivers, specifically EDAC. Accessing it directly is racy. > On top of that, accessing the SMN through root bridge 00:00 is wrong on > multi-die CPUs and may result

[PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is racy. On top of that, accessing the SMN through root bridge 00:00 is wrong on multi-die CPUs and may result in reading the temperature from the wrong die. Use

[PATCH 2/2] hwmon: (k10temp) Use API function to access System Management Network

The SMN (System Management Network) on Family 17h AMD CPUs is also accessed from other drivers, specifically EDAC. Accessing it directly is racy. On top of that, accessing the SMN through root bridge 00:00 is wrong on multi-die CPUs and may result in reading the temperature from the wrong die. Use