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

Managing Interrupts in a Programming Interface

IP.com Disclosure Number: IPCOM000061515D
Original Publication Date: 1986-Aug-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 1 page(s) / 13K

Publishing Venue

IBM

Related People

Wilson, JH: AUTHOR

Abstract

A method is described which provides for control of interrupts by multiple concurrent applications on a Personal Computer (PC) subsystem. The PC subsystem comprises a PC adapter card and software subsystem whose functions are divided into a base set of functions to manage resources and a number of function sets, some subset of which can be concurrently active. A function set is activated by connecting it to an I/O port. This causes the implementation code to be down-loaded onto the adapter card. Associated with each function set is a number of interrupt conditions that can be generated when the function set is active. These interrupt conditions are identified with a mask, unique to the function set, in which each interrupt condition is associated with a particular bit in the mask.

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

Page 1 of 1

Managing Interrupts in a Programming Interface

A method is described which provides for control of interrupts by multiple concurrent applications on a Personal Computer (PC) subsystem. The PC subsystem comprises a PC adapter card and software subsystem whose functions are divided into a base set of functions to manage resources and a number of function sets, some subset of which can be concurrently active. A function set is activated by connecting it to an I/O port. This causes the implementation code to be down-loaded onto the adapter card. Associated with each function set is a number of interrupt conditions that can be generated when the function set is active. These interrupt conditions are identified with a mask, unique to the function set, in which each interrupt condition is associated with a particular bit in the mask. When a function set is activated, all its interrupt conditions are disabled, and no interrupt service routine is established. Thus, if a condition exists, it is ignored. Interrupts are enabled and disabled with the MASKINT function to the particular function set. MASKINT (RCB, function set, interrupt_mask) where "RCB" is the handle to the OPEN resource control block, "function set" is the ID corresponding to an active function set, and "interrupt_mask" is a bit mask whose structure is unique to the function set. For each one-bit in the mask, the corresponding condition is enabled; for each zero bit, the corresponding condition is disabled. The function set must have been activated using the specified RCB. When an interrupt condition occurs in an active function set, and the condition is enabled, a status bit is set on in a mask with the same structure as the interrupt mask. At the same time, the status may be stored to further qualify the condition. If no service routine is established for the condition, the function set continues and may record a number of different interrupt conditions before the function set...