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
| ||
|
Message-ID: <561DAD1B.9010101@roeck-us.net> Date: Tue, 13 Oct 2015 18:17:15 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Lukasz Odzioba <lukasz.odzioba@...el.com>, fenghua.yu@...el.com Cc: jdelvare@...e.de, lm-sensors@...sensors.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128. On 10/12/2015 04:53 AM, Lukasz Odzioba wrote: > A new limit selected arbitrarily as power of two greater than > required minimum for Xeon Phi processor. > > Currently driver is not able to handle cores with core ID greater than 32. > Such attempt ends up with the following error in dmesg: > coretemp coretemp.0: Adding Core XXX failed > > Signed-off-by: Lukasz Odzioba <lukasz.odzioba@...el.com> Applied, after fixing up the subject and listing the current required limit of 72 cores for Xeon Phi (per published information). Guenter > --- > drivers/hwmon/coretemp.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/hwmon/coretemp.c b/drivers/hwmon/coretemp.c > index 3e03379..6a27eb2 100644 > --- a/drivers/hwmon/coretemp.c > +++ b/drivers/hwmon/coretemp.c > @@ -52,7 +52,7 @@ module_param_named(tjmax, force_tjmax, int, 0444); > MODULE_PARM_DESC(tjmax, "TjMax value in degrees Celsius"); > > #define BASE_SYSFS_ATTR_NO 2 /* Sysfs Base attr no for coretemp */ > -#define NUM_REAL_CORES 32 /* Number of Real cores per cpu */ > +#define NUM_REAL_CORES 128 /* Number of Real cores per cpu */ > #define CORETEMP_NAME_LENGTH 19 /* String Length of attrs */ > #define MAX_CORE_ATTRS 4 /* Maximum no of basic attrs */ > #define TOTAL_ATTRS (MAX_CORE_ATTRS + 1) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists