Browse Prior Art Database

Methods And Process For Generating Hardware Object Model In A Computer System

IP.com Disclosure Number: IPCOM000237061D
Publication Date: 2014-May-29
Document File: 2 page(s) / 28K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method for generating a hardware object model from machine readable content in a form readable by a service processor allowing the service processor to boot the system is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 47% of the total text.

Page 01 of 2

Methods And Process For Generating Hardware Object Model In A Computer System

Disclosed is a method for generating a hardware object model from machine readable content in a form readable by a service processor allowing the service processor to boot the system.

The disclosed method solves the general problem of aggregating a machine readable workbook (MRW) [i.e. software digestible] description of a computer system's possible hardware configuration and related system policies (typically provided by a hardware design team), combining it with service processor firmware specific customization's, and processing that information into a logical representation of the system. This logical representation of the system (or "object model") is made available to a service processor firmware, such that the firmware can then query/manipulate that logical view to boot the system.

The firmware design team for a computer system models and defines types of logical parts within a system (a "type" a.k.a. "target" as some logical representation of hardware of interest to firmware, and various types of attributes can be associated with each target type). The definition along with a machine readable blueprint is provided by a hardware design team (as well as firmware/hardware team customization's), to produce a light-weight, data driven, logical view of the system tailored to the needs of the firmware responsible for initializing the computer system.

In an embodiment of the disclosed method may have the following elements as part of the system:
1) Machine readable data files defining types of "attributes" (including size, whether it's an array, persistency, etc.) that are possible for firmware to access

Override capabilities. All attribute types can have default values (or none


a.

specified -- forced to be specified elsewhere). The default value of an attribute type can be overridden when it is mapped to a specific target type (or it can be overridden by any derived target type). Further, it can finally be overridden when a target type is instantiated.


2) Machine readable data files that define which "targets" are of interest to the firmware. Each attribute type (from 1 above) maps to one or more target types

Inheritance capabilities. Any target type can derive from an existing target type.


a.

    Any attribute type associated with a target type at a more senior level of the hierarchy is inherited
Taking 1+2 together, it's possible to represent any combination of "things of interest" in a computer system, and for each one, a highly customized set of properties.

3) Machine readable maximum hardware (blueprint) configuration
4) Machine readable system specific set of policies
5) Parser which aggregates parts of interest from 3) + 4) to produce a view of the possible computer system configuration tailored to firmware
6) Parser to convert all parts given by 5) into corresponding target instances, using information from 1) and 2) to compute the attribute values (unl...