IP Library Granted Patent US 7,243,222
Granted Patent B2
US 7,243,222 · App. 10/877,218 · Granted Jul 10, 2007

Storing data related to system initialization in memory while determining and storing data if an exception has taken place during initialization

Assignee: Intel Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,243,222
App. No.
10/877,218
Granted
Jul 10, 2007
Kind
B2
Abstract

A method of storing data related to system initialization in a data hub in a manner which provides accessibility to the data in either the pre-boot environment or the run-time environment.

Claims (61)

1. A method comprising:

performing a system initialization of a system;

storing data related to the system initialization in a data hub in a system memory;

determining if an exception has taken place during the system initialization, and if so, reading data hub data from the data hub and writing the data hub data to a non-volatile target; and

exporting the data hub data from the data hub to an operating system (O/S) accessible location.

2. The method of claim 1 , wherein performing a system initialization comprises: in a pre-boot environment, preparing system hardware, discovering the system memory and initializing a chipset.

3. The method of claim 1 , wherein the data related to the system initialization comprises state data, warning data, and error data.

4. The method of claim 1 , further comprising launching an error viewer to view the data hub data.

5. The method of claim 1 , further comprising sending an alert broadcast over a network to indicate that an error has occurred.

6. The method of claim 1 , further comprising sending the data hub data from the non-volatile target to a remote system.

7. The method of claim 1 , wherein the non-volatile target comprises a hard disk.

8. The method of claim 1 , wherein the non-volatile target comprises flash memory.

9. The method of claim 1 , wherein exporting the data from the data hub to the O/S accessible location comprises exporting the data to one of: an ACPI SSDT record and an EFI configuration table.

10. The method of claim 1 , wherein exporting the data from the data hub to the O/S accessible location occurs upon a transition to an O/S runtime environment.

11. The method of claim 1 , further comprising accessing the exported data from an O/S.

12. The method of claim 11 , further comprising using the data to debug the system.

13. An article comprising a machine-accessible medium having stored thereon instructions that, when executed by a machine, cause the machine to log state data by:

performing a system initialization;

storing data related to the system initialization in a data hub in a system memory;

determining if an exception has taken place during the system initialization, and if so, reading data hub data from the data hub and writing the data hub data to a non-volatile target; and

exporting the data hub data from the data hub to an operating system (O/S) accessible location.

14. The article of claim 13 , wherein the instructions, when executed by the machine, further cause the machine to export the data from the data hub to the O/S accessible location upon transition to an O/S runtime environment.

15. A system, comprising:

a bus;

a processor coupled to the bus;

a video interface device coupled to the bus; and

memory coupled to the processor, the memory adapted for storing instructions, which upon execution by the processor, cause:

a system initialization to occur;

data related to the system initialization to be stored in a data hub in system memory;

data hub data to be read from the data hub and written to a non-volatile target if an exception occurs during the system initialization; and

the data hub data from the data hub to be exported to an O/S accessible location.

16. The system of claim 15 , further comprising instructions to cause the machine to export the data from the data hub to the O/S accessible location upon transition to an O/S runtime environment.

17. The system of claim 16 , further comprising instructions to access the exported data from an O/S.

18. A method comprising:

initializing a system and installing an exception handler;

initializing a data hub repository in system memory for data hub records;

registering an entry point of the data hub records in the data hub repository with the exception handler;

determining if an exception has occurred, and if so, reading each data hub record and writing the contents to a non-volatile target;

determining if state information has been exported, and if so, building data hub record data; and

determining if the system is transitioning to an O/S run-time environment, and if so, and exporting the data hub record information.

19. The method of claim 18 , wherein the non-volatile target comprises a hard-disk drive.

20. The method of claim 18 , wherein the non-volatile target comprises flash memory.

21. The method of claim 18 , further comprising enacting a system policy if an exception has occurred.

22. The method of claim 21 , wherein enacting a system policy comprises sending the contents of the data hub to a display for viewing.

23. The method of claim 18 , further comprising accessing the exported data hub record information from an O/S.

24. An article comprising a machine-accessible medium having stored thereon instructions that, when executed by a machine, cause the machine to log state data by:

initializing a system and installing an exception handler;

initializing a data hub repository in system memory for data hub records;

registering the entry point of the data hub records in the data hub repository with the exception handler;

determining if an exception has occurred, and if so, reading each data hub record and writing the contents to a non-volatile target;

determining if state information has been exported, and if so, building data hub record data;

determining if the system is transitioning to an O/S run-time environment, and if so, and exporting the data hub record information.

25. The article of claim 24 , wherein the instructions, when executed by the machine, further cause the machine to enact a system policy if an exception has occurred.

26. The article of claim 24 , wherein the instructions, when executed by the machine, further cause the machine to access the exported data hub record information from an O/S.

27. A system, comprising:

a bus;

a processor coupled to the bus;

a video interface device coupled to the bus; and

memory coupled to the processor, the memory adapted for storing instructions, which upon execution by the processor, cause a system to be initialized, an exception handler to be installed, a data hub repository for data hub records to be initialized in system memory, an entry point of the data hub records in the data hub repository to be registered with the exception handler, a determination to be made whether an exception has occurred, and if so, reading data hub data from the data hub repository and writing the data hub data to a non-volatile target; a determination to be made whether state information has been exported, and if so, building data hub record data, and a determination to be made whether the system is transitioning to an O/S run-time environment, and if so, and exporting the data hub record information.

28. The system of claim 27 , further comprising instructions to cause the machine to enact a system policy if an exception has occurred.

29. The system of claim 27 , further comprising instructions to cause the machine to enact to access the exported data hub record information from an O/S.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 24, 2004
From: ROTHMAN, MICHAEL A.; ZIMMER, VINCENT J.
To: INTEL CORPORATION
Reel/Frame 015525/0092 →
Continuity (1)
Related Publication 20050289333A1 · Dec 29, 2005