# US 2017/0364365 A1 · Multiprocessor initialization via firmware configuration

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

- Number: US 2017/0364365 A1
- Document ID: US20170364365A1
- Status: Published application
- Kind: A1
- Application number: 15/183,192
- Filed: 2016-06-15
- Published: 2017-12-21
- Earliest claimed: 2016-06-15
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Andrei WARKENTIN; Harvey TUCH; Cyprien LAPLACE; Alexander FAINKICHEN
- Web page: https://patentgrep.com/patent/US20170364365A1

## CPC

- G06F 9/4405: {Initialisation of multiprocessor systems}
- G01D 11/30: Supports specially adapted for an instrument; Supports specially adapted for a set of instruments
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/4403: {Processor initialisation}
- G06F 12/0842: for multiprocessing or multitasking
- H04N 23/55: Optical parts specially adapted for electronic image sensors; Mounting thereof
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G01D: MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

An example method of initializing a plurality of processors in a hardware platform of computing device for use by system software executing on the hardware platform includes: parsing a descriptor table that has been loaded into memory from firmware to identify an original boot protocol for initializing at least one secondary processor of the plurality of processors; creating at least one mailbox structure in the memory associated with the at least one secondary processor; causing the at least one secondary processor to execute secondary processor initialization code stored in the memory, the secondary processor initialization code implementing a mailbox-based boot protocol that uses the at least one mailbox structure to initialize the at least one secondary processor; and modifying the descriptor table to identify the mailbox-based boot protocol for initializing the at least one secondary processor in place of the original boot protocol.

## Claims

### Claim 1

A method of initializing a plurality of processors in a hardware platform of computing device for use by system software executing on the hardware platform, the method comprising:
parsing a descriptor table that has been loaded into memory from firmware to identify an original boot protocol for initializing at least one secondary processor of the plurality of processors, the plurality of processors including a primary processor and the at least one secondary processor;
creating at least one mailbox structure in the memory associated with the at least one secondary processor;
causing the at least one secondary processor to execute secondary processor initialization code stored in the memory, the secondary processor initialization code implementing a mailbox-based boot protocol that uses the at least one mailbox structure to initialize the at least one secondary processor; and
modifying the descriptor table to identify the mailbox-based boot protocol for initializing the at least one secondary processor in place of the original boot protocol.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
allocating a portion of the memory to store the at least one mailbox structure and the secondary processor initialization code; and
marking the allocated portion of the memory as being in use by the firmware.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
copying the secondary processor initialization code to the allocated portion of the memory by a bootloader of the system software.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of creating the at least one mailbox structure comprises:
storing an identifier of a respective one of the at least one secondary processor in a respective one of the at least one mailbox structure; and
storing a jump address in each of the at least one mailbox structure that refers to designated code of the system software.

### Claim 5 (depends on 1)

The method of claim 1, wherein the secondary processor initialization code is configured to implement the mailbox-based boot protocol by causing each of the at least one secondary processor to sleep until receiving an interrupt and, in response to the interrupt, accessing a respective one of the at least one mailbox structure.

### Claim 6 (depends on 1)

The method of claim 1, wherein the step of causing the at least one secondary processor to execute the secondary processor initialization code comprises:
invoking an interface of the firmware to control each the at least one secondary processor to begin executing the secondary processor initialization code.

### Claim 7 (depends on 1)

The method of claim 1, wherein the step of modifying the descriptor table comprises:
modifying an boot protocol identifier field to indicate the mailbox-based boot protocol in place of the original boot protocol;
modifying at least one mailbox pointer field to refer to the at least one mailbox structure; and
updating a checksum field of the descriptor table based the modification of the boot protocol identifier field and the at least one mailbox pointer field.

### Claim 8

A non-transitory computer readable medium comprising instructions to be executed in a computing device to cause the computing device to carry out a method of initializing a plurality of processors in a hardware platform of the computing device for use by system software executing on the hardware platform, the method comprising:
parsing a descriptor table that has been loaded into memory from firmware to identify an original boot protocol for initializing at least one secondary processor of the plurality of processors, the plurality of processors including a primary processor and the at least one secondary processor;
creating at least one mailbox structure in the memory associated with the at least one secondary processor;
causing the at least one secondary processor to execute secondary processor initialization code stored in the memory, the secondary processor initialization code implementing a mailbox-based boot protocol that uses the at least one mailbox structure to initialize the at least one secondary processor; and
modifying the descriptor table to identify the mailbox-based boot protocol for initializing the at least one secondary processor in place of the original boot protocol.

### Claim 9 (depends on 8)

The non-transitory computer readable medium of claim 8, further comprising:
allocating a portion of the memory to store the at least one mailbox structure and the secondary processor initialization code; and
marking the allocated portion of the memory as being in use by the firmware.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, further comprising:
copying the secondary processor initialization code to the allocated portion of the memory by a bootloader of the system software.

### Claim 11 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the step of creating the at least one mailbox structure comprises:
storing an identifier of a respective one of the at least one secondary processor in a respective one of the at least one mailbox structure; and
storing a jump address in each of the at least one mailbox structure that refers to designated code of the system software.

### Claim 12 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the secondary processor initialization code is configured to implement the mailbox-based boot protocol by causing each of the at least one secondary processor to sleep until receiving an interrupt and, in response to the interrupt, accessing a respective one of the at least one mailbox structure.

### Claim 13 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the step of causing the at least one secondary processor to execute the secondary processor initialization code comprises:
invoking an interface of the firmware to control each the at least one secondary processor to begin executing the secondary processor initialization code.

### Claim 14 (depends on 8)

The non-transitory computer readable medium of claim 8, wherein the step of modifying the descriptor table comprises:
modifying an boot protocol identifier field to indicate the mailbox-based boot protocol in place of the original boot protocol;
modifying at least one mailbox pointer field to refer to the at least one mailbox structure; and
updating a checksum field of the descriptor table based the modification of the boot protocol identifier field and the at least one mailbox pointer field.

### Claim 15

A computing device including a hardware platform and system software, the hardware platform including a primary processor and at least one secondary processor, wherein the primary processor executes the system software to initialize the at least one secondary processor, by carrying out the steps of:
parsing a descriptor table that has been loaded into memory from firmware to identify an original boot protocol for initializing at least one secondary processor of the plurality of processors, the plurality of processors including a primary processor and the at least one secondary processor;
creating at least one mailbox structure in the memory associated with the at least one secondary processor;
causing the at least one secondary processor to execute secondary processor initialization code stored in the memory, the secondary processor initialization code implementing a mailbox-based boot protocol that uses the at least one mailbox structure to initialize the at least one secondary processor; and
modifying the descriptor table to identify the mailbox-based boot protocol for initializing the at least one secondary processor in place of the original boot protocol.

### Claim 16 (depends on 15)

The device of claim 15, wherein the steps carried out by the primary processor further comprise:
allocating a portion of the memory to store the at least one mailbox structure and the secondary processor initialization code; and
marking the allocated portion of the memory as being in use by the firmware.

### Claim 17 (depends on 15)

The device of claim 15, wherein the step of creating the at least one mailbox structure comprises:
storing an identifier of a respective one of the at least one secondary processor in a respective one of the at least one mailbox structure; and
storing a jump address in each of the at least one mailbox structure that refers to designated code of the system software.

### Claim 18 (depends on 15)

The device of claim 15, wherein the secondary processor initialization code is configured to implement the mailbox-based boot protocol by causing each of the at least one secondary processor to sleep until receiving an interrupt and, in response to the interrupt, accessing a respective one of the at least one mailbox structure.

### Claim 19 (depends on 15)

The device of claim 15, wherein the step of causing the at least one secondary processor to execute the secondary processor initialization code comprises:
invoking an interface of the firmware to control each the at least one secondary processor to begin executing the secondary processor initialization code.

### Claim 20 (depends on 15)

The device of claim 15, wherein the step of modifying the descriptor table comprises:
modifying an boot protocol identifier field to indicate the mailbox-based boot protocol in place of the original boot protocol;
modifying at least one mailbox pointer field to refer to the at least one mailbox structure; and
updating a checksum field of the descriptor table based the modification of the boot protocol identifier field and the at least one mailbox pointer field.
