Branch Prediction Patch Management Guideline

Branch Prediction Patch Management 2.0 05/05/03
Hewlett-Packard Development Company L.P Page 3 of 5 CSSI Website
To disable patch persistence:
When you no longer want the patch to be active after a processor reload or cold start,
you must remove $ZBR from the kernel subsystem configuration so that DIAG2 does
not run again.
1. $ZBR must be in a stopped state to be removed. To stop $ZBR, at the TACL
prompt, enter this command as the super ID:
SCF ABORT PROCESS $ZZKRN.#ZBR
Note: The ABORT command does not make the patch inactive.
2. To remove DIAG2 from the kernel subsystem configuration after $ZBR stops, at
the TACL prompt, enter this command as the super ID:
SCF DELETE PROCESS $ZZKRN.#ZBR
The DELETE command does not make the patch inactive or remove DIAG2 from
the system. To make the patch inactive, you must run DIAG2 manually or use an
OBEY command file such as DISALL (please refer to the “Using the DIAG2
OBEY Files” section of this guideline).
3. To verify that DIAG2 was correctly removed from the kernel subsystem
configuration, at the TACL prompt, enter:
SCF INFO PROCEESS $ZZKRN.#ZBR
or
SCF STATUS PROCESS $ZZKRN.#ZBR
Neither command you enter should find the process in the kernel subsystem
configuration. An output message should indicate that the object is not found.
You can use the OBEY command file INSTBPM to reconfigure DIAG2 as $ZBR after an
SCF DELETE command has been processed.
Manually Managing the Patch
When you need additional control over the patch, you can:
• Run DIAG2 manually for a single processor in either an interactive or non-
interactive mode.
• Use a set of OBEY command files to automate the use of DIAG2 from TACL for
all processors.