In 653 cold start and warm start map to a restartProcess API call. Part 5 specifies that initialized data and bss are reinitialized in both scenarios. However, persistent data/bss is left intact for a warm start and initialized for a cold start. It appears that some Ada implementations using GCC have a notion of persistent bss: https://gcc.gnu.org/ml/gcc-patches/2012-05/msg00237.html The Daube evaluation customer would desire persistent data/bss to support a faster warm start as provided by their current vendor. I believe the kernel would need an indication that a warm start is desired, and then support the .persistent.data/.bss sections appropriately. When this PCR is worked, a PCR for the 653 runtime should be created to take advantage of this feature and provide 653 WARM_START.
CCB visited this PCR on 2014-06-12.
CCB visited this PCR on 2014-07-14
CCB 2 visited this PCR on 2014-11-11
CCB visited this PCR on 2014-11-17
CCB visited this PCR on 2016-04-18
CCB visited this PCR on 2016-06-20
CCB visited this PCR on 2017-02-01-59501
CCB visited this PCR on 2017-06-28-69227
CCB visited this PCR on 2017-07-06-58325
CCB visited this PCR on 2018-03-06-71236
CCB visited this PCR on 2021-03-26-57787
CCB visited this PCR on 2021-04-05-59141
CCB visited this PCR on 2023-08-14-64795
PCR to remain on HOLD for Kismet, as no customer requesting this feature.