# US 2022/0027164 A1 · Fast boot

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0027164 A1
- Document ID: US20220027164A1
- Status: Published application
- Kind: A1
- Application number: 17/494,113
- Filed: 2021-10-05
- Published: 2022-01-27
- Earliest claimed: 2017-11-14
- Assignees: TidalScale, Inc.
- Applicants: TidalScale, Inc.
- Inventors: David P. Reed; Isaac R. Nassi; Pete Jarvis
- Web page: https://patentgrep.com/patent/US20220027164A1

## CPC

- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/4403: {Processor initialisation}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/4856: {resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence)}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 12/0815: Cache consistency protocols
- G06F 12/1009: using page tables, e.g. page table structures
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F 2212/1016: Performance improvement
- G06F 2212/205: Hybrid memory, e.g. using both volatile and non-volatile memory
- G06F 2212/263: Network storage, e.g. SAN or NAS
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Initializing a computing system using dormant pages includes marking a set of guest physical addresses as dormant. It further includes, for each node in a plurality of physical nodes, designating a set of real physical addresses for zeroing. An operating system is executing collectively across the physical nodes.

## Claims

### Claim 1

A computer system, comprising:
a plurality of physically interconnected computing nodes, wherein a guest operating system is run on a virtual environment that is defined by a set of hyper-kernels running on the plurality of physically interconnected computing nodes;
wherein a guest physical address is marked as dormant, and wherein the guest physical address is owned by a first computing node; and
wherein the guest physical address is migrated from the first computing node to a second computing node, and wherein migrating the guest physical address comprises transmitting a message indicating that the guest physical address is dormant.

### Claim 2 (depends on 1)

The computer system of claim 1, wherein the guest physical address is indicated to be dormant based at least in part on a dormant bit associated with the guest physical address being set.

### Claim 3 (depends on 1)

The computer system of claim 1, wherein the dormant bit is included in a page table, and wherein the page table includes metadata information associated with guest physical addresses.

### Claim 4 (depends on 1)

The computer system of claim 1, wherein the guest physical address is marked as dormant in response to detecting that a page of physical memory mapped to the guest physical address comprises a page of zeroes.

### Claim 5 (depends on 1)

The computer system of claim 1, wherein the guest physical address is marked as dormant in response to detecting that the guest physical address has requested a page of physical memory mapped to the guest physical address.

### Claim 6 (depends on 1)

The computer system of claim 1, wherein contents of a page of physical memory mapped to the guest physical address marked as dormant are not transmitted.

### Claim 7

A method, comprising:
marking a guest physical address as dormant, wherein the guest physical address is owned by a first computing node, wherein the first computing node is included in a plurality of physically interconnected computing nodes, and wherein a guest operating system is run on a virtual environment that is defined by a set of hyper-kernels running on the plurality of physically interconnected computing nodes; and
migrating the guest physical address from the first computing node to a second computing node, wherein migrating the guest physical address comprises transmitting a message indicating that the guest physical address is dormant.

### Claim 8 (depends on 7)

The method of claim 7, wherein the guest physical address is indicated to be dormant based at least in part on a dormant bit associated with the guest physical address being set.

### Claim 9 (depends on 7)

The method of claim 7, wherein the dormant bit is included in a page table, and wherein the page table includes metadata information associated with guest physical addresses.

### Claim 10 (depends on 7)

The method of claim 7, wherein the guest physical address is marked as dormant in response to detecting that a page of physical memory mapped to the guest physical address comprises a page of zeroes.

### Claim 11 (depends on 7)

The method of claim 7, wherein the guest physical address is marked as dormant in response to detecting that the guest physical address has requested a page of physical memory mapped to the guest physical address.

### Claim 12 (depends on 7)

The method of claim 7, wherein contents of a page of physical memory mapped to the guest physical address marked as dormant are not transmitted.
