2014-11-27 18:27:34 +00:00
|
|
|
#ifndef HEADER_Platform
|
|
|
|
#define HEADER_Platform
|
|
|
|
/*
|
2014-11-27 21:33:37 +00:00
|
|
|
htop - freebsd/Platform.h
|
2014-11-27 18:27:34 +00:00
|
|
|
(C) 2014 Hisham H. Muhammad
|
2020-10-05 07:51:32 +00:00
|
|
|
Released under the GNU GPLv2, see the COPYING file
|
2014-11-27 18:27:34 +00:00
|
|
|
in the source distribution for its full text.
|
|
|
|
*/
|
|
|
|
|
2020-11-11 21:15:35 +00:00
|
|
|
#include <stdbool.h>
|
|
|
|
#include <sys/types.h>
|
|
|
|
|
2014-11-27 18:27:34 +00:00
|
|
|
#include "Action.h"
|
2014-11-27 23:07:42 +00:00
|
|
|
#include "BatteryMeter.h"
|
2020-10-21 15:06:32 +00:00
|
|
|
#include "DiskIOMeter.h"
|
PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
#include "Hashtable.h"
|
2020-11-18 14:12:18 +00:00
|
|
|
#include "Meter.h"
|
2021-03-01 00:55:15 +00:00
|
|
|
#include "NetworkIOMeter.h"
|
2020-11-18 14:12:18 +00:00
|
|
|
#include "Process.h"
|
2020-11-11 21:15:35 +00:00
|
|
|
#include "ProcessLocksScreen.h"
|
2015-10-19 19:22:54 +00:00
|
|
|
#include "SignalsPanel.h"
|
2021-03-30 04:55:48 +00:00
|
|
|
#include "generic/gettime.h"
|
2021-03-03 22:00:34 +00:00
|
|
|
#include "generic/hostname.h"
|
|
|
|
#include "generic/uname.h"
|
2014-11-27 18:27:34 +00:00
|
|
|
|
2020-11-18 14:12:18 +00:00
|
|
|
|
2020-12-19 17:10:03 +00:00
|
|
|
extern const ProcessField Platform_defaultFields[];
|
2015-03-16 06:13:42 +00:00
|
|
|
|
2016-08-30 12:41:17 +00:00
|
|
|
extern const SignalItem Platform_signals[];
|
2015-10-19 19:22:54 +00:00
|
|
|
|
2016-08-30 12:41:17 +00:00
|
|
|
extern const unsigned int Platform_numberOfSignals;
|
2015-10-19 19:22:54 +00:00
|
|
|
|
2020-10-05 11:19:50 +00:00
|
|
|
extern const MeterClass* const Platform_meterTypes[];
|
2014-11-27 21:33:37 +00:00
|
|
|
|
2020-11-19 01:32:07 +00:00
|
|
|
void Platform_init(void);
|
|
|
|
|
|
|
|
void Platform_done(void);
|
2014-11-27 21:33:37 +00:00
|
|
|
|
2020-11-23 06:32:57 +00:00
|
|
|
void Platform_setBindings(Htop_Action* keys);
|
|
|
|
|
2020-09-08 12:28:34 +00:00
|
|
|
int Platform_getUptime(void);
|
2014-11-27 18:27:34 +00:00
|
|
|
|
2014-11-27 22:03:29 +00:00
|
|
|
void Platform_getLoadAverage(double* one, double* five, double* fifteen);
|
|
|
|
|
2020-09-08 12:28:34 +00:00
|
|
|
int Platform_getMaxPid(void);
|
2014-11-27 22:18:01 +00:00
|
|
|
|
2021-02-17 16:38:35 +00:00
|
|
|
double Platform_setCPUValues(Meter* this, unsigned int cpu);
|
2015-03-16 06:13:42 +00:00
|
|
|
|
|
|
|
void Platform_setMemoryValues(Meter* this);
|
|
|
|
|
|
|
|
void Platform_setSwapValues(Meter* this);
|
2014-11-27 23:07:42 +00:00
|
|
|
|
2019-07-06 04:27:49 +00:00
|
|
|
void Platform_setZfsArcValues(Meter* this);
|
|
|
|
|
2019-09-03 18:26:02 +00:00
|
|
|
void Platform_setZfsCompressedArcValues(Meter* this);
|
|
|
|
|
Introduce CLAMP macro. Unify all MIN(MAX(a,b),c) uses.
With the CLAMP macro replacing the combination of MIN and MAX, we will
have at least two advantages:
1. It's more obvious semantically.
2. There are no more mixes of confusing uses like MIN(MAX(a,b),c) and
MAX(MIN(a,b),c) and MIN(a,MAX(b,c)) appearing everywhere. We unify
the 'clamping' with a single macro.
Note that the behavior of this CLAMP macro is different from
the combination `MAX(low,MIN(x,high))`.
* This CLAMP macro expands to two comparisons instead of three from
MAX and MIN combination. In theory, this makes the code slightly
smaller, in case that (low) or (high) or both are computed at
runtime, so that compilers cannot optimize them. (The third
comparison will matter if (low)>(high); see below.)
* CLAMP has a side effect, that if (low)>(high) it will produce weird
results. Unlike MIN & MAX which will force either (low) or (high) to
win. No assertion of ((low)<=(high)) is done in this macro, for now.
This CLAMP macro is implemented like described in glib
<http://developer.gnome.org/glib/stable/glib-Standard-Macros.html>
and does not handle weird uses like CLAMP(a++, low++, high--) .
2016-01-15 12:26:01 +00:00
|
|
|
char* Platform_getProcessEnv(pid_t pid);
|
|
|
|
|
2020-11-11 21:15:35 +00:00
|
|
|
char* Platform_getInodeFilename(pid_t pid, ino_t inode);
|
|
|
|
|
|
|
|
FileLocks_ProcessData* Platform_getProcessLocks(pid_t pid);
|
|
|
|
|
2020-10-21 15:06:32 +00:00
|
|
|
bool Platform_getDiskIO(DiskIOData* data);
|
2020-09-13 17:46:34 +00:00
|
|
|
|
2021-03-01 00:55:15 +00:00
|
|
|
bool Platform_getNetworkIO(NetworkIOData* data);
|
2020-10-08 14:34:54 +00:00
|
|
|
|
2020-11-25 11:46:00 +00:00
|
|
|
void Platform_getBattery(double* percent, ACPresence* isOnAC);
|
2020-11-17 07:12:38 +00:00
|
|
|
|
2021-03-02 04:58:11 +00:00
|
|
|
static inline void Platform_getHostname(char* buffer, size_t size) {
|
2021-03-02 23:59:28 +00:00
|
|
|
Generic_hostname(buffer, size);
|
2021-03-02 04:58:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline void Platform_getRelease(char** string) {
|
2021-03-02 23:59:28 +00:00
|
|
|
*string = Generic_uname();
|
2021-03-02 04:58:11 +00:00
|
|
|
}
|
|
|
|
|
2021-03-22 03:49:07 +00:00
|
|
|
#define PLATFORM_LONG_OPTIONS
|
|
|
|
|
|
|
|
static inline void Platform_longOptionsUsage(ATTR_UNUSED const char* name) { }
|
|
|
|
|
2021-03-17 21:23:07 +00:00
|
|
|
static inline bool Platform_getLongOption(ATTR_UNUSED int opt, ATTR_UNUSED int argc, ATTR_UNUSED char** argv) {
|
2021-03-17 03:29:40 +00:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2021-03-30 04:55:48 +00:00
|
|
|
static inline void Platform_gettime_realtime(struct timeval* tv, uint64_t* msec) {
|
2021-07-14 17:15:09 +00:00
|
|
|
Generic_gettime_realtime(tv, msec);
|
2021-03-30 04:55:48 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline void Platform_gettime_monotonic(uint64_t* msec) {
|
2021-07-14 17:15:09 +00:00
|
|
|
Generic_gettime_monotonic(msec);
|
2021-03-30 04:55:48 +00:00
|
|
|
}
|
|
|
|
|
PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
static inline Hashtable* Platform_dynamicMeters(void) { return NULL; }
|
2021-06-23 07:44:56 +00:00
|
|
|
|
2021-09-03 02:11:31 +00:00
|
|
|
static inline void Platform_dynamicMetersDone(ATTR_UNUSED Hashtable* table) { }
|
|
|
|
|
2021-06-23 07:44:56 +00:00
|
|
|
static inline void Platform_dynamicMeterInit(ATTR_UNUSED Meter* meter) { }
|
|
|
|
|
|
|
|
static inline void Platform_dynamicMeterUpdateValues(ATTR_UNUSED Meter* meter) { }
|
|
|
|
|
|
|
|
static inline void Platform_dynamicMeterDisplay(ATTR_UNUSED const Meter* meter, ATTR_UNUSED RichString* out) { }
|
|
|
|
|
PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
static inline Hashtable* Platform_dynamicColumns(void) { return NULL; }
|
|
|
|
|
|
|
|
static inline const char* Platform_dynamicColumnInit(ATTR_UNUSED unsigned int key) { return NULL; }
|
|
|
|
|
2021-09-03 02:11:31 +00:00
|
|
|
static inline void Platform_dynamicColumnsDone(ATTR_UNUSED Hashtable* table) { }
|
|
|
|
|
PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
static inline bool Platform_dynamicColumnWriteField(ATTR_UNUSED const Process* proc, ATTR_UNUSED RichString* str, ATTR_UNUSED unsigned int key) { return false; }
|
|
|
|
|
2014-11-27 18:27:34 +00:00
|
|
|
#endif
|