USRE36394E - Device driver and adapter binding technique - Google Patents
Device driver and adapter binding technique Download PDFInfo
- Publication number
- USRE36394E USRE36394E US07/321,439 US32143989A USRE36394E US RE36394 E USRE36394 E US RE36394E US 32143989 A US32143989 A US 32143989A US RE36394 E USRE36394 E US RE36394E
- Authority
- US
- United States
- Prior art keywords
- operating system
- resource manager
- virtual resource
- drivers
- dependent information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/545—Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space
Definitions
- the present invention generally relates to computer operating systems running as Virtual Machines (VM) on a Virtual Resource Manager (VRM) and, more particularly, to a technique for binding the device drivers of an operating system to the corresponding real and virtual devices of the virtual resource manager.
- VM Virtual Machines
- VRM Virtual Resource Manager
- Virtual machine operating systems are known in the prior art which make a single real machine appear to be several machines. These machines can be very similar to the real machine on which they are run or they can be very different. While many virtual machine operating systems have been developed, perhaps the most widely used is VM/370 which runs on the IBM System/370. The VM/370 operating system creates the illusion that each of several users operating from terminals has a complete System/370. Moreover, each user can use a different operating system running under VM/370.
- Harvey M. Deitel entitled An Introduction to Operating Systems, published by Addison-Wesley (1984), and in particular to Chapter 22 entitled "VM: A Virtual Machine Operating System”. A more in depth discussion may be had by referring to the text book by Harold Lorin and Harvey M. Deitel entitled Operating Systems, published by Addison-Wesley (1981), and in particular to Chapter 16 entitled "Virtual Machines”.
- UNIX is a trademark of Bell Telephone Laboratories, Inc., which developed the operating system. It was originally developed for use on a DEC minicomputer but has become a popular operating system for a wide range of mini- and microcomputers.
- One reason for this popularity is that UNIX is written in C language, also developed at Bell Telephone Laboratories, rather than in assembly language so that it is not processor specific.
- compilers written for various machines to give them C capability make it possible to transport the UNIX operating system from one machine to another. Therefore, application programs written for the UNIX operating system environment are also portable from one machine to another.
- Physical devices such as printers, modems and the like, which are supported by the UNIX operating system appear as an entry in the /dev (for device) directory.
- Application programs running on UNIX handle devices as if they were files.
- the application program issues a system command to the file /dev/lp (for device, line printer). While the procedure is convenient for the applications programmer, the UNIX operating system programmer must write device driver programs so that the physical devices can communicate with the operating system.
- virtual resource manager In order to support a more dynamic system environment for UNIX as a Virtual Machine (VM) running on a Virtual Resource Manager (VRM), certain linkages must be made between the UNIX device drivers and the corresponding real and virtual devices in the virtual resource manager.
- virtual resource manager what is meant is that part of a virtual machine operating system which manages the resources that are connected to the computer, as will be understood by those skilled in the systems programming art. Again, reference may be had to the text books by Deitel and Lorin and Deitel mentioned above.
- This binding capability enables a programmer writing an interrupt handler for a new adapter being installed into the system to utilize and move devices on an adapter with minimal effort and not to have devices "wired" to a specific port.
- the virtual resource manager can be thought of as a sophisticated hardware interface, analogous to the BIOS (Basic Input/Output System) which is a relatively simple hardware interface.
- a "token” (Input/Output) Device Number (IODN) corresponding to the device is placed in the UNIX device driver.
- this token is used to define to the virtual resource manager the device, with adapter dependent information which includes a hardware port address for the physical device.
- a special file corresponding to the device has been created.
- the UNIX device driver retrieves the token for the device and "attaches" to the virtual resource manager. This causes the virtual resource manager device driver to use the adapter dependent information corresponding to the token and placed in the process stack.
- the UNIX device driver uses this token passed to it to communicate with the virtual resource manager device driver thereby accomplishing driver to driver binding. As a result, this burden is eliminated from the writer of the device driver programs.
- FIG. 1 is a block and flow diagram of the Virtual Resource Manager (VRM) device driver model
- FIG. 2 is a block and flow diagram of the relational structure of the virtual resource manager configuration VRMCONF according to the present invention
- FIG. 3 is a flow diagram showing the device driver and adapter binding technique according to the invention.
- FIG. 4 is a block and flow diagram illustrating the scenario for device/port binding for the specific example of a printer.
- the virtual resource manager consists of two basic types of components; processes and interrupt handlers. Processes are scheduled for execution through a prioritized round-robin algorithm. Interrupt handlers are divided into two types; First Level Interrupt Handlers (FLIHs) and Second Level Interrupt Handlers (SLIHs). There is only one FLIH per hardware interrupt level, and one SLIH per adapter on each interrupt level. Both processes and interrupt handlers can be installed from a virtual machine. Also, processes and interrupt handlers can be created by processes within the virtual resource manager. Basically, anything a virtual machine can do with Virtual Machine Interface (VMI) Supervisory Calls (SVCs), a virtual resource manager can do with function calls to the virtual resource manager nucleus.
- VMI Virtual Machine Interface
- SVCs Supervisory Calls
- the virtual machine When components and devices are installed into the virtual resource manager from a virtual machine, the virtual machine supplies identifying Input/Output Code Numbers (IOCNs) and identifying Input/Output Device Numbers (IODNs).
- IOCNs Input/Output Code Numbers
- IODNs Input/Output Device Numbers
- the virtual resource manager generates IODNs for newly created instances of virtual devices.
- components and devices are known by encoded identifications (IDs) which are generated by the virtual resource manager. These IDs are unique and dynamic; i.e., each time an IODN is defined by a virtual machine, the internal device identification will be different even though the IODN is static. Only programmers writting code for inside the virtual resource manager need be concerned with the internal identifications since they are not reflected above the virtual machine interface.
- FIG. 1 of the drawings there is shown a model of the virtual resource manager device driver.
- the virtual machine 10 is interfaced with the virtual resource manager driver 12 through a well defined virtual machine interface 14.
- the virtual machine 10 issues calls to define device supervisory calls (SVCs) and to attach device supervisory calls as represented by block 16, and in response to those calls, the virtual resource manager device driver 12 is initialized at block 122 and provides an virtual interrupt to the virtual machine 10.
- the virtual machine 10 also issues a call to start an input/output supervisory call as represented by block 18.
- the virtual resource manager device driver 12 This causes the virtual resource manager device driver 12 to check device parameters in block 126 and provide a return to the start input/output supervisory call block 18 which then causes the virtual resource manager device driver 12 to initiate input/output in block 124 and provide a virtual interrupt to the virtual machine 10.
- a virtual interrupt to the virtual machine 10 is also provided by the SLIH 128.
- the adpater 20 provides interrupts to the virtual resource manager device driver 12 and responds to input/output operation commands from the device driver 12 via the hardware interface 22.
- a device is defined at virtual resource manager initial program load time for virtual resource manager devices or when the operating system issues the appropriate "Define Device SVC".
- the device driver's define device routine is called at this time to disable the device's adapter (interrupts, DMA, and the like).
- the data passed to this routine is the Define Device Structure (DDS) specified with the "Define Device SVC".
- DDS Define Device Structure
- the DDS which is passed to the device driver's define device routine contains a device dependent area that provides the means by which the operating system can pass configuration information to the device driver.
- the define routine is responsible for copying this structure into its static data area and returning its address.
- Each device driver will define the parameters that must be contained in the DDS device characteristics section in response to a change characteristics operation.
- a device is initialized by the virtual resource manager by calling the "Start Device” routine. This occurs automatically each time a virtual machine 10 attaches a device.
- the device driver's initialization routine is called at this time to enable/initialize the device's adapter. By not initializing the device until it is attached saves system resources and allows a more flexible use of hardware resources. For example, two devices that do not support interrupt sharing could use the same interrupt level if they are not both active.
- a device is terminated by the virtual resource manager by calling the "Start Device” routine with the stop option. The device driver's termination routine is called at this time to disable the device's adapter. This allows the device to be allocated to a co-processor or resources used by the device to be allocated to other devices.
- UNIX device drivers in a non-virtual resource manager environment interface directly to the system hardware.
- several UNIX system files exist. These files fall into two categories; those required to "make” the UNIX kernel (system tables) and those that are constructed as the result of "making" a new kernel (binding tables).
- the present invention provides certain linkages between the UNIX device drivers and the corresponding real and virtual devices in the virtual resource manager. This linkage mechanism consists primarily of a convention by which both real and virtual devices are identified by a device number referred to as the IODN as described above.
- a mechanism is provided to communicate the IODN along with other information to the UNIX device driver as part of the normal UNIX initialization.
- VRMCONF virtual resource manager configuration
- the CONFIG.DD subcomponent 242 of VRMCONF is itself a device driver inside the UNIX kernel 24. As such, it is the part of VRMCONF which issues the virtual resource manager supervisory calls. It also is the mechanism by which the IODN and other information gets passed to the respective kernel device drivers. It passes this information via a kernel function call.
- the function call is initiated via the "CFDDRU" input/output control issued to the CONFIG.DD.
- the internal call, i.e. CONFIG.DD to kernel is of the following format:
- iodn the iodn to use for this device or 0 if not applicable
- ddptr a pointer to the device dependent information or 0 if none
- the /etc/master 26 is an ASCII text file containing information about every device the system is capable of supporting. There is at least one entry in this file for every real device. In the virtual resource manager environment, the same is still true, but in addition, there must be at least one entry for every virtual device (device manager).
- the /etc/system file 28 is also an ASCII text file. It contains information about every device driver on the UNIX file system. There is at least one entry in this file for each device driver. In the UNIX environment, there are both real and pseudo device drivers.
- a pseudo device driver has no real or virtual device associated with it. (Pseudo device drivers is one way to gain access to the VMI -- SVC -- calls.) Entries for these pseudo device drivers are required in the /etc/system file 28 in the virtual resource manager environment.
- CONF.C At least two tables are created as part of the UNIX kernel build operation.
- One is known as "CONF.C” 244 and the other as interrupt table 246.
- CONF.C The CONF.C table 244 is used by the kernel to locate each device driver (major number) and the routines that driver supports. It is a binding table which identifies each major device number and relates that driver to a set of system calls. For example, the UNIX system call OPEN /dev/devicel would be indexed through the CONF.C table to find the UNIX device driver to pass the call to as well as the specific routine to run as the result of the OPEN system call. This continues to be true in the virtual resource manager environment.
- CONF.C does not change. Additional binding information is added to provide pointers into UDD data areas.
- the interrupt table 246 is an interrupt vectoring table "made" with the kernel 24 in normal UNIX operation.
- the Virtual Interrupt Vector Table is shown below and represents information contained in the routine table:
- This table is not "static” built as part of the kernel build but is dynamically built at run-time.
- Each UNIX device driver must call the kernel function call to receive interrupt sub-level information while passing its major and minor number as well as a pointer to the interrupt handler routine.
- Every UNIX device driver follows certain conventions. While there is the concept of a predefined IODN, for some of the nucleus components of a virtual resource manager, the majority of the device/device manager tags (IODNs) will vary in assignment. Only the nucleus virtual resource manager components are allowed to default always to a specific IODN. Therefore, UNIX device drivers are not allowed to have "hardcode" device dependent information.
- Each UDD writer will have a table entry for each IODN it controls. If the UDD is a multiplexing device driver, i.e. deals with more than one IODN, the table must reflect this situation. An example of this is a UDD for controlling printers. This UDD perhaps might control multiple printers.
- the defined mechanism for handling this is the UNIX major device number which reflects the Printer UDD and the minor number which reflects the specific printer. Therefore, the size of the UDD table is directly proportional to the number of minor devices.
- this major/minor number combination is the mechanism by which the correct table entry in the associated UDD is updated.
- FIG. 3 the flow chart for the device driver and adapter binding according to the invention is shown.
- block 40 it is assumed that the user modifies the device configuration. To do this, the physical port number of the device connection must be specified in the table of adapter characteristics as indicated in block 42. Then, if the device is a new device, the flow progresses to block 46; otherwise, the flow progresses to block 54 as indicated by the decision block 44.
- block 46 the UNIX system configuration files /etc/master 26 and etc/system 28 are modified.
- a token (IODN) is assigned to the device.
- the device is defined to the virtual resource manager with modified adapter characteristics, including passing the token number for the device.
- the UNIX device driver is updated for device characteristics, including an identical token number for the device.
- the UNIX application "OPENS" the UNIX device driver to use the device in block 56.
- the UNIX device driver passes the device token number to the virtual resource manager.
- the virtual resource manager receives the token number, it passes a request to the associated virtual resource manager device driver for the corresponding token number as indicated in block 60.
- the virtual resource manager device driver uses adapter characteristics and port number corresponding to the device token number to drive the device thus completing the device driver and and adpater binding. Then, when the device is to be driven by an application, the device which has been set up by the user is requested via the UNIX device driver and the virtual resource manager device driver as indicated in block 64.
- a line printer 70 identified as LPT9 is to be attached to an RS232 serial adapter 72 having four ports identified by the tokens IODNl, IODN2, IODN3, and IODN4.
- the first step is to modify the /etc/system file 28 and the /etc/master file 26.
- the /etc/master file 26 contains all supported devices, irrespective of their configuration.
- step 2 the DDI (device dependent information) file may be modified for device or adpater parameters.
- step 3 the character special file is created for the line printer LPT9.
- step 4 with the initial program load (IPL) sequence to execute the VRMCONFIG program.
- step 5 the VRMCONFIG program passes device dependent information to the configuration (CONFIG) pseudo device driver.
- step 6 the CONFIG device driver makes known the virtual resource manager device driver code to the virtual resource manager, along with the token (IODN).
- step 7 the CONFIG device driver passes some device information to the UNIX device driver, along with the same token (IODN), which is stored in the table area of the UNIX device driver.
- an application program can "OPEN" the special file /dev/lpt9 created in step 3 as indicated in FIG. 4 at step 8. This causes, in step 9, the UNIX device driver to use the IODN (passed in step 7) to go to the virtual resource manager to "bind" to the virtual resource manager device driver corresponding to the same token and associated with the adapter port.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
An operating system in a digital computer environment is run as a virtual machine on a virtual resource manager. In order to provide a more dynamic environment for the operating system, linkages are made between the operating system device drivers and the corresponding real and virtual devices of the virtual resource manager. This is accomplished by assigning a "token" to the virtual resource manager. A device dependent information file corresponding to the device is created. This file contains adapter dependent information including a hardward port address for the physical device. The "token" is placed in the operating system device driver at the time it is initiated. When the operating system device driver is "opened" to drive the device, it uses the "token" to communicate with the virtual resource manager device driver thereby accomplishing driver to driver binding. This causes the virtual resource manager device driver to use the adapter dependent information in the special file corresponding to the "token" and placed in the process stack.
Description
The present invention generally relates to computer operating systems running as Virtual Machines (VM) on a Virtual Resource Manager (VRM) and, more particularly, to a technique for binding the device drivers of an operating system to the corresponding real and virtual devices of the virtual resource manager.
Virtual machine operating systems are known in the prior art which make a single real machine appear to be several machines. These machines can be very similar to the real machine on which they are run or they can be very different. While many virtual machine operating systems have been developed, perhaps the most widely used is VM/370 which runs on the IBM System/370. The VM/370 operating system creates the illusion that each of several users operating from terminals has a complete System/370. Moreover, each user can use a different operating system running under VM/370. For further background, the reader is referred to the text book by Harvey M. Deitel entitled An Introduction to Operating Systems, published by Addison-Wesley (1984), and in particular to Chapter 22 entitled "VM: A Virtual Machine Operating System". A more in depth discussion may be had by referring to the text book by Harold Lorin and Harvey M. Deitel entitled Operating Systems, published by Addison-Wesley (1981), and in particular to Chapter 16 entitled "Virtual Machines".
The invention to be described hereinafter is primarily intended for use with the UNIX operating system but may have application with other operating systems which have characteristics similar to the UNIX operating system. UNIX is a trademark of Bell Telephone Laboratories, Inc., which developed the operating system. It was originally developed for use on a DEC minicomputer but has become a popular operating system for a wide range of mini- and microcomputers. One reason for this popularity is that UNIX is written in C language, also developed at Bell Telephone Laboratories, rather than in assembly language so that it is not processor specific. Thus, compilers written for various machines to give them C capability make it possible to transport the UNIX operating system from one machine to another. Therefore, application programs written for the UNIX operating system environment are also portable from one machine to another. For more information on the UNIX operating system, the reader is referred to UNIX™ System, User's Manual, System V, published by Western Electric Co., January 1983. A good overview of the UNIX operating system is provided by Brian W. Kernighan and Rob Pike in their book entitled The UNIX Programming Environment, published by Prentice-Hall (1984).
Physical devices, such as printers, modems and the like, which are supported by the UNIX operating system appear as an entry in the /dev (for device) directory. Application programs running on UNIX handle devices as if they were files. To send characters to a line printer, for example, the application program issues a system command to the file /dev/lp (for device, line printer). While the procedure is convenient for the applications programmer, the UNIX operating system programmer must write device driver programs so that the physical devices can communicate with the operating system.
In order to support a more dynamic system environment for UNIX as a Virtual Machine (VM) running on a Virtual Resource Manager (VRM), certain linkages must be made between the UNIX device drivers and the corresponding real and virtual devices in the virtual resource manager. By virtual resource manager, what is meant is that part of a virtual machine operating system which manages the resources that are connected to the computer, as will be understood by those skilled in the systems programming art. Again, reference may be had to the text books by Deitel and Lorin and Deitel mentioned above.
It is therefore an object of the present invention to provide a scheme for dynamically binding the UNIX device drivers to the virtual resource manager device drivers. This binding capability enables a programmer writing an interrupt handler for a new adapter being installed into the system to utilize and move devices on an adapter with minimal effort and not to have devices "wired" to a specific port. In the environment to be described in more detail hereinafter, the virtual resource manager can be thought of as a sophisticated hardware interface, analogous to the BIOS (Basic Input/Output System) which is a relatively simple hardware interface.
According to the invention, a "token" (Input/Output) Device Number (IODN) corresponding to the device is placed in the UNIX device driver. At the program initiation time (Initial Program Load or IPL), this token is used to define to the virtual resource manager the device, with adapter dependent information which includes a hardware port address for the physical device. A special file corresponding to the device has been created. When this special file is opened, the UNIX device driver retrieves the token for the device and "attaches" to the virtual resource manager. This causes the virtual resource manager device driver to use the adapter dependent information corresponding to the token and placed in the process stack. Thus, when the UNIX device driver is "opened" to drive a device, it uses this token passed to it to communicate with the virtual resource manager device driver thereby accomplishing driver to driver binding. As a result, this burden is eliminated from the writer of the device driver programs.
The foregoing and other objects, aspects and advantages of the invention will be better understood from the following detailed description with reference to the drawings, in which:
FIG. 1 is a block and flow diagram of the Virtual Resource Manager (VRM) device driver model;
FIG. 2 is a block and flow diagram of the relational structure of the virtual resource manager configuration VRMCONF according to the present invention;
FIG. 3 is a flow diagram showing the device driver and adapter binding technique according to the invention; and
FIG. 4 is a block and flow diagram illustrating the scenario for device/port binding for the specific example of a printer.
In the environment in which the invention is used, the virtual resource manager consists of two basic types of components; processes and interrupt handlers. Processes are scheduled for execution through a prioritized round-robin algorithm. Interrupt handlers are divided into two types; First Level Interrupt Handlers (FLIHs) and Second Level Interrupt Handlers (SLIHs). There is only one FLIH per hardware interrupt level, and one SLIH per adapter on each interrupt level. Both processes and interrupt handlers can be installed from a virtual machine. Also, processes and interrupt handlers can be created by processes within the virtual resource manager. Basically, anything a virtual machine can do with Virtual Machine Interface (VMI) Supervisory Calls (SVCs), a virtual resource manager can do with function calls to the virtual resource manager nucleus.
When components and devices are installed into the virtual resource manager from a virtual machine, the virtual machine supplies identifying Input/Output Code Numbers (IOCNs) and identifying Input/Output Device Numbers (IODNs). The virtual resource manager generates IODNs for newly created instances of virtual devices. Within the virtual resource manager, components and devices are known by encoded identifications (IDs) which are generated by the virtual resource manager. These IDs are unique and dynamic; i.e., each time an IODN is defined by a virtual machine, the internal device identification will be different even though the IODN is static. Only programmers writting code for inside the virtual resource manager need be concerned with the internal identifications since they are not reflected above the virtual machine interface.
Referring now to FIG. 1 of the drawings, there is shown a model of the virtual resource manager device driver. The virtual machine 10 is interfaced with the virtual resource manager driver 12 through a well defined virtual machine interface 14. The virtual machine 10 issues calls to define device supervisory calls (SVCs) and to attach device supervisory calls as represented by block 16, and in response to those calls, the virtual resource manager device driver 12 is initialized at block 122 and provides an virtual interrupt to the virtual machine 10. The virtual machine 10 also issues a call to start an input/output supervisory call as represented by block 18. This causes the virtual resource manager device driver 12 to check device parameters in block 126 and provide a return to the start input/output supervisory call block 18 which then causes the virtual resource manager device driver 12 to initiate input/output in block 124 and provide a virtual interrupt to the virtual machine 10. A virtual interrupt to the virtual machine 10 is also provided by the SLIH 128. The adpater 20 provides interrupts to the virtual resource manager device driver 12 and responds to input/output operation commands from the device driver 12 via the hardware interface 22.
A device is defined at virtual resource manager initial program load time for virtual resource manager devices or when the operating system issues the appropriate "Define Device SVC". The device driver's define device routine is called at this time to disable the device's adapter (interrupts, DMA, and the like). The data passed to this routine is the Define Device Structure (DDS) specified with the "Define Device SVC". The DDS which is passed to the device driver's define device routine contains a device dependent area that provides the means by which the operating system can pass configuration information to the device driver. The define routine is responsible for copying this structure into its static data area and returning its address. Each device driver will define the parameters that must be contained in the DDS device characteristics section in response to a change characteristics operation.
A device is initialized by the virtual resource manager by calling the "Start Device" routine. This occurs automatically each time a virtual machine 10 attaches a device. The device driver's initialization routine is called at this time to enable/initialize the device's adapter. By not initializing the device until it is attached saves system resources and allows a more flexible use of hardware resources. For example, two devices that do not support interrupt sharing could use the same interrupt level if they are not both active. A device is terminated by the virtual resource manager by calling the "Start Device" routine with the stop option. The device driver's termination routine is called at this time to disable the device's adapter. This allows the device to be allocated to a co-processor or resources used by the device to be allocated to other devices.
UNIX device drivers in a non-virtual resource manager environment interface directly to the system hardware. To support the adding and/or deleting of devices and the building of a new UNIX kernel, several UNIX system files exist. These files fall into two categories; those required to "make" the UNIX kernel (system tables) and those that are constructed as the result of "making" a new kernel (binding tables). In order to support a more dynamic system environment for UNIX as a virtual machine running on a virtual resource manager, the present invention provides certain linkages between the UNIX device drivers and the corresponding real and virtual devices in the virtual resource manager. This linkage mechanism consists primarily of a convention by which both real and virtual devices are identified by a device number referred to as the IODN as described above. In order to bind the UNIX device drivers to the corresponding virtual resource manager components, a mechanism is provided to communicate the IODN along with other information to the UNIX device driver as part of the normal UNIX initialization.
The virtual resource manager configuration (VRMCONF) relational structure for UNIX is shown in FIG. 2. The CONFIG.DD subcomponent 242 of VRMCONF is itself a device driver inside the UNIX kernel 24. As such, it is the part of VRMCONF which issues the virtual resource manager supervisory calls. It also is the mechanism by which the IODN and other information gets passed to the respective kernel device drivers. It passes this information via a kernel function call. The function call is initiated via the "CFDDRU" input/output control issued to the CONFIG.DD. The internal call, i.e. CONFIG.DD to kernel, is of the following format:
(p-<d-- init)(device, iodn, ilev, ddlen, ddptr),
where the parameters are
device: a dev-- with the major/minor device numbers
iodn: the iodn to use for this device or 0 if not applicable
ipri: virtual interrupt level
ddlen: the length of the device dependent information or 0 if none
ddptr: a pointer to the device dependent information or 0 if none
There are two key tables used in "making" the UNIX kernel. These are /etc/master 26 and /etc/system 28 (alias /usr/sys/cf/dfile.std). The /etc/master 26 is an ASCII text file containing information about every device the system is capable of supporting. There is at least one entry in this file for every real device. In the virtual resource manager environment, the same is still true, but in addition, there must be at least one entry for every virtual device (device manager). The /etc/system file 28 is also an ASCII text file. It contains information about every device driver on the UNIX file system. There is at least one entry in this file for each device driver. In the UNIX environment, there are both real and pseudo device drivers. A pseudo device driver has no real or virtual device associated with it. (Pseudo device drivers is one way to gain access to the VMI-- SVC-- calls.) Entries for these pseudo device drivers are required in the /etc/system file 28 in the virtual resource manager environment.
At least two tables are created as part of the UNIX kernel build operation. One is known as "CONF.C" 244 and the other as interrupt table 246. These are part of the UNIX kernel 24 and are software vectoring tables. The CONF.C table 244 is used by the kernel to locate each device driver (major number) and the routines that driver supports. It is a binding table which identifies each major device number and relates that driver to a set of system calls. For example, the UNIX system call OPEN /dev/devicel would be indexed through the CONF.C table to find the UNIX device driver to pass the call to as well as the specific routine to run as the result of the OPEN system call. This continues to be true in the virtual resource manager environment. In addition, the normal use of this table is extended to contain pointers to the UNIX Device Driver (UDD) tables, contained within the device drivers, in which the IODN and device dependent information are written during UNIX initialization as indicated in FIG. 2. The UNIX device driver table structure is shown below:
______________________________________ Status Flags ______________________________________ IODN INT.sub.-- LEV/SUB.sub.-- LEV LL Device Dep. Info. ______________________________________ Status-one entry per major/minor table entry IODN2-byte integer; tag by which the UDD knows its corresponding VRM component, one entry per major/minor combination INT.sub.-- LEVvalue 0-15 of virtual interrupt level SUB.sub.-- LEVvalue 0-255 interrupt sublevel values (assigned at "ATTACH" time) LL2-yte integer; length of the device dependent information
Thus, the type of information in CONF.C does not change. Additional binding information is added to provide pointers into UDD data areas.
The interrupt table 246 is an interrupt vectoring table "made" with the kernel 24 in normal UNIX operation. The Virtual Interrupt Vector Table is shown below and represents information contained in the routine table:
______________________________________ INT.sub.-- LEV/SUB.sub.-- LEV MAJ/MIN # PNTR (UNIX DD INTR ROUTINE) ______________________________________ INT.sub.-- LEV/SUB.sub.-- LEVVirtual Interrupt Identifier from VRM MAJ/MIN Identifier of UDD owning interrupt PNTRPointer to UDD interrupt handling routine
This table is not "static" built as part of the kernel build but is dynamically built at run-time. Each UNIX device driver must call the kernel function call to receive interrupt sub-level information while passing its major and minor number as well as a pointer to the interrupt handler routine.
There is generally one table 30 similar to the UNIX system tables per device type (/etc/ddi). These tables contain device or device type specific information, while etc/master 26 and etc/system 28 contain information common to all devices. The files containing device-dependent information (the descriptive data that is associated with a particular device) are as follows:
______________________________________ /etc/disk etc/display /etc/diskette etc/tape /etc/printer etc/keyboard /etc/async etc/locator ______________________________________
Every UNIX device driver follows certain conventions. While there is the concept of a predefined IODN, for some of the nucleus components of a virtual resource manager, the majority of the device/device manager tags (IODNs) will vary in assignment. Only the nucleus virtual resource manager components are allowed to default always to a specific IODN. Therefore, UNIX device drivers are not allowed to have "hardcode" device dependent information. Each UDD writer will have a table entry for each IODN it controls. If the UDD is a multiplexing device driver, i.e. deals with more than one IODN, the table must reflect this situation. An example of this is a UDD for controlling printers. This UDD perhaps might control multiple printers. The defined mechanism for handling this is the UNIX major device number which reflects the Printer UDD and the minor number which reflects the specific printer. Therefore, the size of the UDD table is directly proportional to the number of minor devices. Using CONF.C, this major/minor number combination is the mechanism by which the correct table entry in the associated UDD is updated.
Turning now to FIG. 3, the flow chart for the device driver and adapter binding according to the invention is shown. In block 40, it is assumed that the user modifies the device configuration. To do this, the physical port number of the device connection must be specified in the table of adapter characteristics as indicated in block 42. Then, if the device is a new device, the flow progresses to block 46; otherwise, the flow progresses to block 54 as indicated by the decision block 44. In block 46, the UNIX system configuration files /etc/master 26 and etc/system 28 are modified. Then in block 48, a token (IODN) is assigned to the device. This is followed in block 50 with a re-load operation, and then in block 52, the device is defined to the virtual resource manager with modified adapter characteristics, including passing the token number for the device. Going now to block 54, the UNIX device driver is updated for device characteristics, including an identical token number for the device. The UNIX application "OPENS" the UNIX device driver to use the device in block 56. This is followed in block 58 by the UNIX device driver passing the device token number to the virtual resource manager. When the virtual resource manager receives the token number, it passes a request to the associated virtual resource manager device driver for the corresponding token number as indicated in block 60. In block 62, the virtual resource manager device driver uses adapter characteristics and port number corresponding to the device token number to drive the device thus completing the device driver and and adpater binding. Then, when the device is to be driven by an application, the device which has been set up by the user is requested via the UNIX device driver and the virtual resource manager device driver as indicated in block 64.
To provide a more concrete example for those skilled in the art of system programming and familiar with the UNIX operating system, reference is now made to FIG. 4. In this example, a line printer 70 identified as LPT9 is to be attached to an RS232 serial adapter 72 having four ports identified by the tokens IODNl, IODN2, IODN3, and IODN4. The first step is to modify the /etc/system file 28 and the /etc/master file 26. In these tables, the parameters for the LPT9 printer are entered as major number=9, prefix=XX, and DDI=/etc/printers. The /etc/master file 26 contains all supported devices, irrespective of their configuration. In the etc/system file 28, there is one entry per adapter/device, i.e. per UNIX device driver.
In step 2, the DDI (device dependent information) file may be modified for device or adpater parameters. Then, in step 3, the character special file is created for the line printer LPT9. This is followed, in step 4, with the initial program load (IPL) sequence to execute the VRMCONFIG program. In step 5, the VRMCONFIG program passes device dependent information to the configuration (CONFIG) pseudo device driver. In step 6, the CONFIG device driver makes known the virtual resource manager device driver code to the virtual resource manager, along with the token (IODN). In step 7, the CONFIG device driver passes some device information to the UNIX device driver, along with the same token (IODN), which is stored in the table area of the UNIX device driver. At this point, an application program can "OPEN" the special file /dev/lpt9 created in step 3 as indicated in FIG. 4 at step 8. This causes, in step 9, the UNIX device driver to use the IODN (passed in step 7) to go to the virtual resource manager to "bind" to the virtual resource manager device driver corresponding to the same token and associated with the adapter port.
Other specific examples will readily suggest themselves to those skilled in the art, and although the preferred embodiment of the invention has been described as using the UNIX operating system, other operating systems having similar characteristics could be adapted for use in accordance with the teachings of the invention. Therefore, it will be understood by those skilled in the systems programming art that while the invention has been particularly shown and described with respect to a single preferred embodiment, changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (11)
1. A device driver and adapter binding technique in which an operating system having device drivers is run as a virtual machine on a virtual resource manager having device drivers of real and virtual devices comprising the steps of .Iadd.in a computer system.Iaddend.:
assigning a "token" to the virtual resource manager's device driver for the device to be bound to a device driver of said operating system;
creating a device dependent information file in said operating system corresponding to said device to be bound, said file including adapter dependent information for said device;
placing said "token" in a device driver of said operating system .[.at the time.]. .Iadd.when .Iaddend.said operating system is initiated; and
using said "token" placed in said device driver of said operating system to communicate with the corresponding virtual resource manager device driver when said device driver of said operating system is opened to drive said device, thereby binding the two drivers and using the device dependent information in said device dependent information file to drive the physical device.
2. A device driver and adaptive binding technique as recited in claim 1 wherein a user may modify a device configuration, said technique further comprising the steps of:
specifying .[.the.]. .Iadd.a .Iaddend.port number of the device connection in a table of adapter characteristics; and
updating the device driver of said operating system for device characteristics including said "token" for the device if the device is not a new device before using said "token" when said device driver of said operating system is opened;
otherwise, repeating said steps of assigning, creating and placing if the device is a new device.
3. A device driver and adaptive binding technique as recited in claim 1 wherein the step of using said "token" is performed with the following steps:
passing said "token" from said operating system device driver to said virtual resource manager;
retrieving device dependent information from the associated virtual resource manager device driver corresponding to said "token"; and
using said device dependent information to drive the device.
4. A method of linking device drivers of an operating system run as a virtual machine on a virtual resource manager with the device drivers of said virtual resource manager comprising the steps of .Iadd.in a computer system.Iaddend.:
specifying .[.the.]. .Iadd.a .Iaddend.port number of a device connection in a table of adapter characteristics;
modifying the operating system configuration files and assigning a token number to said device;
reloading said operating system to define said device to said virtual resource manager with adapter characteristics and passing said token number to an associated device driver of said virtual resource manager;
opening the device driver of said operating system to use said device;
passing said token number from said device driver to said virtual resource manager;
retrieving .[.the.]. device dependent information from the associated virtual resource manager device driver corresponding to said token number; and
using said device dependent information to drive said device, thereby linking the device drivers of said operating system and said virtual resource manager.
5. The method recited in claim 4 wherein a user may modify a device configuration further comprising the steps of updating the device driver of said operating system for the device characteristics including the identical token number for the device if the device is not a new device. .Iadd.
6. A method of linking device drivers of an operating system, run as a virtual machine on a virtual resource manager, with the device drivers of said virtual resource manager, comprising the steps of in a computer system:
providing an intermediate layer operating as the virtual resource manager and having a plurality of first device drivers for driving devices within the computer system;
providing a system configuration file which describes a plurality of corresponding devices accessible by the operating system through the first device drivers;
loading the operating system into the computer system, wherein a plurality of second device drivers for the plurality of accessible devices are linked to the operating system, and wherein the second device drivers are linked to first device drivers from the intermediate layer;
providing, to the second device drivers, device dependent information for the plurality of accessible devices;
opening each second device driver to use a particular one of the plurality of accessible devices, wherein the device dependent information is accessed by the device driver to drive one of the plurality of accessible devices through a corresponding first device driver; and
using the device dependent information to drive the plurality of accessible devices through the first device drivers. .Iaddend..Iadd.
7. A method for linking device drivers in a computer operating system, run as a virtual machine on a virtual resource manager, with the device drivers of said virtual resource manager, wherein a user may modify a device configuration, comprising the steps of:
providing an intermediate layer operating as the virtual resource manager and having a plurality of first device drivers for driving devices within the computer system;
creating a device dependent information file in the operating system corresponding to a physical device to be bound, such file including device dependent information for such device;
specifying a port number of the device connection in a table of adapter characteristics;
updating a second device driver of the operating system with device characteristics if the device is not a new device when the device driver of the operating system is opened;
otherwise, repeating said creating step if the device is a new device; and
using, within the second device driver, the device dependent information in the device dependent information file to drive a first device driver within the intermediate layer, which in turn drives the physical device. .Iaddend..Iadd.
8. A reconfigurable computer system having an operating system run as a virtual machine on a virtual resource manager, comprising:
an operating system;
a plurality of devices attached to the computer system;
an intermediate layer operating as the virtual resource manager and having a plurality of first device drivers for driving the devices;
a plurality of second device drivers coupled to the operating system and directly callable therefrom, wherein the operating system communicates with the intermediate layer through the second device drivers, and wherein said devices communicate with said intermediate layer through said first device drivers; and
means, connected to said operating system, for communicating stored device dependent information describing said devices to said second device drivers when said operating system is initialized, wherein said second device drivers drive said first device drivers using the device dependent information. .Iaddend..Iadd.9. The system of claim 8, wherein said communicating means includes, for each attached device, a device dependent information file describing characteristics of such device.
.Iaddend..Iadd.0. A reconfigurable computer system having an operating system run as a virtual machine on a virtual resource manager, comprising:
an operating system;
a plurality of devices attached to the computer system;
an intermediate layer operating as a virtual resource manager and having a plurality of first device drivers for driving the devices;
a plurality of second device drivers coupled to the operating system and directly callable therefrom, wherein the operating system communicates with the intermediate layer through the second device drivers, and wherein said devices communicate with said intermediate layer through said first device drivers;
means, connected to said operating system, for communicating stored device dependent information describing said devices to said second device drivers when said operating system is initialized, wherein said second device drivers drive said first device drivers using the device dependent information; and
a system file, in the computer system, describing the attached devices, wherein said operating system reads said system file when said operating system is initialized, and wherein the second device drivers are coupled to said operating system according to the system file descriptions.
.Iaddend..Iadd.11. A reconfigurable computer system having an operating system run as a virtual machine on a virtual resource manager, comprising:
an operating system;
a plurality of devices attached to the computer system;
an intermediate layer operating as a virtual resource manager and having a plurality of first device drivers for driving the devices;
a plurality of second device drivers coupled to the operating system and directly callable therefrom, wherein the operating system communicates with the intermediate layer through the second device drivers, and wherein said devices communicate with said intermediate layer through said first device drivers;
means, connected to said operating system, for communicating stored device dependent information describing said devices to said second device drivers when said operating system is initialized, wherein said second device drivers drive said first device drivers using the device dependent information; and
wherein said device drivers have empty tables when they are coupled to said operating system, and wherein the device dependent information is placed into the empty tables when said operating system is initialized. .Iaddend..Iadd.12. The system of claim 11, wherein at least one second device driver has more than one table containing device dependent information, whereby one such second device driver communicates with more
than one device through a first device driver. .Iaddend..Iadd.13. The system of claim 10, further comprising:
a master file, in the computer system, containing template descriptions of devices which can communicate with said operating system through the first device drivers, wherein entries in said system file are copied from said master file when new devices are attached to the system. .Iaddend.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/321,439 USRE36394E (en) | 1985-02-28 | 1989-03-09 | Device driver and adapter binding technique |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US06/706,642 US4649479A (en) | 1985-02-28 | 1985-02-28 | Device driver and adapter binding technique |
US07/321,439 USRE36394E (en) | 1985-02-28 | 1989-03-09 | Device driver and adapter binding technique |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US06/706,642 Reissue US4649479A (en) | 1985-02-28 | 1985-02-28 | Device driver and adapter binding technique |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE36394E true USRE36394E (en) | 1999-11-16 |
Family
ID=24838471
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US06/706,642 Ceased US4649479A (en) | 1985-02-28 | 1985-02-28 | Device driver and adapter binding technique |
US07/321,439 Expired - Lifetime USRE36394E (en) | 1985-02-28 | 1989-03-09 | Device driver and adapter binding technique |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US06/706,642 Ceased US4649479A (en) | 1985-02-28 | 1985-02-28 | Device driver and adapter binding technique |
Country Status (5)
Country | Link |
---|---|
US (2) | US4649479A (en) |
EP (1) | EP0192924B1 (en) |
JP (1) | JPS61201341A (en) |
CA (1) | CA1233262A (en) |
DE (1) | DE3678735D1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030126331A1 (en) * | 2002-01-03 | 2003-07-03 | Levy Paul S. | Method, apparatus, and system for multi-line communication |
US6606669B1 (en) * | 1994-12-06 | 2003-08-12 | Canon Kabushiki Kaisha | Information processing apparatus having automatic OS selecting function |
US6708229B2 (en) | 2000-12-27 | 2004-03-16 | Intel Corporation | Configuring computer components |
US6987579B1 (en) * | 2001-03-30 | 2006-01-17 | Bellsouth Intellectual Property Corp. | Read only printer (ROP) capabilities on a CSN platform |
US7580826B2 (en) | 2004-06-30 | 2009-08-25 | Microsoft Corporation | Systems and methods for development of emulated devices in a virtual machine environment |
Families Citing this family (109)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4701848A (en) * | 1984-11-19 | 1987-10-20 | Clyde, Inc. | System for effectively paralleling computer terminal devices |
JPS61206057A (en) * | 1985-03-11 | 1986-09-12 | Hitachi Ltd | Address converting device |
US4835685A (en) * | 1985-05-06 | 1989-05-30 | Computer X, Inc. | Virtual single machine with message-like hardware interrupts and processor exceptions |
US4875186A (en) * | 1986-02-28 | 1989-10-17 | Prime Computer, Inc. | Peripheral emulation apparatus |
US5083262A (en) * | 1986-04-28 | 1992-01-21 | International Business Machines Corporation | Language bindings for graphics functions to enable one application program to be used in different processing environments |
US4916608A (en) * | 1986-05-30 | 1990-04-10 | International Business Machines Corporation | Provision of virtual storage resources to an operating system control program |
US4975829A (en) * | 1986-09-22 | 1990-12-04 | At&T Bell Laboratories | Communication interface protocol |
US5179703A (en) * | 1987-11-17 | 1993-01-12 | International Business Machines Corporation | Dynamically adaptive environment for computer programs |
JP2569092B2 (en) * | 1987-12-11 | 1997-01-08 | 株式会社日立製作所 | Address resolution method for I / O device control program |
US5664177A (en) * | 1988-04-13 | 1997-09-02 | Digital Equipment Corporation | Data processing system having a data structure with a single, simple primitive |
US4864497A (en) * | 1988-04-13 | 1989-09-05 | Digital Equipment Corporation | Method of integrating software application programs using an attributive data model database |
US5079695A (en) * | 1988-04-25 | 1992-01-07 | Hewlett-Packard Company | Object management facility which includes a snapshot facility for providing data transfer between two objects |
US5155838A (en) * | 1988-04-28 | 1992-10-13 | Kabushiki Kaisha Toshiba | Computer system with emulation mechanism |
US5170470A (en) * | 1988-05-02 | 1992-12-08 | National Semiconductor Corp. | Integrated modem which employs a host processor as its controller |
JPH0290330A (en) * | 1988-09-28 | 1990-03-29 | Hitachi Ltd | Program constitution system |
US5063500A (en) * | 1988-09-29 | 1991-11-05 | Ibm Corp. | System for executing segments of application program concurrently/serially on different/same virtual machine |
US5363487A (en) * | 1989-08-29 | 1994-11-08 | Microsoft Corporation | Method and system for dynamic volume tracking in an installable file system |
EP0419064A3 (en) * | 1989-09-22 | 1992-08-05 | International Business Machines Corporation | Computer system having apparatus for providing pointing device independent support in an operating environment |
CA2010591C (en) * | 1989-10-20 | 1999-01-26 | Phillip M. Adams | Kernels, description tables and device drivers |
US5265228A (en) * | 1989-12-05 | 1993-11-23 | Texas Instruments Incorporated | Apparatus for transfer of data units between buses |
US5081577A (en) * | 1989-12-22 | 1992-01-14 | Harris Corporation | State controlled device driver for a real time computer control system |
JPH0727505B2 (en) * | 1990-02-12 | 1995-03-29 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Interface method and interface system |
US5179666A (en) * | 1990-06-07 | 1993-01-12 | Unisys Corporation | Block oriented peripheral device interface |
US5161222A (en) * | 1990-08-20 | 1992-11-03 | Human Microprocessing, Inc. | Software engine having an adaptable driver for interpreting variables produced by a plurality of sensors |
JPH0833818B2 (en) * | 1990-09-04 | 1996-03-29 | インターナショナル・ビジネス・マシーンズ・コーポレイション | How to operate a computer system |
US5497492A (en) * | 1990-09-04 | 1996-03-05 | Microsoft Corporation | System and method for loading an operating system through use of a fire system |
JPH0776951B2 (en) * | 1990-10-30 | 1995-08-16 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Computer system, address space sharing system with multiple I / O adapters, and communication management method between multiple I / O devices and computer processors |
US5307491A (en) * | 1991-02-12 | 1994-04-26 | International Business Machines Corporation | Layered SCSI device driver with error handling circuit providing sense data from device directly to the driver on the occurrence of an error |
US5291585A (en) * | 1991-07-29 | 1994-03-01 | Dell Usa, L.P. | Computer system having system feature extension software containing a self-describing feature table for accessing I/O devices according to machine-independent format |
US5517636A (en) * | 1992-01-07 | 1996-05-14 | Unisys Corporation | Platform independent data communication system and method |
US5390301A (en) * | 1992-08-11 | 1995-02-14 | Acer Incorporated | Method and apparatus for communicating device-specific information between a device driver and an operating system in a computer system |
EP0588046A1 (en) * | 1992-08-14 | 1994-03-23 | International Business Machines Corporation | IEEE standard 802.2 virtual device driver |
EP0584909A1 (en) * | 1992-08-26 | 1994-03-02 | Sun Microsystems, Inc. | Self configuring device system |
US5613123A (en) * | 1992-09-30 | 1997-03-18 | Microsoft Corporation | Method and system for configuring and executing device drivers based on configuration requirements |
US7043407B2 (en) * | 1997-03-10 | 2006-05-09 | Trilogy Development Group, Inc. | Method and apparatus for configuring systems |
AU715256B2 (en) * | 1993-03-29 | 2000-01-20 | Trilogy Development Group, Inc. | Method and apparatus for configuring systems |
US5515524A (en) * | 1993-03-29 | 1996-05-07 | Trilogy Development Group | Method and apparatus for configuring systems |
JPH0765540A (en) * | 1993-08-27 | 1995-03-10 | Olympus Optical Co Ltd | Apparatus for controlling data of optical card |
US5771354A (en) * | 1993-11-04 | 1998-06-23 | Crawford; Christopher M. | Internet online backup system provides remote storage for customers using IDs and passwords which were interactively established when signing up for backup services |
EP0657809B1 (en) * | 1993-12-13 | 2000-04-05 | International Business Machines Corporation | Input/output objects in operating system kernel |
US5712974A (en) * | 1994-03-30 | 1998-01-27 | International Business Machines Corporation | Method and apparatus for controlling the configuration definitions in a data processing system with a plurality of processors |
US5613161A (en) * | 1994-05-06 | 1997-03-18 | Sun Microsystems, Inc. | Method and apparatus for preemptable multiplexing of connections to input/out devices |
US5613125A (en) * | 1994-06-17 | 1997-03-18 | Motorola, Inc. | Method and system for selectively defining hardware parameters in an executable operating system program |
US5748866A (en) * | 1994-06-30 | 1998-05-05 | International Business Machines Corporation | Virtual display adapters using a digital signal processing to reformat different virtual displays into a common format and display |
JPH096706A (en) * | 1995-06-22 | 1997-01-10 | Hitachi Ltd | Loosely coupled computer system |
US5732282A (en) * | 1995-06-30 | 1998-03-24 | Sun Microsystems, Inc. | Virtual device driver registry having a globally unique identifier supplying virtual driver call information to the requesting program |
US5910180A (en) * | 1995-11-21 | 1999-06-08 | Diamond Multimedia Systems, Inc. | Context virtualizing device driver architecture |
US6393495B1 (en) | 1995-11-21 | 2002-05-21 | Diamond Multimedia Systems, Inc. | Modular virtualizing device driver architecture |
US5752032A (en) * | 1995-11-21 | 1998-05-12 | Diamond Multimedia Systems, Inc. | Adaptive device driver using controller hardware sub-element identifier |
US6009476A (en) * | 1995-11-21 | 1999-12-28 | Diamond Multimedia Systems, Inc. | Device driver architecture supporting emulation environment |
US5940613A (en) * | 1996-05-01 | 1999-08-17 | Sun Microsystems, Inc. | Method for creating a single binary virtual device driver for a windowing operating system |
US5953522A (en) * | 1996-07-01 | 1999-09-14 | Sun Microsystems, Inc. | Temporary computer file system implementing using anonymous storage allocated for virtual memory |
US5923328A (en) * | 1996-08-07 | 1999-07-13 | Microsoft Corporation | Method and system for displaying a hierarchical sub-tree by selection of a user interface element in a sub-tree bar control |
EP0825506B1 (en) * | 1996-08-20 | 2013-03-06 | Invensys Systems, Inc. | Methods and apparatus for remote process control |
US6687761B1 (en) | 1997-02-20 | 2004-02-03 | Invensys Systems, Inc. | Process control methods and apparatus with distributed object management |
US6353862B1 (en) * | 1997-04-04 | 2002-03-05 | Avid Technology, Inc. | Video device manager for managing motion video output devices and supporting contexts and buffer adoption |
US6418485B1 (en) * | 1997-04-21 | 2002-07-09 | International Business Machines Corporation | System and method for managing device driver logical state information in an information handling system |
US6078747A (en) * | 1998-01-05 | 2000-06-20 | Jewitt; James W. | Application program interface to physical devices |
US6681266B2 (en) | 1998-04-14 | 2004-01-20 | Dell Usa, L.P. | Late binding dynamic software configuration information |
US6691183B1 (en) | 1998-05-20 | 2004-02-10 | Invensys Systems, Inc. | Second transfer logic causing a first transfer logic to check a data ready bit prior to each of multibit transfer of a continous transfer operation |
US6910210B1 (en) * | 1998-11-24 | 2005-06-21 | Microsoft Corp. | System and method for terminating applications |
US6754885B1 (en) | 1999-05-17 | 2004-06-22 | Invensys Systems, Inc. | Methods and apparatus for controlling object appearance in a process control configuration system |
AU5273100A (en) * | 1999-05-17 | 2000-12-05 | Foxboro Company, The | Methods and apparatus for control configuration with versioning, security, composite blocks, edit selection, object swapping, formulaic values and other aspects |
US7096465B1 (en) | 1999-05-17 | 2006-08-22 | Invensys Systems, Inc. | Process control configuration system with parameterized objects |
US7272815B1 (en) | 1999-05-17 | 2007-09-18 | Invensys Systems, Inc. | Methods and apparatus for control configuration with versioning, security, composite blocks, edit selection, object swapping, formulaic values and other aspects |
US7089530B1 (en) | 1999-05-17 | 2006-08-08 | Invensys Systems, Inc. | Process control configuration system with connection validation and configuration |
US6501995B1 (en) | 1999-06-30 | 2002-12-31 | The Foxboro Company | Process control system and method with improved distribution, installation and validation of components |
US6532279B1 (en) * | 1999-06-11 | 2003-03-11 | David D. Goodman | High-speed data communication over a residential telephone wiring network |
US6788980B1 (en) * | 1999-06-11 | 2004-09-07 | Invensys Systems, Inc. | Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network |
US6704824B1 (en) * | 1999-07-27 | 2004-03-09 | Inline Connection Corporation | Universal serial bus adapter with automatic installation |
US20040230710A1 (en) * | 1999-07-27 | 2004-11-18 | Inline Connection Corporation | System and method of automatic installation of computer peripherals |
US6510352B1 (en) | 1999-07-29 | 2003-01-21 | The Foxboro Company | Methods and apparatus for object-based process control |
US6473660B1 (en) | 1999-12-03 | 2002-10-29 | The Foxboro Company | Process control system and method with automatic fault avoidance |
US7062648B2 (en) * | 2000-02-18 | 2006-06-13 | Avamar Technologies, Inc. | System and method for redundant array network storage |
US7194504B2 (en) * | 2000-02-18 | 2007-03-20 | Avamar Technologies, Inc. | System and method for representing and maintaining redundant data sets utilizing DNA transmission and transcription techniques |
US6779128B1 (en) | 2000-02-18 | 2004-08-17 | Invensys Systems, Inc. | Fault-tolerant data transfer |
US6826711B2 (en) | 2000-02-18 | 2004-11-30 | Avamar Technologies, Inc. | System and method for data protection with multidimensional parity |
US6704730B2 (en) | 2000-02-18 | 2004-03-09 | Avamar Technologies, Inc. | Hash file system and method for use in a commonality factoring system |
US7509420B2 (en) | 2000-02-18 | 2009-03-24 | Emc Corporation | System and method for intelligent, globally distributed network storage |
US7111297B1 (en) * | 2000-05-02 | 2006-09-19 | Microsoft Corporation | Methods and architectures for resource management |
US7137119B1 (en) | 2000-05-02 | 2006-11-14 | Microsoft Corporation | Resource manager architecture with resource allocation utilizing priority-based preemption |
US6799208B1 (en) | 2000-05-02 | 2004-09-28 | Microsoft Corporation | Resource manager architecture |
US7058947B1 (en) | 2000-05-02 | 2006-06-06 | Microsoft Corporation | Resource manager architecture utilizing a policy manager |
US7284244B1 (en) | 2000-05-02 | 2007-10-16 | Microsoft Corporation | Resource manager architecture with dynamic resource allocation among multiple configurations |
US7337179B1 (en) | 2000-11-01 | 2008-02-26 | Versata Development Group, Inc. | Context subsystems for system configurations |
US6810398B2 (en) * | 2000-11-06 | 2004-10-26 | Avamar Technologies, Inc. | System and method for unorchestrated determination of data sequences using sticky byte factoring to determine breakpoints in digital sequences |
US6677347B2 (en) * | 2000-12-08 | 2004-01-13 | 3M Innovative Properties Company | Sulfonamido ether substituted imidazoquinolines |
US8214849B2 (en) * | 2001-07-13 | 2012-07-03 | Advanced Micro Devices, Inc. | System for loading device-specific code and method thereof |
US20030055863A1 (en) * | 2001-07-24 | 2003-03-20 | Spiegel Michael G. | Method and apparatus for managing system resources in an information handling system |
US7107331B2 (en) * | 2002-03-25 | 2006-09-12 | Kabushiki Kaisha Toshiba | System and method for configuring digital image devices |
US6977994B2 (en) * | 2002-03-27 | 2005-12-20 | Toshiba Tec Kabushiki Kaisha | Portable, high performance messaging system |
US7242991B2 (en) * | 2002-04-15 | 2007-07-10 | Invensys Systems, Inc. | Workflow control configurator for use with process, factory-floor, environmental, computer aided manufacturing-based or other control system |
US20070186216A1 (en) * | 2002-05-28 | 2007-08-09 | Mustafa Seifi | Message driven job processing system and method |
US7437613B2 (en) * | 2004-01-30 | 2008-10-14 | Intel Corporation | Protecting an operating system kernel from third party drivers |
US7761923B2 (en) * | 2004-03-01 | 2010-07-20 | Invensys Systems, Inc. | Process control methods and apparatus for intrusion detection, protection and network hardening |
JP2005258493A (en) * | 2004-03-09 | 2005-09-22 | Buffalo Inc | External storage device |
US7574709B2 (en) * | 2004-04-30 | 2009-08-11 | Microsoft Corporation | VEX-virtual extension framework |
US8024726B2 (en) * | 2004-05-28 | 2011-09-20 | International Business Machines Corporation | System for correct distribution of hypervisor work |
WO2007123753A2 (en) | 2006-03-30 | 2007-11-01 | Invensys Systems, Inc. | Digital data processing apparatus and methods for improving plant performance |
EP2021926A4 (en) | 2006-05-05 | 2009-07-15 | Hybir Inc | Group based complete and incremental computer file backup system, process and apparatus |
US7716379B2 (en) | 2007-04-26 | 2010-05-11 | Microsoft Corporation | Hardware control interface for IEEE standard 802.11 including transmission control interface component and a transmission status interface component |
US8346974B2 (en) * | 2007-07-27 | 2013-01-01 | Microsoft Corporation | Hardware control interface for IEEE standard 802.11 |
US8281303B2 (en) * | 2007-10-31 | 2012-10-02 | Hewlett-Packard Development Company, L.P. | Dynamic ejection of virtual devices on ejection request from virtual device resource object within the virtual firmware to virtual resource driver executing in virtual machine |
CN102124432B (en) | 2008-06-20 | 2014-11-26 | 因文西斯系统公司 | Systems and methods for immersive interaction with actual and/or simulated facilities for process, environmental and industrial control |
TW201005535A (en) * | 2008-07-17 | 2010-02-01 | Ind Tech Res Inst | Electronic apparatus and method for managing a plugged device |
US8463964B2 (en) | 2009-05-29 | 2013-06-11 | Invensys Systems, Inc. | Methods and apparatus for control configuration with enhanced change-tracking |
US8127060B2 (en) | 2009-05-29 | 2012-02-28 | Invensys Systems, Inc | Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware |
US8881140B1 (en) * | 2009-09-04 | 2014-11-04 | Symantec Corporation | Systems and methods for virtualizing software associated with external computer hardware devices |
US8312195B2 (en) * | 2010-02-18 | 2012-11-13 | Red Hat, Inc. | Managing interrupts using a preferred binding between a device generating interrupts and a CPU |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3828325A (en) * | 1973-02-05 | 1974-08-06 | Honeywell Inf Systems | Universal interface system using a controller to adapt to any connecting peripheral device |
US4330822A (en) * | 1971-09-02 | 1982-05-18 | Burroughs Corporation | Recursive system and method for binding compiled routines |
US4455619A (en) * | 1980-05-30 | 1984-06-19 | Hitachi, Ltd. | Interactive equipment for computer programming by linkage of labeled block representations of arithmetic/logical subprograms |
US4456954A (en) * | 1981-06-15 | 1984-06-26 | International Business Machines Corporation | Virtual machine system with guest architecture emulation using hardware TLB's for plural level address translations |
US4475156A (en) * | 1982-09-21 | 1984-10-02 | Xerox Corporation | Virtual machine control |
US4485439A (en) * | 1982-07-27 | 1984-11-27 | S.A. Analis | Standard hardware-software interface for connecting any instrument which provides a digital output stream with any digital host computer |
US4493034A (en) * | 1982-10-14 | 1985-01-08 | Honeywell Information Systems Inc. | Apparatus and method for an operating system supervisor in a data processing system |
US4494188A (en) * | 1981-04-03 | 1985-01-15 | Hitachi, Ltd. | Method of processing an operating system in a multi-processor system |
US4500933A (en) * | 1982-04-02 | 1985-02-19 | Ampex Corporation | Universal interface unit |
US4589063A (en) * | 1983-08-04 | 1986-05-13 | Fortune Systems Corporation | Data processing system having automatic configuration |
US4701848A (en) * | 1984-11-19 | 1987-10-20 | Clyde, Inc. | System for effectively paralleling computer terminal devices |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3381881D1 (en) * | 1983-02-22 | 1990-10-18 | Ibm | METHOD FOR THE DYNAMIC RECONFIGURATION OF A DATA PROCESSING SYSTEM WITH THE ADDITION OF DEVICES. |
-
1985
- 1985-02-28 US US06/706,642 patent/US4649479A/en not_active Ceased
- 1985-09-20 CA CA000491268A patent/CA1233262A/en not_active Expired
- 1985-12-18 JP JP60283218A patent/JPS61201341A/en active Granted
-
1986
- 1986-01-02 DE DE8686100039T patent/DE3678735D1/en not_active Expired - Fee Related
- 1986-01-02 EP EP86100039A patent/EP0192924B1/en not_active Expired
-
1989
- 1989-03-09 US US07/321,439 patent/USRE36394E/en not_active Expired - Lifetime
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4330822A (en) * | 1971-09-02 | 1982-05-18 | Burroughs Corporation | Recursive system and method for binding compiled routines |
US3828325A (en) * | 1973-02-05 | 1974-08-06 | Honeywell Inf Systems | Universal interface system using a controller to adapt to any connecting peripheral device |
US4455619A (en) * | 1980-05-30 | 1984-06-19 | Hitachi, Ltd. | Interactive equipment for computer programming by linkage of labeled block representations of arithmetic/logical subprograms |
US4494188A (en) * | 1981-04-03 | 1985-01-15 | Hitachi, Ltd. | Method of processing an operating system in a multi-processor system |
US4456954A (en) * | 1981-06-15 | 1984-06-26 | International Business Machines Corporation | Virtual machine system with guest architecture emulation using hardware TLB's for plural level address translations |
US4500933A (en) * | 1982-04-02 | 1985-02-19 | Ampex Corporation | Universal interface unit |
US4485439A (en) * | 1982-07-27 | 1984-11-27 | S.A. Analis | Standard hardware-software interface for connecting any instrument which provides a digital output stream with any digital host computer |
US4475156A (en) * | 1982-09-21 | 1984-10-02 | Xerox Corporation | Virtual machine control |
US4493034A (en) * | 1982-10-14 | 1985-01-08 | Honeywell Information Systems Inc. | Apparatus and method for an operating system supervisor in a data processing system |
US4589063A (en) * | 1983-08-04 | 1986-05-13 | Fortune Systems Corporation | Data processing system having automatic configuration |
US4701848A (en) * | 1984-11-19 | 1987-10-20 | Clyde, Inc. | System for effectively paralleling computer terminal devices |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6606669B1 (en) * | 1994-12-06 | 2003-08-12 | Canon Kabushiki Kaisha | Information processing apparatus having automatic OS selecting function |
US6708229B2 (en) | 2000-12-27 | 2004-03-16 | Intel Corporation | Configuring computer components |
US6987579B1 (en) * | 2001-03-30 | 2006-01-17 | Bellsouth Intellectual Property Corp. | Read only printer (ROP) capabilities on a CSN platform |
US20030126331A1 (en) * | 2002-01-03 | 2003-07-03 | Levy Paul S. | Method, apparatus, and system for multi-line communication |
US6868464B2 (en) * | 2002-01-03 | 2005-03-15 | Intel Corporation | Method, apparatus, and system for multi-line communication |
US7580826B2 (en) | 2004-06-30 | 2009-08-25 | Microsoft Corporation | Systems and methods for development of emulated devices in a virtual machine environment |
Also Published As
Publication number | Publication date |
---|---|
EP0192924B1 (en) | 1991-04-17 |
JPS61201341A (en) | 1986-09-06 |
EP0192924A3 (en) | 1988-09-28 |
CA1233262A (en) | 1988-02-23 |
DE3678735D1 (en) | 1991-05-23 |
EP0192924A2 (en) | 1986-09-03 |
JPH0535898B2 (en) | 1993-05-27 |
US4649479A (en) | 1987-03-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE36394E (en) | Device driver and adapter binding technique | |
CA2178581C (en) | Automatic booting framework | |
US6751737B1 (en) | Multiple protected mode execution environments using multiple register sets and meta-protected instructions | |
US5459867A (en) | Kernels, description tables, and device drivers | |
US4787026A (en) | Method to manage coprocessor in a virtual memory virtual machine data processing system | |
US5574915A (en) | Object-oriented booting framework | |
Creasy | The origin of the VM/370 time-sharing system | |
EP0192944B1 (en) | Data processing system with a main processor and a co-processor sharing the same resources | |
US5974517A (en) | Method and system for mounting a system partition as a logical drive while an operating system is operational by modifying a partition table | |
KR100361635B1 (en) | Logical partition manager and method | |
US6157960A (en) | Technique for programmatically creating distributed object programs | |
US5675795A (en) | Boot architecture for microkernel-based systems | |
US5701483A (en) | Data acess implementation of device driver interface | |
US5526523A (en) | Interface between operating system and operating system extension | |
US5630074A (en) | Inter-program communication and scheduling method for personal computers | |
CN1781091A (en) | System and method for virtualizing basic input/output system (BIOS) including BIOS run time services | |
US5291595A (en) | Batch/application program processing | |
US6199117B1 (en) | Generalized control for starting of tasks (processes and threads) | |
JPH05216689A (en) | Computer apparatus and computer-apparatus operating method | |
US7343603B1 (en) | System and method for performing incremental initialization of a master runtime system process | |
US5909576A (en) | Method and apparatus for using device drivers of a first operating system, under the control of a second operating system | |
US5673418A (en) | Method and apparatus for emulating the operations of an emulated system terminal driver on a host system | |
EP0260458B1 (en) | Networking processors | |
Schleipfer | The ServOS kernel: a special-purpose operating system kernel for server machines | |
Lennon | A mini-computer network for support of real time research |