osfmk/man/etap_get_info.html
Function - Map ETAP buffers and tables into server's address space.
**#include<mach/etap.h>**** kern\_return\_t etap\_get\_info****(host\_priv\_t**priv\_port, **int** int, **int** int, **vm\_offset\_t** vm\_offset\_t, **vm\_offset\_t** vm\_offset\_t, **int** int, **int** int, **int** int, **int** int**);**
priv_portthe name of the Server's privileged device port (server_device_port), granting the Server access to this service.
et_entriesused to return number of entries in the event table.
st_entriesused to return number of entries in the subsystem table.
et_offsetused to return the event table's page offset.
st_offsetused to return the subsystem table's page offset.
cb_widthreturns the current cumulative buffer interval width.
mb_sizereturns the size of the monitored buffers,
mb_entriesreturns the maximum number of entries in a monitored buffer.
mb_cpusreturns the number of allocated monitored buffers (or supported CPUs).
The etap_get_info interface provides the user space etap server or daemon with configuration and location information pertaining to the kernel's internal ETAP buffers; this information enables the caller to properly map the ETAP buffers and tables into its address space. When mapping is successfully completed, the Server displays the ETAP configuration on the console. The configuration output will resemble the following:
ETAP configuration [ee:108 se:8 eo:a60 so:acc cw:0 ms:1008008 me:36 mc:1]
ETAP event table mapped
ETAP subsystem table mapped
ETAP monitored buffer #0 mapped
The values between the brackets correspond with the arguments returned by the etap_get_info call (listed above). For example, "ee:108" indicates that the event table contains 108 ETAP event types and "mc:1" indicates that one monitored buffer has been allocated.
KERN_SUCCESS The call was performed successfully.
Functions: etap_probe, etap_trace_thread, etap_trace_event, etap_get_info.