The locking / pinning mechanism moved from the FRMTE to the PTE/PGSTE as of 5.2.0 as part of the support for HPMA (a hardware page fault assist allow ing hardware pinning) and QDIO passthrough. A page being locked by command i s now indicated by the PGSCPLOK bit in byte 6 of the PGSTE (see also PGSD98 LK for Diag x'98' locking).
Yes, the PGMBK stays resident as long as the page stays locked (in some cases, even after the virtual megabyte has been released). - Bill Holder, z/VM Development, IBM On Thu, 11 Dec 2008 01:05:47 +0100, Rob van der Heij <[EMAIL PROTECTED]> wrote: >On Thu, Dec 11, 2008 at 12:22 AM, David Kreuter ><[EMAIL PROTECTED]> wrote: > >> The frametable entries do not have an obvious bit indicating that the page >> is a target of a CP lock. I'll keep digging. >> I'm going to as time permits hunt down through the virtual machine pgm bk's. >> David > >So you can tell how long ago it was that I cared. I believe 5.1 still >had X'40' as FRMCPLOK >My apologies for providing out-of-date guidance. If I have the picture >right, then the PGMBK would still be resident as long as one of the >pages is resident, even though it now does not live under the bar >anymore. > >-Rob >======================== ========================= ========================
