Fast boot
摘要
說明書
In one embodiment, node_1 is instructed by node_0 (e.g., via a sent message) to set the dormant bit for GPA_34, thereby creating a dormant page (if GPA_34 is to be zeroed, then its contents are irrelevant). In one embodiment, creating the dormant includes updating the record in the internal page table for GPA_34, and marking the dormant bit (e.g., as true, indicating that the guest physical address is dormant, or using any other appropriate marker/indicator). The page of real physical memory that GPA_34 previously pointed to now becomes a free page that may be used for some other purpose. For example, the real address RPA_734 is placed on node_1's to be zeroed list (2312) (where its zeroing may be deferred). Between the time that the real physical page is unmapped from the guest physical addresses and the time that another dormant page uses the real page of physical memory, the real page of physical memory may be zeroed when there are spare processor cycles (e.g., as part of housekeeping performed by the hyper-kernel). The page may also be zeroed directly and added to a list of already zeroed pages. Another dormant page may use the real page, for example, when a non-zero value is being written into, and be converted/materialized, as described above.
Thus, the remote page on node_1 being zeroed on node_0 (where the zeroing instruction originated) may be remotely converted to dormant on node_1. The converted page may be left on node_1 or may be moved to node_0 after becoming dormant.
