Guardian Procedure Calls Reference Manual

IPUAFFINITY_CONTROL_ Procedure
Summary
Syntax for C Programmers
Syntax for TAL Programmers
Parameters
Returned Value
Considerations
Example
Summary
The IPUAFFINITY_CONTROL_ procedure controls scheduling features which are not associated
with a single process. It can also clear all the settings as well as all the process-to-IPU associations,
thus bringing the system or CPU back to its initial state with respect to process scheduling.
The term soft affinity used below refers to all processes other than DP2 processes or system processes
known as Interrupt Processes (IPs) or Auxiliary Processes (APs). See also attribute 136 of
PROCESS_GETINFOLIST_ which can be used to obtain the affinity class of the process.
NOTE: This procedure can only be called only from native processes, beginning with the J06.12
RVU. It is present in H-series RVUs beginning with H06.23, but is meaningful only for J-series RVUs
when more than one IPU is present in the target CPU. (This procedure is present in the J06.11 and
H06.22 RVUs, but was not yet supported.)
Syntax for C Programmers
#include <ktdmtyp.h>
#include "$system.zguard.dipuaff.h"
int16 IPUAFFINITY_CONTROL_ ( int16 TargetCPU
,uint64 controlFlagsMask
,uint64 controlFlagsSetting
,uint64 *previousControlFlags );
• The header file dipuaff.h is distributed and optionally installed in the ZGUARD subvolume.
Syntax for TAL Programmers
?SOURCE $SYSTEM.ZGUARD.DIPUAFF(IPUAFFINITY_CONTROL_)
error := IPUAFFINITY_CONTROL_ ( TargetCPU ! i
,controlFlagsMask ! i
,controlFlagsSetting, ! i
,previousControlFlags ); ! o
• The header file DIPUAFF is distributed and optionally installed in the ZGUARD subvolume.
• The IPUAFFINITY_CONTROL_ procedure is only supported in pTAL; it is not supported in TAL.
736 Guardian Procedure Calls (H-K)