Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Separation of Non-Functional Logic from Functional Logic

IP.com Disclosure Number: IPCOM000103443D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Related People

Brey, TM: AUTHOR [+3]

Abstract

In many designs, a component has multi-functions integrated within the same package. In some cases, the high level function may be separated into several functional parts; however, their failure characteristics are as if they were independent elements.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 90% of the total text.

Separation of Non-Functional Logic from Functional Logic

      In many designs, a component has multi-functions integrated
within the same package.  In some cases, the high level function may
be separated into several functional parts; however, their failure
characteristics are as if they were independent elements.

      Within functions, there are many sub-functions that are put
there for service, instrumenting, recovery, error collection,
performance or others that provide no customer function yet because
they are integrated with the main execution element, when they fail,
the main element also fails.

      This design provides the capability to separate these lower
level non-customer functions so that their failures do not cause the
main execution element to also fail.

      This is done by providing logic that brings out the error
reporting mechanism and signals to a separate interrupt mechanism.
Errors then are retried, and the error condition reset; however, if
the error continues to fail, a mask register is set that inhibits the
further reporting of this error and causes the logic to inhibit the
logic to set the error.  For error data itself (error trigger
status), it can be brought out to a separate error register that is
collected after the logic is recovered, then the error register is
reset and enabled to collect the next error. The error collection
logic is also maskable if it fails.  In this manner, the execution
element will not be interr...