| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6219 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When gathering the attributes of each hwmon chip, libsensors uses a
temporary structure in memory to order and group all the attributes
into features. This temporary structure used to be a single array with
room for every possible attribute/subfeature. While simple, this
approach required to predefine a maximum number of per-type sensor
that could be handled.
In order to get rid of this arbitrary limit, which we hit and had to
raise three times already, I changed the temporary structure to an
array of dynamically allocated per-type subattribute arrays. This lets
us not allocate any memory for types which aren't implemented by a
given chip, and more importantly, this lets us reallocate room for
more attributes of a given type as needed.
I decided to allocate chunks of 8 attributes at a time, as this seemed
a good compromise between two frequent reallocations and
over-provisioning. It could be tweaked if needed.
Icing on the cake, I benchmarked this change on two different systems
and it results in performance gains. The total heap usage as reported
by valgrind is down by 50% on average, with peak memory consumption
(as reported by valgrind's massif) also down by 43% on average. The
total instructions count (as reported by valgrind's callgrind) is down
by 11% on average, with measured execution time also down by a few
percents. Valgrind rocks, BTW.
I have some ideas to optimize the memory allocations further, but I do
not expect such a huge gain from them. They may not even improve peak
memory consumption as massif shows the peak is somewhere else now at
least in some cases.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6218 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
The new function name, sensors_compute_max_sf, better reflects what
the function is actually doing.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6217 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
| |
Several kernel drivers have already moved their attributes from the
hardware device to the hwmon class device, and others will follow.
Teach fancontrol about this possibility and let it adjust the attribute
paths transparently.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6216 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6215 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6214 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6212 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
|
|
| |
With recent (>202) systemd release, syslog.target is no longer provided:
services are ensured they are started after logging socket is setup, so
journal will capture all syslog messages and will store them and forward
them to syslog implementation (if running).
Patch from Ville Skyttä.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6211 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6210 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
| |
Patch from Phil Pokorny.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6209 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
This is needed to properly support all temperatures reported by the
coretemp driver on recent hardware.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6208 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6207 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6206 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6205 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6203 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
| |
Contributed by Jaromir Capik.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6197 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on a report and an original patch from Jaromir Capik:
There's no vendor_id entry in the /proc/cpuinfo file in case of PPC64
systems and consequently the script returns 3 screens full of the
following errors:
Use of uninitialized value in string eq at /usr/sbin/sensors-detect
line 6444
Use of uninitialized value in string eq at /usr/sbin/sensors-detect
line 6459
Use of uninitialized value in string eq at /usr/sbin/sensors-detect
line 6473
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6196 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
| |
sensors_get_adapter_name(). Paul Crawford asked questions about these
as he found the original documentation unclear. I'm including my
answers to his questions here, reformatted, so that other developers
can benefit from them too.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6195 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
Rework the way command line options are handled. If we ever need more
than this, we should consider moving to some GetOpt perl module.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6194 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
| |
It is better to use option --auto for non-interactive runs of the
sensors-detect script than faking an input to get the default answers
to all questions.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6193 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
Add option --auto to sensors-detect, for non-interactive use. Default
answer is assumed to every question.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6192 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6191 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6190 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
| |
NCT6683D is found on recent Intel mainboards (eg DH87MC, DH87RL).
NCT6681D is mentioned on the Nuvoton web site. NCT6682D is similar
to NCT6681D with added support for current monitoring.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6189 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
New superio chip, found on recent ASUS boards.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6188 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
We now have everything we need to handle built-in modules properly, so
do it. It should work fine since kernel 2.6.33.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6187 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
| |
/sys/module doesn't actually contain all built-in modules, only the
ones which have a version or at least one parameter. Better use file
modules.builtin which is generated since kernel 2.6.33, it is complete
and this will let us handle built-in modules properly.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6186 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6185 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
are not done in adm1021 driver, as this is no longer correct.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6184 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
| |
* EnvironmentFile is mandatory for sensord.
* fancontrol needs no EnvironmentFile.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6181 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6180 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6179 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6178 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6176 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6175 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
| |
Original file contributed by Nikola Pajkovsky.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6174 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6173 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
| |
Reported by Marc Ferland. Make DEVPATH and DEVNAME mandatory only when
using relative paths. Optionally support DEVNAME check when using
absolute paths.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6172 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
| |
Detection of the Dallas/Maxim DS1621, DS1625 and DS1631 chips is weak
and likely to result in false positive. There's no rationale for
keeping it in sensors-detect as these chips are not found in desktop
computer systems. So drop detection of these chips altogether.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6170 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6169 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6168 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6167 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6166 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a given PWM output controls more than one fan,
fanactive_min is no longer a space-separated list of numbers, it will
also include items of the form "A+B". The tests in the rest of the
code do not expect that and choke with errors like:
/usr/sbin/pwmconfig: line 926: [: 538+799: integer expression expected
/usr/sbin/pwmconfig: line 952: [: 538+799: integer expression expected
As the only thing we really care about is whether any fan stops
completely when PWM is 0, we can simply record the minimum of the
lowest speed of all affected fans.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6165 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
| |
fancontrol supports multiple controlled fans for quite some time now.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6164 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
| |
Detection threshold of 2/3 of the maximum speed is too low, some fans
will slow down to about that speed so controlled fans may be missed.
Use 3/4 as the threshold to avoid these false negatives.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6163 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
| |
Print the initial PWM values before letting the user change them. This
should be useful to better understand what happens next, and for user
support in general.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6162 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So we can not use the chip revision to detect the actual chip.
Merge entries for NCT5577D and NCT6776F into one.
List NCT5572D as another variant of W83677HG-I (NCT6775).
NCT6106D chip ID as observed on a real system is 0xC452, not 0x1061 as
claimed by the data sheet. Confirmed with Nuvoton that the correct
chip ID is 0xC452. Also list its variants NCT6102D and NCT6104D.
List NCT5532D as variant of NCT6779D. Data sheets list possible chip
IDs of 0xC561 and 0xC562, so detect and accept all chip revisions.
Point to new nct6775 driver for NCT6775, NCT6776, and NCT6779.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6128 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6127 7894878c-1315-0410-8ee3-d5d059ff63e0
|
|
|
|
| |
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@6126 7894878c-1315-0410-8ee3-d5d059ff63e0
|