System, method, and apparatus for processor detection in a pre-boot execution environment

• US 7,882,345 B1
• Filed: 09/29/2007
• Issued: 02/01/2011
• Est. Priority Date: 09/19/2007
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Christensen, Michael J.
• Primary Examiner(s): Lee; Thomas
• Assistant Examiner(s): Choudhury; Zahid
• Application Number:
  US11/864,993
• Time in Patent Office: 1,221 Days
• Field of Search: 713/1, 713/2, 709/217, 709/220
• US Class Current: 713/2
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]

Abstract

The disclosure is directed to systems and methods for processor detection in a pre-boot execution environment. In one example, a client initiates a boot process by transmitting a pre-boot image request identifying the client'"'"'s processor architecture. A boot server replies to the request and transmits a non-booting image configured to precisely determine the processor installed on the client. The non-booting image then initiates a second pre-boot image request including the precise identification of the processor installed on the client. The boot server may then proceed with the boot process, transmitting subsequent boot code precisely configured for the installed processor.

Claims

1. A system for booting a client, the system comprising:

a client configured to initiate a pre-boot image request in response to a boot command, the pre-boot image request comprising a data field for communicating a processor architecture for the client;

a boot server configured to provide a non-booting image in response to a first pre-boot image request from the client, the first pre-boot image request comprising an architecture identifier that may be imprecise;

the non-booting image configured to query the client and determine a precise processor architecture for the client;

the non-booting image further configured to reset a boot process for the client and thereby initiate a second pre-boot image request from the client wherein the second pre-boot image request comprises an architecture identifier that is precise;

the boot server further configured to provide a pre-boot image to the client that corresponds to the architecture identifier that is precise in response to the second pre-boot image request; and

the boot server further configured to provide a boot image to the client that corresponds to the architecture identifier that is precise in response to a boot image request comprising the architecture identifier that is precise.

2. The system of claim 1, wherein the pre-boot image request is made in compliance with the PXE boot protocol.

3. The system of claim 1, wherein resetting the boot process comprises setting a PXE boot item field to zero.

4. The system of claim 1, wherein the architecture identifier that is precise identifies a 64 bit processor.

5. The system of claim 1, wherein the architecture identifier that may be imprecise identifies a 32 bit processor.

6. The system of claim 1, wherein the boot server supports the DHCP protocol.

7. The system of claim 1, wherein the preboot image is a level 0 PXE image.

8. A method for booting a client, the method comprising:

receiving, from a client, a first pre-boot image request in response to a boot command, the first pre-boot image request comprising a data field for communicating a processor architecture for the client, the first pre-boot image request comprising an architecture identifier that may be imprecise;

providing a non-booting image to the client in response to the first pre-boot image request, wherein;

the non-booting image is configured to query the client and determine a precise processor architecture for the client,

the non-booting image is further configured to reset a boot process for the client and thereby initiate a second pre-boot image request from the client, the second pre-boot image request comprising an architecture identifier that is precise;

providing a pre-boot image to the client in response to the second pre-boot image request, the pre-boot image corresponding to the architecture identifier that is precise in response to the second pre-boot image request;

providing a boot image to the client in response to a boot image request, the boot image corresponding to the architecture identifier that is precise in response to the second pre-boot image request.

9. The method of claim 8, wherein the architecture identifier that may be imprecise identifies a 32 bit processor.

10. The method of claim 8, wherein the architecture identifier that is precise identifies a 64 bit processor.

11. The method of claim 8, wherein the pre-boot image request is made in compliance with the PXE boot protocol.

12. The method of claim 8, wherein the preboot image is a level 0 PXE image.

13. An apparatus for booting a client, the apparatus comprising:

a non-booting image download module configured to;

receive, from a client, a first pre-boot image request in response to a boot command, the first pre-boot image request comprising a data field for communicating a processor architecture for the client, the first pre-boot image request comprising an architecture identifier that may be imprecise;

provide a non-booting image to the client in response to the first pre-boot image request, wherein;

the non-booting image is configured to query the client and determine a precise processor architecture for the client,

the non-booting image is further configured to reset a boot process for the client and thereby initiate a second pre-boot image request from the client, the second pre-boot image request comprising an architecture identifier that is precise;

a pre-boot image download module configured to provide a pre-boot image to a client;

a boot image download module configured to provide a boot image to a client;

an image selection module configured to;

activate the pre-boot image download module in response to the second pre-boot image request from the client,

activate the boot image download module in response to a boot image request from the client.

14. The apparatus of claim 13, wherein the non-booting image download module is further configured to support the DHCP protocol.

15. The apparatus of claim 13, wherein the precise processor architecture is a 64 bit architecture.