US 6,205,503 B1Grant
Method for the hot swap and add of input/output platforms and devices
Issue Date:2001-03-20
•23 Claims
•15 Drawing Sheets
Abstract
A method for the hot add and swap of I2O compliant input/output platforms and adapters. The method allows users to perform the hot replace failed components, upgrade outdated components, and add new functionality, such as new network interfaces, disk interface adapters and storage, without impacting existing users. The method supports the hot add and swap of off-the-shelf adapters, including those adapters that are programmable.
Metadata
Inventor
- Mallikarjunan Mahalingam
Application Information
Application Number:US 09/118,716
Filing Date:1998-07-17
Priority Date:1998-07-17
Art Unit:7
Classifications
IPC:
G06F 1300
Field of Search:
710 8710 17710 18710 72710 73710 74710 2710 3710 10709250709301714 5714 7714 8713 1713100
Patent Drawings (15 sheets)
Description
Related Applications
[0002] The subject matter of the U.S. Patent Application entitled “APPARATUS FOR THE HOT SWAP AND ADD OF INPUT/OUTPUT PLATFORMS AND DEVICES,” filed concurrently herewith, Application Ser. No. 09/118,219, and having Attorney Docket Number MNFRAME.079A contains related subject matter. In addition, this is a continuation-in-part of and incorporates by reference in their entirety the below listed U.S. patent applications:
Background of the Invention
[0003] 1. Field of the Invention
[0004] The field of the invention relates to I/O adapters in computer systems. More particularly, the field of invention relates to the hot add and swap of adapters and input/output platforms on computer systems.
[0005] 2. Description of the Related Technology
[0006] As enterprise-class servers, which are central computers in a network that manage common data, become more powerful and more capable, they are also becoming ever more sophisticated and complex. For many companies, these changes lead to concerns over server reliability and manageability, particularly in light of the increasingly critical role of server-based applications. While in the past many systems administrators were comfortable with all of the various components that made up a standards-based network server, today's generation of servers can appear as an incomprehensible, unmanageable black box. Without visibility into the underlying behavior of the system, the administrator must “fly blind.” Too often, the only indicators the network manager has on the relative health of a particular server is whether or not it is running.
[0007] It is well-acknowledged that there is a lack of reliability and availability of most standards-based servers. Server downtime, resulting either from hardware or software faults or from regular maintenance, continues to be a significant problem. By one estimate, the cost of downtime in mission critical environments has risen to an annual total of $4.0 billion for U.S. businesses, with the average downtime event resulting in a $140 thousand loss in the retail industry and a $450 thousand loss in the securities industry. It has been reported that companies lose as much as $250 thousand in employee productivity for every 1% of computer downtime. With emerging Internet, intranet and collaborative applications taking on more essential business roles every day, the cost of network server downtime will continue to spiral upward.
[0008] A significant component of cost is hiring administration personnel. These costs decline dramatically when computer systems can be managed using a common set of tools, and where they don't require immediate attention when a failure occurs. Where a computer system can continue to operate even when components fail, and defer repair until a later time, administration costs become more manageable and predictable.
[0009] While hardware fault tolerance is an important element of an overall high availability architecture, it is only one piece of the puzzle. Studies show that a significant percentage of network server downtime is caused by transient faults in the I/O subsystem. These faults may be due, for example, to the device driver, the device firmware, or hardware which does not properly handle concurrent errors, and often causes servers to crash or hang. The result is hours of downtime per failure, while a system administrator discovers the failure, takes some action, and manually reboots the server. In many cases, data volumes on hard disk drives become corrupt and must be repaired when the volume is mounted. A dismount-and-mount cycle may result from the lack of “hot pluggability” or “hot plug” in current standards-based servers. Hot plug refers to the addition and swapping of peripheral adapters to an operational computer system. Diagnosing intermittent errors can be a frustrating and time-consuming process. For a system to deliver consistently high availability, it must be resilient to these types of faults.
[0010] In a typical PC-based server, upon the failure of an adapter, which is a printed circuit board containing microchips, the server must be powered down, the hot added adapter and adapter driver installed, the server powered back up and the operating system reconfigured.
[0011] However, various entities have tried to implement the hot plug of these adapters to a fault tolerant computer system. One significant difficulty in designing a hot plug system is protecting the circuitry contained on the adapter from being short-circuited when an adapter is added to a powered system. Typically, an adapter contains edge connectors which are located on one side of the printed circuit board. These edge connectors allow power to transfer from the system bus to the adapter, as well as supplying data paths between the bus and the adapter. These edge connectors fit into a slot on the bus on the computer system. A traditional hardware solution for “hot plug” systems includes increasing the length of at least one ground contact of the adapter, so that the ground contact on the edge connector is the first connector to contact the bus on insertion of the I/O adapter and the last connector to contact the bus on removal of the adapter. An example of such a solution is described in U.S. Pat. No. 5,210,855 to Thomas M. Bartol.
[0012] U.S. Pat. No. 5,579,491 to Jeffries discloses an alternative solution to the hot installation of I/O adapters. Here, each hotly installable adapter is configured with a user actuable initiator to request the hot removal of an adapter. The I/O adapter is first physically connected to a bus on the computer system. Subsequent to such connection a user toggles a switch on the I/O adapter which sends a signal to the bus controller. The signal indicates to the bus controller that the user has added an I/O adapter. The bus controller then alerts the user through a light emitting diode (LED) whether the adapter can be installed on the bus.
[0013] However, the invention disclosed in the Jeffries patent also contains several limitations. It requires the physical modification of the adapter to be hotly installed. Another limitation is that the Jeffries patent does not teach the hot addition of hot added adapter controllers or bus systems. Moreover, the Jeffries patent requires that before an I/O adapter is removed, another I/O adapter must either be free and spare or free and redundant. Therefore, if there was no free adapter, hot removal of an adapter is impossible until the user added another adapter to the computer system.
[0014] Hardware developers have recently created the Intelligent I/O (I2O) architecture to facilitate the development of hot added adapters for servers. Traditionally, a computer has one processor for handling machine instructions. This processor is called the central processing unit (CPU). The I2O architecture defines a hardware topology in which a secondary processor in addition to the usual CPU is provided for handling I/O transactions. The secondary processor is located on an input/output platform (IOP) which controls a plurality of I/O devices. The architecture also defines a split device driver model wherein an operating system module (OSM) with operating system code is located on the host CPU and a device driver module (DDM) is located on the IOP to control I/O devices. The OSM and the DDM communicate with each other through a messaging layer which is defined by the I2O architecture. The split device driver architecture allows operating system vendors and hardware vendors to each provide only one module for each type of adapter. Thus, an OSM for a LAN adapter is compatible with all classes of LAN adapters, and similarly the DDM provided by the hardware vendor for the LAN device is compatible with all I2O compliant operating systems.
[0015] Recently, the I2O architecture has been amended to define some hot plug primitives by which an operating system can request the hot add and removal of a IOP or an adapter which is located on the IOP. However, the I2O architecture has failed to define or describe the mechanism by which the configuration information of the added or swapped device is maintained. Moreover, the I2O architecture fails to solve the problem of how devices are to be added under the Peripheral Component Interconnect (PCI) architecture. In the PCI architecture, a bus address, a set of memory addresses, and a set of I/O memory addresses for each memory device have to be configured for a particular range depending on the physical location of each of the devices. The bus number, memory address, and the I/O memory addresses are traditionally defined upon the start-up of the computer. If a PCI device is added at a subsequent time, the system must be able to allocate resources for the newly added device appropriate for the slot in which the device is located. However, traditional system initialization routines fail to reserve bus address, memory addresses, and I/O memory for the new device.
[0016] Further, current operating systems do not by themselves provide the support users need to hot add and swap an adapter under the I2O architecture. System users need software that will freeze and resume the communications of their adapters in a controlled way. The software needs to support the hot add of various peripheral adapters such as mass storage and network adapters. Additionally, the software should support adapters that are designed for various bus systems such as Peripheral Component Interconnect, CardBus, Microchannel, Industrial Standard Architecture (ISA), and Extended ISA (EISA). System users also need software to support the hot add and swap of input/output platforms with embedded adapters.
[0017] A related technology, not to be confused with hot plug systems using the I2O architecture, is Plug and Play defined by Microsoft and PC product vendors. Plug and Play is an architecture that facilitates the integration of PC hardware adapters to systems. Plug and Play adapters are able to identify themselves to the computer system after the user installs the adapter on the bus. Plug and Play adapters are also able to identify the hardware resources that they need for operation. Once this information is supplied to the operating system, the operating system can load the adapter drivers for the adapter that the user had added while the system was in a non-powered state. Plug and Play is used by both Windows 95 and Windows NT to configure adapter cards at boot-time. Plug and Play is also used by Windows 95 to configure devices in a docking station when a hot notebook computer is inserted into or removed from a docking station.
[0018] Therefore, a need exists for improvements in server management of I2O devices which will result in continuous operation despite adapter failures. System users must be able to replace failed components, upgrade outdated components, and add new functionality, such as new network interfaces, disk interface adapters and storage, without impacting existing users. Additionally, system users need a process to hot add their legacy adapters on I2O platforms, without purchasing hot added adapters that are specifically designed for hot plug. As system demands grow, organizations must frequently expand, or scale, their computing infrastructure, adding new processing power, memory, mass storage and network adapters. With demand for 24-hour access to critical, server-based information resources, planned system downtime for system service or expansion has become unacceptable.
Summary of the Invention
[0019] One embodiment of the invention includes a method of hot adding an adapter to an expansion bus of an operational input/output platform, comprising adding an adapter to a slot in an expansion bus of an input/output platform which is connected to an operational computer, and activating the adapter so that I/O is communicated between the added adapter and the operational computer.
[0020] Another embodiment of the invention includes a method of hot adding an input/output platform to an operational computer including a plurality of bus slots, comprising adding an input/output platform to a selected one of the bus slots having a non-powered state, enabling power to the bus slot, and initiating communications between the computer and the input/output platform.
[0021] Another embodiment of the invention includes a method of hot swapping an adapter to a bus controlled by an input/output platform, comprising suspending all communication to the adapter, removing the adapter, swapping a hot added adapter into the computer, and restarting communications between the computer and the hot added adapter.
[0022] Yet another embodiment of the invention includes a method of hot swapping an input/output platform having at least one embedded adapter, comprising saving the configuration information of the at least one embedded adapter, disabling power to the input/output platform, removing the selected input/output platform from the computer, swapping a new input/output platform into the computer at the same location as the selected input/output platform, enabling power to the new input/output platform, and initiating communications between the computer and the new input/output platform.
[0023] Yet another embodiment of the invention includes a method of hot swapping an input/output platform having at least one embedded adapter, comprising sparsely allocating the resources of a computer, suspending any communication between the computer and the input/output platform, saving the configuration information of the at least one embedded adapter, disabling power to the input/output platform, removing the selected input/output platform from the computer, swapping a new input/output platform into the computer at the same location as the selected input/output platform, enabling power to the new input/output platform, and initiating communications between the computer and the new input/output platform.
Brief Description of the Drawings
[0024] FIG. 1 is a top-level block diagram showing a fault tolerant computer system, including an input/output platform (IOP).
[0025] FIG. 2 is a block diagram showing a first embodiment of a multiple bus configuration connecting I/O adapters and a network of microcontrollers to the clustered CPUs of the fault tolerant computer system, shown in FIG. 1.
[0026] FIG. 3 is a block diagram showing a second embodiment of a multiple bus configuration connecting canisters containing I/O adapters and a network of microcontrollers to the clustered CPUs of the fault tolerant computer system, shown in FIG. 1.
[0027] FIG. 4 is a block diagram illustrating a portion of the fault tolerant computer system, shown in FIG. 1.
[0028] FIG. 5 is a block diagram illustrating two different intelligent I/O (I2O) subsystems in a computer system.
[0029] FIG. 6 is a block diagram illustrating certain device driver components of the NetWare Operating System and one embodiment of a configuration manager which reside on the fault tolerant computer system, shown in FIG. 1.
[0030] FIG. 7 is an operational flowchart illustrating the process by which a user performs a hot add of an IOP such as is shown in FIG. 5.
[0031] FIG. 8 is an operational flowchart showing the process by which a user performs a hot add of an adapter on the expansion bus of an IOP.
[0032] FIG. 9 is an operational flowchart showing the process by which a user performs a hot swap of an IOP or an adapter on the expansion bus of an IOP.
[0033] FIG. 10 is a block diagram of a memory structure including configuration information about an IOP and the devices which have controlled the IOP.
[0034] FIGS. 11A and 11B are a flowchart depicting the process followed in one embodiment of the invention for creating the configuration space data structure depicted in FIG. 10.
[0035] FIGS. 12A and 12B are a flowchart depicting the process followed in one embodiment of the invention relating to the hot add of an adapter or IOP in a computer system such as shown in FIG. 1.
[0036] FIG. 13 is a flowchart depicting the process followed in one embodiment of the invention relating to hot swap of an adapter or IOP in a computer system such as is shown in FIG. 1.
Detailed Description of the Invention
[0037] The following detailed description presents a description of certain specific embodiments of the present invention. However, the present invention can be embodied in a multitude of different ways as defined and covered by the claims. In this description, reference is made to the drawings wherein like parts are designated with like numerals throughout.
[0038] FIG. 1 is a block diagram showing one embodiment of a fault tolerant computer system. Typically the computer system is one server in a network of servers and is communicating with client computers. Such a configuration of computers is often referred to as a client-server architecture. A fault tolerant server is useful for mission critical applications such as the securities business where any computer down time can result in catastrophic financial consequences. A fault tolerant computer will allow for a fault to be isolated and not propagate through the system thus providing complete or minimal disruption to continuing operation. Fault tolerant systems also provide redundant components, such as adapters, so service can continue even when one component fails.
[0039] The system includes a fault tolerant computer system 100 having an I/O platform (IOP) 103. An IOP 103 comprises a processor, a memory, and at least one I/O adapter (not shown in FIG. 1). The IOP 103 is managed independently from other processors in the system and is configured to process I/O transactions. The IOP 103 controls a mass storage adapter 102 and a network adapter 104 such as for use in a Local Area Network (LAN). The mass storage adapter 102 may contain one or more of various types of device controllers: a magnetic disk controller 108 for magnetic disks 110, an optical disk controller 112 for optical disks 114, a magnetic tape controller 116 for magnetic tapes 118, a printer controller I2O for various printers 122, and any other type of controller 124 for other devices 126. For such multi-function adapters, the controllers may be connected by a bus 106 such as a PCI bus. The peripheral devices communicate and are connected to each controller, by a mass storage bus. In one embodiment, the bus may be a Small Computer System Interface (SCSI) bus. In a typical server configuration there is more than one mass storage adapter connected to the computer 100. Adapters and I/O devices are off-the-shelf products. For instance, sample vendors for a magnetic disk controller 108 and magnetic disks 110 include Qlogic, Intel, and Adaptec. Each magnetic hard disk may hold multiple Gigabytes of data.
[0040] The network adapter 104, which is sometimes referred to as a network interface card (NIC), allows digital communication between the fault tolerant computer system 100 and other computers (not shown) such as a network of servers via a connection 130. In certain configurations there may be more than one network controller adapter connected to the computer 100. For LAN embodiments of the network adapter, the protocol used may be, for example, Ethernet (IEEE 802.3), Token Ring (IEEE 802.5), Fiber Distributed Datalink Interface (FDDI), Asynchronous Transfer Mode (ATM) or any other conventional protocol. Typically, the mass storage adapter 102 and the network adapter 104 are connected to the computer using a standards-based bus system. In different embodiments of the present invention, the standards based bus system could be Peripheral Component Interconnect (PCI), Microchannel, SCSI, Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures.
[0041] FIG. 2 shows one embodiment of the bus structure of the fault tolerant computer system 100. A number ‘n’ of central processing units (CPUs) 200 are connected through a host bus 202 to a memory controller 204, which allows for access to memory by the other system components. In one embodiment, there are four CPUs 200, each being an Intel Pentium Pro or Pentium II microprocessor. However, many other general purpose or special purpose parts and circuits could be used. A number of bridges 206, 208 and 210 connect the host bus to, respectively, three high speed I/O bus systems 212, 214, and 216. The bus systems 212, 214 and 216, referred to as PC buses, may be any standards-based bus system such as PCI, ISA, EISA and Microchannel. In one embodiment of the invention, the bus system 212 is PCI. Alternative embodiments of the invention employ a proprietary bus. An ISA Bridge 218 is connected to the bus system 212 to support legacy devices such as a keyboard, one or more floppy disk drives and a mouse. A network of microcontrollers 225 is also interfaced to the ISA bus 226 to monitor and diagnose the environmental health of the fault tolerant system. A more detailed description of the microcontroller network 225 is contained in the U.S. patent application Ser. No. 08/942,402, “Diagnostic and Managing Distributed Processor System” to Johnson. Other embodiments may not use the network 225.
[0042] A bridge 230 and a bridge 232 connects, respectively, the PC bus 214 with PC bus 234 and the PC bus 216 with the PC bus 236 to provide expansion slots for peripheral devices or adapters. Separating the devices 238 and 240, respectively, on PC buses 234 and 236 reduces the potential that an adapter failure or other transient I/O error affect the entire bus and corrupt data, bring the entire system down or stop the system administrator from communicating with the system. The devices 238 and 240 are electrically and mechanically connected to the PC buses 234 and 236 by PC slots such as slot 241. Hence, an adapter is “plugged” into a slot. In one embodiment of the invention, each slot may be independently powered on and off.
[0043] FIG. 3 shows an alternative bus structure embodiment of the fault tolerant computer system 100. The two PC buses 214 and 216 contain a set of bridges 242-248 to a set of PC bus systems 250-256. As with the PC buses 214 and 216, the PC buses 250-256 can be designed according to any type of bus architecture including PCI, ISA, EISA, and Microchannel. The PC buses 250-256 are connected, respectively, to a canister 258, 260, 262 and 264. The canisters 258-264 are casings for a detachable bus system and provide multiple PC slots 266 for adapters. In one embodiment, each canister may be independently powered on and off.
[0044] The embodiments of the invention illustrated with respect to FIGS. 2 and 3 both provide for the sparse allocation of system resources upon the initialization or boot-up of the computer system 100. For example, referring to FIG. 3, the computer system 100 sparsely apportions the bus numbers for each of the buses 250-256 that are on the system during initialization. Thus, the computer system 100 assigns a range of bus numbers for each of the buses, thereby allowing the future assignment of additional bus numbers for a secondary bus that may be inserted into one of the bus slots.
[0045] Similarly, the I/O addresses and the memory are sparsely allocated for each of the buses and the devices. Each of the bus systems is assigned a range of addresses for memory and I/O. Thus, when a new device is placed in one of the bus slots, memory and I/O may be allocated for the adapter from this range of memory without the risk that other adapters from a different bus have reserved all of the space dedicated to the bus.
[0046] FIG. 4 is a block diagram illustrating hardware and software components of the computer system 100 relating to hot plugging an adapter. A hot plug user interface 302 accepts requests by a user such as a system manager or administrator to perform the hot add or a hot swap of an adapter 310. The user interface 302 preferably communicates through an industry standard operating system 304 such as NetWare, to the hot plug system driver 306 and an adapter driver 308. In an alternative embodiment of the invention, a proprietary operating system may be utilized.
[0047] The hot plug system driver 306 controls the adapter driver 308 for a hot plug operation. The hot plug system driver 306 stops and resumes the communications between the adapter 310 and the adapter driver 308. During a hot add or swap of the adapter 310, the hot plug hardware 312 deactivates the power to the PC slots 241 and 266 (FIGS. 2 and 3). One embodiment of the hot plug hardware 312 may include the network of microcontrollers 225 (FIGS. 2 and 3) to carry out this functionality.
[0048] The adapter 310 could be any type of peripheral device such as a network adapter, a mass storage adapter, or a sound board. Typically, however, adapters involved in providing service to client computers over a network, such as mass storage, network and communications adapters, would be the primary candidates for hot swapping or adding in a fault tolerant computer system such as the computer system 100 (FIG. 1). Further, the adapter 310 could be an IOP device as defined by the I2O architecture. The adapter 310 is physically connected to the hot plug hardware by PC slots such as slots 241 and 266 (FIGS. 2 and 3).
[0049] FIG. 5 is a block diagram illustrating two different types of intelligent I/O (I2O) subsystems with hot plug functionality. Each of these two subsystems may act as the IOP 103 of FIG. 1. A first subsystem 401 has an I/O platform (IOP) 400 including a plurality of embedded adapters 402. The IOP 400 including its adapters 402 is hot pluggable. A second subsystem 407 includes an IOP 406 having an expansion bus 408 for the hot add and swap of an adapter 410. Although only one adapter 410 is illustrated in the subsystem 407, more than one adapter 410 may be located on the expansion bus 408. Each of the adapters 410 which are located on the expansion bus 408 are hot pluggable. For the purposes of discussion, the IOP 406 of subsystem 407 will be assumed to be not configured to be hot pluggable. However, the IOP 406 could readily be made hot pluggable.
[0050] The adapters 402 and 410 may include various types of device controllers, such as: a magnetic disk controller for magnetic disks, an optical disk controller for optical disks, a magnetic tape controller for magnetic tapes, a printer controller for various printers, and any other type of controller for other devices (not shown in FIG. 5). Further, the adapters 402 and 410 may include a network adapter, which allows digital communication between a host 404 and other computers (not shown). The IOP 400 and 406 may, in one embodiment, be any industry standard I/O adapter such as, for example, the Intel IQ80960RP, the Intel IQ80960RD66, or the Cyclone PCI914.
[0051] FIG. 6 is a block diagram illustrating certain system components of the NetWare Operating System and the software components of one embodiment of the invention. A configuration manager 500 is responsible for managing all or some of the adapters 402 and 410 (FIG. 5). The configuration manager 500 keeps track of the configuration information for every managed adapter located on the fault tolerant computer system 100 shown in FIG. 1. The configuration manager 500 also allocates resources for every managed adapter and initializes each managed adapter's registers during a hot swap or add operation. The registers of an adapter 310 are memory addresses which may be used to issue a command to the adapter, or which may indicate the status of the adapter.
[0052] Novell provides two drivers for adapters, including a network device driver 524 and a mass storage driver 526. Each of these two drivers define an interface, called operating system modules (OSMs) for I2O device driver modules (DDM) to communicate with the NetWare Operating System. First, Novell provides a LAN class OSM 504 for network adapter device drivers. Second, Novell provides a block storage OSM 512 for mass storage adapter device drivers. Each of these interfaces will be described below.
[0053] With respect to network device drivers, such as a driver 524, the LAN class OSM 504 is used by the NetWare operating to communicate with an the LAN class DDM 506. The LAN class OSM 504 allows multiple LAN adapters, such as the adapter 104 (FIG. 1) to co-exist on network systems, and to facilitate the task of writing device driver software. The I2O specification promulgated by the I2O Special Interest Group (SIG) describes the set of interfaces and software modules used by hardware vendors to interface with the LAN class OSM 504. The LSL 502 is the interface between drivers and protocol stacks (not shown). A protocol stack is well known software having a layered communication architecture, whereby each layer has a well defined interface.
[0054] The LAN class DDM 506 executes on an IOP, such as IOP 400 or IOP 407 shown in FIG. 5. An instance of a LAN class DDM 506 exists for each LAN adapter which is controlled by the IOP. Typically, a LAN adapter vendor provides a DDM for each class of device. The LAN class DDM 506 contains no operating system specific code. For instance, the DDM does not directly interface to Novell NetWare or any other OS running in the computer. The LAN class DDM 506 communicates with the LAN Class OSM 504 through a messaging layer which is defined by the I2O architecture. These messages correspond to primitives which allow the hot add and hot swap of adapters plugged into slots controlled by an IOP.
[0055] With respect to mass storage device drivers, such as a driver 526, the NetWare Peripheral Architecture (NWPA) 518 is a software architecture developed by Novell which provides an interface for mass storage developers to interface with the NetWare operating system. The NWPA 518 is divided into two components: a block storage OSM 512 and a custom device module (CDM) 513.
[0056] Similar to the LAN class DDM 506 for network devices, a block storage DDM 514 provides the interface to the mass storage adapters and their devices. The block storage OSM 512 contains no operating system specific code. The block storage DDM 514 communicates with the block storage OSM 512 through an messaging layer which is defined by the I2O architecture. Typically, a mass storage adapter vendor provides the block storage DDM 514. The CDM 513 is the component of the NWPA 518 that regulates the mass storage adapters 102.
[0057] A filter CDM 516, which is not typically a part of the Novell NetWare Operating System, is used to locate the block storage OSM 512, register adapter events, and process the I/O suspend and I/O restart requests from the configuration manager 500. To be noted, the process of making and using the filter CDM is commonly known in the device driver technology.
[0058] If a user desires to perform a hot swap of a device, a NetWare user interface 518 is used to request the configuration manager 500 to freeze and restart communications to a specified adapter 310. A remote Simple Network Management Protocol (SNMP) agent 520 can also start the request to freeze and resume communications to the configuration manager 500 through a local SNMP agent 521. SNMP is one of a set of protocols called TCP/IP, which is specifically designed for use in managing computer systems. In one embodiment of the invention, the computers would be similar to the fault tolerant computer system of FIG. 1 and connected in a server network via connection 130.
[0059] FIGS. 7, 8, and 9 illustrate a generic process by which alternative embodiments of the present invention perform the hot add and swap of devices. Embodiments of the invention may use commercial operating systems, such as Macintosh O.S., OS/2, VMS, DOS, Windows 3.1/95/98 or UNIX to support hot add and swap. Furthermore, proprietary operating systems may support hot add and hot swap. However, the description of FIGS. 7, 8 and 9 will refer to the hot add and swap of I2O compliant devices under the NetWare Operating System.
[0060] Referring now to FIG. 7, a flowchart of one embodiment of the process to hot add an IOP with embedded devices, such as IOP 400 of FIG. 5, is illustrated. The process described by FIG. 7 is generic to various implementations of the invention. However, the following description of FIG. 7 focuses on the hot add of an IOP (FIG. 5) under the NetWare Operating System.
[0061] Starting in state 600, a user inserts an IOP into one of the PC bus slots, such as the slot 241. At this point, the hot plug hardware 312 has not turned on the power to the IOP's slot, although the computer system 100 is operational. Since the IOP's slot is not powered and is physically isolated from any other devices which are attached to the bus 234, the IOP will not be damaged by a short circuit during the insertion process, and will not create problems for the normal operation of the computer system 100.
[0062] Moving to state 602, the configuration manager 500 (FIG. 6) is notified that the IOP is now in the slot, and requests the hot plug hardware 312 (FIG. 4) to supply power to the IOP's slot. In one embodiment of the invention, the hot plug hardware 312 automatically detects the presence of the newly added IOP and informs the configuration manager 500. In another embodiment of the invention, the user notifies the hot plug hardware 312 that the IOP is connected to one of the PC slots 241 (FIG. 2).
[0063] Once an IOP is added to the computer system, the configuration manager 500 asserts a bus reset which initializes the IOP at a state 603. System resources must now be allocated for the IOP and for the adapters that are embedded on the IOP. The configuration manager 500 initializes the new IOP and provides it with the information about any other IOPs that may be on the system. The configuration manager 500 configures the newly added adapters on the IOP by writing information to each hot added adapters' configuration space registers (state 604).
[0064] Traditionally, each adapter's resources on the IOP are allocated by the Basic Input Output Services (BIOS) which is typically stored in a nonvolatile memory in the computer system 100. The BIOS are software service routines which are invoked during the boot up of the computer system 100. The BIOS programs the I/O ports, or memory locations of each adapter on the computer system 100. However, since a hot added adapter was not present during the execution of the BIOS initialization routines, the configuration manager 500 must configure the hot added adapter in the same manner that a preconfigured adapter is programmed by the BIOS. The process for configuring the adapters on the IOP is explained in greater detail below in reference to FIGS. 12A and 12B.
[0065] Finally, at a state 605, the process of the configuration manager 500 loads an appropriate OSM depending on the type of adapter on the new IOP. For example, if the IOP contains a LAN adapter, the configuration manager 500 will load the LAN class OSM 504 into the memory of the computer 100.
[0066] FIG. 8 is a flowchart illustrating the process for hot add of an adapter on the expansion bus of an IOP. The process described by FIG. 8 is generic to various embodiments of the invention. However, the following description of FIG. 8 will generally refer to the hot add of an adapter to the expansion bus subsystem 407 of FIG. 5 under the NetWare Operating System.
[0067] Starting in state 700, all adapters already operating on the expansion bus 408 are located, and I/O activity involving those adapters is suspended. In one embodiment, the SNMP agent 520 (FIG. 6) or the NetWare User Interface 518 locates all of the adapters, and initiates the request for the suspension for every adapter, such as the adapter 410, on the expansion bus 408. In another embodiment, the SNMP agent 520 or the NetWare User Interface 518 requests the configuration manager 500 to suspend the adapters. The configuration manager 500 then locates all devices and suspends the I/O for each adapter located on the expansion bus 408.
[0068] The configuration manager 500 initiates the suspension of I/O by sending a shutdown command to either the NWPA 518 for the mass storage adapters 102 or the LSL 502 for the network adapter 104. The purpose of the suspension is to provide an orderly shutdown of the communications between the IOP and the other adapters on the expansion bus, since at a state 710 the bus will be reset.
[0069] Proceeding to state 706, the user inserts an adapter into one of the expansion slots on the expansion bus 408. The hot plug hardware 312 (FIG. 4) then restarts, at the request of the configuration manager 500, the power to the slot of the hot added adapter (state 708). The bus reset bit is then asserted (state 710) to cause the IOP to re-initialize each of the adapters on the expansion bus 408. In one embodiment of the invention, this assertion is accomplished by the hot plug hardware 312. In another embodiment, the configuration manager 500 asserts the bus reset. The configuration manager 500 re-initializes the configuration space of each adapter that is on the expansion bus 408 (state 712).
[0070] Moving to state 714, the configuration manager 500 programs the configuration space of the hot added adapter. It is noted, since an adapter has no power before a hot add, the adapter is in an unknown state after reapplying power. The configuration process for the adapters after the hot add of an adapter is described in greater detail in reference to FIGS. 12A and 12B.
[0071] Finally, the configuration manager 500 resumes operations to all of the adapters located on the expansion bus (state 718). For mass storage adapters 102, the configuration manager 500 notifies the NWPA 518 to resume communications with the mass storage adapters 102. For network adapters 104, the configuration manager 500 notifies the LSL 502 to resume communications with the network adapters 104. In some embodiments of the invention, the configuration manager 500 restarts I/O to all adapters on the expansion bus 408 per such a request to resume communications, while in other embodiments, the user interface 518 or SNMP agent 522 requests the configuration manger 500 to restart each adapter. Finally, at a state 720 the configuration manager 500 loads the appropriate OSM for the hot added adapter.
[0072] FIG. 9 is an operational flowchart illustrating the process by which a user performs the hot swap of an IOP 401 (FIG. 5) having embedded adapters or an adapter controlled by an IOP 406 (FIG. 5). The process described by FIG. 9 is generic to various implementations of the invention. However, the following description of FIG. 9 focuses on the hot swap of an IOP with embedded adapters or an adapter controlled by an IOP under the NetWare Operating System.
[0073] In general, before starting in state 800, an event has occurred, such as a failure of an adapter, and the user has been informed of the failure. The user has procured a replacement part, and is determined to repair the computer system 100 at this time. The operator may have some other reason for deciding to remove and replace a card, such as upgrading to a new version of the card or its firmware. A user indicates his intention to swap an adapter through the NetWare user interface 518 or a remote SNMP agent 528 (FIG. 6) (state 800).
[0074] The configuration manager 500 then suspends the communication between the IOP or adapter, which is to be swapped, and the OSM 504, 512 (state 802). If an IOP is to be swapped, all of the adapters which are controlled by the IOP are also suspended.
[0075] Next, for IOP swappable systems, the hot plug hardware 312 asserts a bus reset before disabling power (state 804). In other embodiments, the configuration manager 500 specifically causes a bus reset to be asserted before directing the hot plug hardware 318 to remove power.
[0076] The hot plug hardware 312 (FIG. 4) is then directed by the configuration manager 500 to suspend the power to the device which is to be swapped, whether it is the IOP itself or the adapter which is on the expansion bus of the IOP. Proceeding to state 808, the user swaps the old IOP or adapter with a new one.
[0077] Continuing to a state 810, the hot plug hardware 312 (FIG. 4) reapplies power to the slot of the new device. If an IOP was swapped, the hot plug hardware 312 re-asserts the bus reset bit, if necessary, after applying power (state 812). In other embodiments, the configuration manager 500 must specifically re-assert the bus reset.
[0078] Next, at a state 814, if an adapter was swapped, the configuration manager 500 reprograms the configuration space of the replaced adapter to the same configuration as the old adapter (state 814). If an IOP was swapped, the configuration manager 500 reprograms the configuration space and resumes the communication of each adapter located on the new IOP (state 814). Finally, at state 816, the configuration manager 500 changes the state of all of the adapters to active.
[0079] Referring to FIG. 10, the configuration manager 500 (FIG. 6) maintains a data structure 1002 in the computer memory which is in the form of an array with each array element, e.g., 1004, of the array representing a PCI bus in the system. Each element of the array 1002 is referred to as a PCI bus information structure. A device information list 1006 may be associated with the PCI bus information structure. The elements 1008 of the device information list 1006 represent devices on the PCI bus. In one embodiment, the data structure is located in the memory storage area of the operating system and is created and maintained by the configuration manager 500.
[0080] Each PCI bus array element 1004 may include the memory start and end locations 1010, 1012 for that bus, the I/O start and end locations 1024, 1026 for that bus, and a pointer 1018 to the device information list 1006 containing the configuration information for devices on that bus. In addition, the bus memory structure element 1004 may include the memory location of the last memory space 1020 assignment performed on that bus. The last memory space 1020 may be used when hot adding a device to the bus. In one embodiment, when memory is allocated for devices on a bus, the memory is allocated from the highest address to the lowest. Therefore, the last address allocated is also the smallest address allocated. Similarly, the last I/O address allocated 1022 may also be stored. The PCI bus information structure may also include configuration information defined by the PCI standard under which the system is operating.
[0081] Each element 1008 on the device information list 1006 associated with each PCI bus information structure is referred to as a device information structure. Each device information structure typically contains PCI configuration information for a specific device on the bus corresponding to the PCI bus information structure to which the device information list is attached. The PCI configuration information is governed by the PCI specification. As an example, the device information structure includes the PCI vendor identification, PCI device identification, PCI command, PCI status, PCI revision identification, PCI class code, PCI cache line size, PCI latency timer, and the base register addresses (BARs). Each device information structure in the device information list may also include a pointer 1009 to the next device information structure in the device information list or a null indicating the end of the list.
[0082] Each device information structure may include, if the device is an IOP, the memory start and end locations 1050, 1052 for the IOP, the I/O start and end locations 1056, 1058 for the IOP. In addition, the device information structure may include the memory location of the last memory space 1054 assignment performed on the IOP. The foregoing information may be used when hot adding a device to the IOP. In one embodiment, when memory is allocated for devices controlled by the IOP, the memory is allocated from the highest address to the lowest. Therefore, the last address allocated is also the smallest address allocated. Similarly, the last I/O address allocated 1060 may also be stored in that array structure.
[0083] Further, the device information structure may also include a child device list pointer 1032 to a second device information list 1030 of device information structures if the device is an IOP having an expansion bus or having embedded adapters. The second device information list 1030 contains the device information structures for the adapters that are controlled by an IOP.
[0084] FIGS. 11A and 11B depict flowcharts which illustrate one inventive method for creating the PCI configuration space data structure shown in FIG. 10. FIGS. 11A and 11B represent the states which may be accomplished by the configuration manager 500 (FIG. 6) operating within the computer system 100.
[0085] As indicated by state 1110, the process indicated and represented by FIGS. 11A and 11B is carried out for one or more buses on the computer system. At state 1112, space in the memory of the computer system 100 (FIG. 1) is allocated for the memory structure. This allocation can be performed at the time of compiling or dynamically.
[0086] Next, at state 1114 the predefined start and end memory addresses for the PCI bus are written to the array element 1004 (FIG. 10) representing that PCI bus. The start and end memory addresses may be the same as those used when the system is initialized by the BIOS program during system boot-up.
[0087] Then, at state 1116 the predefined start and end input/output (“I/O”) addresses and the interrupt assignment (ISA IRQ) for the bus are written in the appropriate locations in the array element representing the PCI bus. As with the start and end memory addresses, the start and end I/O addresses and the interrupt assignment may also be the same as those used by the BIOS program when the system was initialized.
[0088] As represented by states 1118, 1120, 1121, 1122, 1123 and 1124, a repeated process or loop is next performed where each device number from 0 to 31 and function number from 0 to 7 is reviewed sequentially to determine whether such a device exists on the current bus and whether that device supports more than one function as defined by the PCI standard. At the first part of that loop, at state 1118, a standard PCI configuration access (query) is performed, which determines whether, for example, device 0, is present on the bus. If a device is located with that device number, the process continues to state 1120 wherein the PCI configuration space information of that device is then read from that device including whether any other function numbers (0-7) are supported by the device.
[0089] Next, at state 1121 memory space is allocated for the device information structure for the device and the PCI configuration information read from the device is then copied into the allocated device information structure. At state 1122 that device information structure is linked into the list either by inserting a pointer into the corresponding bus information structure if this is the first device, or inserting the pointer into the next device location of the previous device information structure in the device information list for this bus.
[0090] Continuing to a state 1123, the configuration manager 500 checks whether the device provides a bridge to a second bus. If the device has a bridge, the configuration manager 500 allocates configuration space data structures for the adapters on the secondary side of the bridge at decision state 1142. However, if no bridge is found, the configuration manager 500 sets the child device list to NULL (state 1124). The process then returns to state 1118 where the system may attempt to locate the next PCI device on the bus. This process or loop may be repeated for each device on the PCI bus. In this manner, a device information list of PCI devices with each element in the list containing configuration information is created in the form depicted in FIG. 10.
[0091] Referring now to the state 1142, the configuration manager 500 having determined that the device has a bridge, the configuration manager 500 attempts to allocate configuration space date structures for the adapters on the secondary side of the bridge. As represented by states 1142, 1144, 1146 and 1148, a repeated process or loop is next performed where each device number from 0 to 31 and function number from 0 to 7 is reviewed sequentially on the secondary side of the bridge to determine whether such a device exists on the secondary side and whether that device supports more than one function. At the first part of that loop, at decision state 1142, a standard PCI configuration access (query) is performed, which determines whether, for example, device 0, is present on the secondary side. If a device is located with that device number, the process continues to state 1144 wherein the PCI configuration space information of that device is then read from that device including whether any other function numbers (0-7) are supported by the device.
[0092] Next, at state 1146 memory space is allocated for the device information structure for that device and the PCI configuration information read from the device is then copied into the allocated device information structure. At state 1148 that device information structure is linked into the child device list 1032 (FIG. 10) either by inserting a pointer into the child device list 1032 if this is the first device, or inserting the pointer into the next device location of the previous device information structure in the child device list 1032.
[0093] The process then returns to decision state 1142 where the system may attempt to locate the next PCI device on the secondary side of the bridge. This process or loop may be repeated for each device on the secondary side of the bridge. In this manner, a child device list 1032 of PCI devices with each element in the list containing configuration information is created in the form depicted in FIG. 10.
[0094] After the last PCI device on the bus has been added to the child device list, the process proceeds to state 1150. In this state, the last I/O address 1060 in the device information structure 1008 (see FIG. 10) and the last memory address 1054 in the PCI bus information structure are set, respectively, to the memory end 1052 and the I/O end 1058 addresses.
[0095] Next, in state 1152, the amount of memory and I/O address space used by all of the PCI devices on the secondary bus may be determined. In one embodiment, the amount of memory and I/O address space used is determined by tracking the last memory and I/O address space assigned. The process for making those determinations is performed in states 1154 through 1164. Generally speaking, the process for determining the amount of memory an I/O address used by the PCI devices on the secondary bus includes looking at each of the base address registers on each of the devices on the secondary bus and determining the lowest base address register value for an I/O and the lowest base address register value for memory.
[0096] Specifically, at state 1154, the process locates the first device information structure on the bus by scanning the device information list 1030 attached to the device information structure or, if the first device information structure has already been processed, the process looks for the next device information structure. If no device information structure is found, the process is complete.
[0097] When a device information structure is located at state 1154, the data in the device information structure representing the first base address register is read (state 1158). If the first base address register has already been read, the process attempts to read the next base address register. If no further base address registers exist, the process then returns to state 1154.
[0098] When a base register is found and read in state 1158, the process proceeds to the state represented by state 1160. Under the PCI configuration standard, if the low order bit of a base address register is set, then that base register represents an I/O address and the process then proceeds to state 1164. In state 1164, the base address register contents are masked with the hexadecimal number 0xFFFFFFFE (per the PCI specification) and a comparison is made between that value and the last I/O address in the device information structure. If that masked value is a lower value, it is then written to the last I/O address in the bus information structure. The process then returns to state 1158.
[0099] However, if the low order bit in the base address register is not set, then the base address register represents a memory address and the process proceeds to state 1162. In state 1162, the contents of the base address register are masked with the hexadecimal number 0xFFFFFFF0 (per the PCI specification) and then compared with the contents of the last memory address in the device information structure. If that masked value is a lower value, it is then written to the last memory address in the bus information structure. The process then returns to state 1158.
[0100] As represented by state 1158, this process is repeated for each of the base registers located on a device. After the last base address register has been analyzed according to states 1160, 1162, 1164, the process returns to state 1154 and the foregoing process is repeated for each device on the bus. This process thereby determines the lowest address for both I/O and memory used by the devices on the secondary bus. The process proceeds in this manner because memory for the devices is allocated from the highest address to the lowest. After this has been completed, the PCI configuration initialization process for the IOP is completed (state 1156). The configuration manager 500 then proceeds to decision state 1118 (FIG. 11A) to look for other devices on the primary bus.
[0101] After the last PCI device on the primary bus has been added to the device information list, the process proceeds to state 1126. In this state, the last I/O address in the PCI bus information structure 1022 (see FIG. 4) and the last memory address 1020 in the PCI bus information structure are set, respectively, to the memory end 1012 and the I/O end 1016 addresses.
[0102] Next, in state 1128, the amount of memory and I/O address space used by all of the PCI devices on the bus may be determined. In one embodiment, the amount of memory and I/O address space used is determined by tracking the last memory and I/O address space assigned. The process for making those determinations is performed in states 1130 through 1140. Generally speaking, the process for determining the amount of memory an I/O address used by the PCI devices on the bus includes reading each of the base address registers on each of the devices on the bus and determining the lowest base address register value for an I/O and the lowest base address register value for memory.
[0103] Specifically, at state 1130, the process locates the first device information structure on the bus by scanning the device information list attached to the bus information structure or, if the first device information structure has already been processed, the process looks for the next device information structure. If no device information structure is found, the process is complete.
[0104] When a device information structure is located at state 1130, the data in the device information structure representing the first base address register is read (state 1134). If the first base address register has already been read, the process attempts to read the next base address register. If no further base address registers exist, the process then returns to state 1130.
[0105] When a base register (not shown) is found and read in state 1134, the process proceeds to the state represented by state 1136. Under the PCI configuration standard, if the low order bit of a base address register is set, then that base register represents an I/O address and the process then proceeds to state 1140. In state 1140, the base address register contents are masked with the hexadecimal number 0xFFFFFFFE (per the PCI specification) and a comparison is made between that value and the last I/O address in the bus information structure. If that masked value is a lower value, it is then written to the last I/O address in the bus information structure. The process then returns to state 1134.
[0106] However, if the low order bit in the base address register is not set, then the base address register represents a memory address and the process proceeds to state 1138. In state 1138, the contents of the base address register are masked with the hexadecimal number 0xFFFFFFF0 (per the PCI specification) and then compared with the contents of the last memory address in the bus information structure. If that masked value is a lower value, it is then written to the last memory address in the bus information structure. The process then returns to state 1134.
[0107] As represented by state 1134, this process is repeated for each of the base registers located on a device. After the last base address register has been analyzed according to states 1136, 1138, 1140, the process returns to state 1130 and the foregoing process is repeated for each device on the bus. This process thereby determines the lowest address for both I/O and memory used by the devices on the bus. The process proceeds in this manner because memory for the devices is allocated from the highest address to the lowest. After this has been completed, the PCI configuration initialization process is completed.
[0108] Referring now to FIGS. 12A and 12B, the process for programming the configuration space of a device during a hot addition will be described. The device may consist of an IOP or an adapter which is controlled by an IOP. FIGS. 12A and 12B describe in greater detail the state 604 of FIG. 7 and states 712 and 714 of FIG. 8. The flowcharts represent the states which may be accomplished by the configuration manager 500 operating within the computer system.
[0109] In general, the process for performing a hot add is similar to the states that occur with regard to each device on a bus during system initialization associated with boot-up. However, generally speaking, the process differs in that rather than initializing every device in the system, the capability exists to initialize any device because configuration information is available and maintained in the PCI configuration space by the configuration manager 500.
[0110] First, at state 1220, a system query is sent to attempt to locate or read the newly added IOP or adapter. If the IOP or adapter cannot be read by the system, the process continues to state 1222, wherein the power to that slot is turned off. Next, at state 1224, an error message is generated and the process ends.
[0111] However, if the device is located in response to the system query, the process proceeds to state 1225, wherein, memory space is allocated for what will be the device information structure for the newly added device. Since a hotly added IOP may have multiple embedded adapters, the configuration manager 500 must configure each of the adapters on the IOP. Thus, the states 1225-1272 are followed for each adapter on the IOP. However, the following description will, for the sake of simplicity, describe the configuration process for a single adapter.
[0112] Next, at state 1226, the configuration information that is stored on the adapter is read. Typically, this information includes the vendor identification, and the amounts and types of memory required by the device. At state 1228 that information is written to the memory location allocated in state 1225.
[0113] Next, as represented generally by state 1228, the base address registers of the adapter are programmed. Specifically, at state 1230, the first base address register is read in accordance with the PCI specification. This may be accomplished by writing 0xFFFFFFFF to the base address register and then reading the base address register. Next, at state 1232, if no base address registers remain (i.e., if all of the base address registers have already been read), the configuration manager 500 continues on to the sequence of states starting at state 1274. However, when the base address register is being read, the process continues to state 1234.
[0114] At state 1234, if the low order bit of the base register is set (equals 1) then that base address register represents an I/O address and the process continues to the series of states beginning with state 1252 and continuing on FIG. 12B which are described below. Alternatively, if the lower order bit is not set, the base address register is a memory base address register and the system proceeds to state 1236.
[0115] At state 1236, the four low order bits from the base address register are masked as a preliminary step to determining the size of the memory required by the base address register. The determination of the amount of memory required by the base address register is commonly known to those of ordinary skill in the art as part of the standards of the PCI bus architecture and is therefore only outlined here.
[0116] Next, at state 1238, the amount of memory required by the base address register is determined. Then, at state 1240 the memory assignment for the base address register is determined with reference to the last memory address 1020 in the bus information structure.
[0117] Next, as represented by state 1242, after the memory assignment for the base address register is determined, the memory assignment is compared to the memory start address 1010 stored in the PCI bus information structure for that bus to ensure that the memory being assigned to that base address register is within the range allocated for devices on that bus. If an error is encountered, the configuration managers ends at a state 1243. Otherwise, if the memory is allocated within a valid range, in states 1246, 1248 and 1250, the proper value is written to the base address register according to the sequence of states defined by the PCI specification.
[0118] Specifically, in state 1246, the memory assignment for the base address register is written to the base address register. Then, at state 1248, the base address register is read and at state 1250, that value is used to set the last memory address 1020 (see FIG. 10) in the PCI bus information structure. As those of ordinary skill will recognize, reads to and writes from the base address register sometimes involve masking of selected bits as specified by the PCI bus standard. After state 1250 has been completed, the process returns to state 1230.
[0119] If the base address register had the lower order bit set at decision state 1234, indicating that the base address register was for I/O, not memory, the process proceeds to the state 1252 to start I/O address processing.
[0120] At state 1254 in FIG. 12B, the number stored in the base address register is read and the low order bit is masked. Next, at state 1256, from that information the amount of I/O required by the base address register is determined according to the PCI specification, as is apparent to those of ordinary skill in the art.
[0121] Next, at state 1260, the I/O assignment for the base address register is determined by using the last I/O address 1022 (see FIG. 10) stored in the PCI bus information structure and the amount of I/O required by the base address register. Next, at state 1264, a comparison is made to ensure that the I/O assignment given to the base address register does not fall outside the range of I/O allocated to devices on this bus. If it does, the process cannot be completed and the process flow ends at a state 1265.
[0122] If sufficient resources are available, at state 1268 according to the PCI specification, the I/O assignment for the base address register is written to the base address register. First, at state 1268, the memory assignment is written to the base address register. Then, at state 1270, the base address register is read. Next, at state 1272, the information read from the base address register is used to set the last I/O 1022 in the PCI bus information structure (see FIG. 10).
[0123] After the base address register has been programmed, the process returns to state 1230 to read the next base address register. At state 1232, if no further base address registers are present, the configuration manager 500 next executes states 1274 through 1284 to complete the programming of the adapter or IOP.
[0124] First, at state 1274, the device interrupt line is programmed with the proper ISA IRQ corresponding to the bus number. This information is stored as part of the PCI bus information structure. Next, at state 1276, a device latency timer is programmed with a predefined value and at state 1278, a device command register is also programmed with a predefined value.
[0125] Then, at state 1282, the device PCI configuration information is read from the device and then written into the device information structure. Finally, at state 1284, the created device information structure is inserted into the device information list associated with the bus which completes the process.
[0126] Turning now to FIG. 13, the aspects of the configuration space relating to its use in connection with the hot swap of an IOP or an adapter controlled by an IOP will be described. FIG. 13 represents the states which are accomplished by the configuration manager 500 (FIG. 6) operating within the computer system. The following description explains in further detail the process that occurs in state 814 of FIG. 9.
[0127] Starting at a state 1320, a new IOP or adapter which is controlled by an IOP has been added to the computer system 100. The power to the computer has been turned on. The configuration manager 500 will now attempt to reconfigure the new device according to the same configuration as the old device. Further, if an IOP having multiple adapters has been added, the following process flow will have to be followed for each adapter on the IOP. Now, at state 1320, the replacement card in the slot is queried to return the vendor identification and the device identification of the card installed in the slot using standard PCI configuration access known to those of ordinary skill in the art.
[0128] The location of this card on the bus is located in the bus device information structure 1004 (see FIG. 10). This is accomplished by locating the array element corresponding to the bus and then traversing the device information list linked to that array element until the PCI location (typically identified by bus number, device number and function number) corresponding to the current location of interest is located. Then, at state 1324 the vendor identification and device identification which was read from the replacement card is compared to the vendor ID and device ID in the device information structure corresponding to the slot of interest. If those values are not the same, an improper swap has been attempted in that the replacement card is not identical to the card previously located in the slot. The system then proceeds to state 1326 wherein power to that slot is turned off. The process then proceeds to state 1328 wherein an error message is generated and the process terminates.
[0129] However, if the vendor identification and the device identification of the card currently located in the slot of interest and the vendor ID and device ID in the device information structure corresponding to that slot are identical, the process proceeds to state 1330. At state 1330, the PCI configuration space information stored in the device information structure is written to the replacement device. Then, at state 1332, I/O to the slot is restarted. At that point, as represented by state 1334, the hot swap is completed.
[0130] The invention may be embodied in other specific forms and arrangements without departing from its spirit or essential characteristics. For example, the information required to initialize a device being hot added can be maintained in a template. The template may be based upon the configuration information of an adapter of the same type located on a reference system. After following the traditional initialization process of configuring the reference system which includes some or all the devices on some or all the buses, the configuration information for each bus and each device in each bus slot is stored in memory. That information is used to build a template which is then used to supply the configuration information when a device is hot added. However, such a system requires that devices which are hot added can only be the identical type and in the same location as in the reference system. Additionally, the memory structure can be in forms other than an array with device information lists, such as a table.
[0131] While the above detailed description has shown, described, and pointed out the fundamental novel features of the invention as applied to various embodiments, it will be understood that various omissions and substitutions and changes in the form and details of the system illustrated can be made by those skilled in the art, without departing from the intent of the invention. The scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims
What is claimed is:
1. A method of hot adding an adapter to a computer system, comprising:
providing a central processing unit executing an operating system module;
providing a configuration data space for a plurality of devices;
adding an input/output platform to the computer system, wherein the input/output platform is connected to at least one adapter, and wherein the input/output platform comprises a device driver module that controls communications between the adapter and the operating system module;
programming a plurality of configuration registers on the added input/output platform; and
updating the configuration data space to include configuration information of the added input/output platform.
2. The method of claim 1, wherein the operating system module is associated with a selected type of adapter.
3. The method of claim 1, wherein programming the plurality of configuration registers on the added input/output platform includes the act of reading of configuration information which is stored in a memory on the added input/output platform.
4. The method of claim 3, wherein the configuration information includes a vendor identification and the amount and type of memory required by the added input/output platform.
5. The method of claim 1, further comprising requesting a plug hardware to activate power to the added input/output platform.
6. The method of claim 1, wherein adding the input/output platform includes the act of adding an input/output platform having at least one embedded adapter.
7. The method of claim 1, further comprising providing a configuration manager, executed on the computer system, to program the added input/output platform.
8. The method of claim 7, further comprising receiving a request from a user to add an input/output platform and communicating the request to the configuration manager.
9. The method of claim 1, further comprising using a network of microcontrollers to enable the power to the added input/output platform.
10. The method of claim 1, wherein the plurality of configuration registers define a memory range.
11. The method of claim 1, wherein the plurality of configuration registers define a range of I/O addresses.
12. A method of swapping an adapter to a computer system, comprising:
providing a central processing unit executing an operating system module;
providing an input/output platform that comprises a processor and a device driver module, wherein the input/output platform is connected to at least one adapter, wherein the device driver module controls communications between the adapter and the operating system module;
storing configuration information of the adapter;
removing the adapter from the computer system;
adding an adapter to the computer system;
reading the configuration information of the removed adapter from the computer system; and
programming a plurality of configuration registers of the added adapter with configuration information of the removed adapter.
13. The method of claim 12, further comprising starting communications between the added input/output platform and the operating system module.
14. The method of claim 12, further comprising requesting a plug hardware to activate power to the added input/output platform.
15. The method of claim 12, wherein the operating system module is associated with a selected type of adapter.
16. The method of claim 12, wherein the adapter is a mass storage controller.
17. The method of claim 12, wherein the adapter is a network card.
18. The method of claim 12, further comprising providing a configuration manager to program the added input/output platform.
19. The method of claim 18, further comprising receiving a request from a user to perform a swap of an input/output platform and forwarding the request to the configuration manager.
20. The method of claim 12, further comprising using a network of microcontrollers to enable the power to the added input/output platform.
21. A method of hot swapping an input/output platform having at least one embedded adapter from an operational computer, comprising:
providing a central processing unit executing an operating system module;
providing an input/output platform that comprises a processor, a device driver module, and at least one embedded adapter, wherein the device driver module manages input output communications between the operating system module and the embedded adapter;
saving configuration information of the input/output platform into the computer;
disabling power to the input/output platform;
removing the input/output platform from the computer system;
swapping a new input/output platform into the computer in the place of the removed input/output platform;
enabling power to the added input/output platform; and
initiating communications between the computer system and the added input/output platform.
22. The method of claim 21, additionally comprising programming a configuration space of the embedded adapter.
23. The method of claim 21, wherein the operating system module is associated with a selected type of adapter.
Patent Citations (300)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4057847 | 1977-11-01 | Lowell et al. | Applicant |
| US4100597 | 1978-07-01 | Fleming et al. | Applicant |
| US4449182 | 1984-05-01 | Rubinson et al. | Applicant |
| US4672535 | 1987-06-01 | Katzman et al. | Applicant |
| US4692918 | 1987-09-01 | Elliott et al. | Applicant |
| US4695946 | 1987-09-01 | Andreasen et al. | Applicant |
| US4707803 | 1987-11-01 | Anthony, Jr. et al. | Applicant |
| US4769764 | 1988-09-01 | Levanon | Applicant |
| US4774502 | 1988-09-01 | Kimura | Applicant |
| US4821180 | 1989-04-01 | Gerety et al. | Applicant |
| US4835737 | 1989-05-01 | Herrig et al. | Applicant |
| US4894792 | 1990-01-01 | Mitchell et al. | Applicant |
| US4949245 | 1990-08-01 | Martin et al. | Applicant |
| US4999787 | 1991-03-01 | McNally et al. | Applicant |
| US5006961 | 1991-04-01 | Monico | Applicant |
| US5007431 | 1991-04-01 | Donehoo, III | Applicant |
| US5033048 | 1991-07-01 | Pierce et al. | Applicant |
| US5051720 | 1991-09-01 | Kittirutsunetorn | Applicant |
| US5073932 | 1991-12-01 | Yossifor et al. | Applicant |
| US5103391 | 1992-04-01 | Barrett | Applicant |
| US5118970 | 1992-06-01 | Olson et al. | Applicant |
| US5121500 | 1992-06-01 | Arlington et al. | Applicant |
| US5123017 | 1992-06-01 | Simpkins et al. | Applicant |
| US5136708 | 1992-08-01 | Lapourtre et al. | Applicant |
| US5136715 | 1992-08-01 | Hirose et al. | Applicant |
| US5138619 | 1992-08-01 | Fasang et al. | Applicant |
| US5157663 | 1992-10-01 | Major et al. | Applicant |
| US5210855 | 1993-05-01 | Bartol | Applicant |
| US5222897 | 1993-06-01 | Collins et al. | Applicant |
| US5245615 | 1993-09-01 | Treu | Applicant |
| US5247683 | 1993-09-01 | Holmes et al. | Applicant |
| US5253348 | 1993-10-01 | Scalise | Applicant |
| US5261094 | 1993-11-01 | Everson et al. | Applicant |
| US5265098 | 1993-11-01 | Mattson et al. | Applicant |
| US5266838 | 1993-11-01 | Gerner | Applicant |
| US5269011 | 1993-12-01 | Yanai et al. | Applicant |
| US5272382 | 1993-12-01 | Heald et al. | Applicant |
| US5272584 | 1993-12-01 | Austruy et al. | Applicant |
| US5276814 | 1994-01-01 | Bourke et al. | Applicant |
| US5276863 | 1994-01-01 | Heider | Applicant |
| US5277615 | 1994-01-01 | Hastings et al. | Applicant |
| US5280621 | 1994-01-01 | Barnes et al. | Applicant |
| US5283905 | 1994-02-01 | Saadeh et al. | Applicant |
| US5307354 | 1994-04-01 | Cramer et al. | Applicant |
| US5311397 | 1994-05-01 | Harshberger et al. | Applicant |
| US5311451 | 1994-05-01 | Barrett | Applicant |
| US5317693 | 1994-05-01 | Cuenod et al. | Applicant |
| US5329625 | 1994-07-01 | Kannan et al. | Applicant |
| US5337413 | 1994-08-01 | Lui et al. | Applicant |
| US5351276 | 1994-09-01 | Doll, Jr. et al. | Applicant |
| US5367670 | 1994-11-01 | Ward et al. | Applicant |
| US5379184 | 1995-01-01 | Barraza et al. | Applicant |
| US5379409 | 1995-01-01 | Ishikawa | Applicant |
| US5386567 | 1995-01-01 | Lien et al. | Applicant |
| US5388267 | 1995-02-01 | Chan et al. | Applicant |
| US5402431 | 1995-03-01 | Saadeh et al. | Applicant |
| US5404494 | 1995-04-01 | Garney | Applicant |
| US5423025 | 1995-06-01 | Goldman et al. | Applicant |
| US5430717 | 1995-07-01 | Fowler et al. | Applicant |
| US5430845 | 1995-07-01 | Rimmer et al. | Applicant |
| US5432715 | 1995-07-01 | Shigematsu et al. | Applicant |
| US5432946 | 1995-07-01 | Allard et al. | Applicant |
| US5438678 | 1995-08-01 | Smith | Applicant |
| US5440748 | 1995-08-01 | Sekine et al. | Applicant |
| US5448723 | 1995-09-01 | Rowett | Applicant |
| US5455933 | 1995-10-01 | Schieve et al. | Applicant |
| US5460441 | 1995-10-01 | Hastings et al. | Applicant |
| US5463766 | 1995-10-01 | Schieve et al. | Applicant |
| US5471617 | 1995-11-01 | Farrand et al. | Applicant |
| US5471634 | 1995-11-01 | Giorgio et al. | Applicant |
| US5473499 | 1995-12-01 | Weir | Applicant |
| US5483419 | 1996-01-01 | Kaczeus, Sr. et al. | Applicant |
| US5485550 | 1996-01-01 | Dalton | Applicant |
| US5485607 | 1996-01-01 | Lomet et al. | Applicant |
| US5487148 | 1996-01-01 | Komori et al. | Applicant |
| US5491791 | 1996-02-01 | Glowny et al. | Applicant |
| US5493574 | 1996-02-01 | McKinley | Applicant |
| US5493666 | 1996-02-01 | Fitch | Applicant |
| US5513314 | 1996-04-01 | Kandasamy et al. | Applicant |
| US5513339 | 1996-04-01 | Agrawal et al. | Applicant |
| US5515515 | 1996-05-01 | Kennedy et al. | Applicant |
| US5517646 | 1996-05-01 | Piccirillo et al. | Applicant |
| US5519851 | 1996-05-01 | Bender et al. | Applicant |
| US5526289 | 1996-06-01 | Dinh et al. | Applicant |
| US5528409 | 1996-06-01 | Cucci et al. | Applicant |
| US5530810 | 1996-06-01 | Bowman | Examiner |
| US5533193 | 1996-07-01 | Roscoe | Applicant |
| US5533198 | 1996-07-01 | Thorson | Applicant |
| US5535326 | 1996-07-01 | Baskey et al. | Applicant |
| US5539883 | 1996-07-01 | Allon et al. | Applicant |
| US5542055 | 1996-07-01 | Amini et al. | Applicant |
| US5546272 | 1996-08-01 | Moss et al. | Applicant |
| US5548712 | 1996-08-01 | Larson et al. | Applicant |
| US5555510 | 1996-09-01 | Verseput et al. | Applicant |
| US5559764 | 1996-09-01 | Chen et al. | Applicant |
| US5559958 | 1996-09-01 | Farrand et al. | Applicant |
| US5559965 | 1996-09-01 | Oztaskin et al. | Applicant |
| US5560022 | 1996-09-01 | Dunstan et al. | Applicant |
| US5564024 | 1996-10-01 | Pemberton | Applicant |
| US5566299 | 1996-10-01 | Billings et al. | Applicant |
| US5566339 | 1996-10-01 | Perholtz et al. | Applicant |
| US5568610 | 1996-10-01 | Brown | Applicant |
| US5568619 | 1996-10-01 | Blackledge et al. | Applicant |
| US5572403 | 1996-11-01 | Mills | Applicant |
| US5577205 | 1996-11-01 | Hwang et al. | Applicant |
| US5579487 | 1996-11-01 | Meyerson et al. | Applicant |
| US5579491 | 1996-11-01 | Jeffries et al. | Applicant |
| US5579528 | 1996-11-01 | Register | Applicant |
| US5581712 | 1996-12-01 | Herrman | Applicant |
| US5581714 | 1996-12-01 | Amini et al. | Applicant |
| US5584030 | 1996-12-01 | Husak et al. | Applicant |
| US5586250 | 1996-12-01 | Carbonneau et al. | Applicant |
| US5588121 | 1996-12-01 | Reddin et al. | Applicant |
| US5588144 | 1996-12-01 | Inoue et al. | Applicant |
| US5592610 | 1997-01-01 | Chittor | Applicant |
| US5592611 | 1997-01-01 | Midgely et al. | Applicant |
| US5596711 | 1997-01-01 | Burckhartt et al. | Applicant |
| US5598407 | 1997-01-01 | Bud et al. | Applicant |
| US5602758 | 1997-02-01 | Lincoln et al. | Applicant |
| US5604873 | 1997-02-01 | Fite et al. | Applicant |
| US5606672 | 1997-02-01 | Wade | Applicant |
| US5608876 | 1997-03-01 | Cohen et al. | Applicant |
| US5615207 | 1997-03-01 | Gephardt et al. | Applicant |
| US5621159 | 1997-04-01 | Brown et al. | Applicant |
| US5621892 | 1997-04-01 | Cook | Applicant |
| US5622221 | 1997-04-01 | Genga, Jr. et al. | Applicant |
| US5625238 | 1997-04-01 | Ady et al. | Applicant |
| US5627962 | 1997-05-01 | Goodrum et al. | Applicant |
| US5628028 | 1997-05-01 | Michelson | Applicant |
| US5630076 | 1997-05-01 | Saulpaugh et al. | Applicant |
| US5631847 | 1997-05-01 | Kikinis | Applicant |
| US5632021 | 1997-05-01 | Jennings et al. | Applicant |
| US5636341 | 1997-06-01 | Matsushita et al. | Applicant |
| US5638289 | 1997-06-01 | Yamada et al. | Applicant |
| US5644470 | 1997-07-01 | Benedict et al. | Applicant |
| US5644731 | 1997-07-01 | Liencres et al. | Applicant |
| US5651006 | 1997-07-01 | Fujino et al. | Applicant |
| US5652832 | 1997-07-01 | Kane et al. | Applicant |
| US5652839 | 1997-07-01 | Giorgio et al. | Applicant |
| US5652892 | 1997-07-01 | Ugajin | Applicant |
| US5652908 | 1997-07-01 | Douglas et al. | Applicant |
| US5655081 | 1997-08-01 | Bonnell et al. | Applicant |
| US5655083 | 1997-08-01 | Bagley | Applicant |
| US5655148 | 1997-08-01 | Richman et al. | Applicant |
| US5659682 | 1997-08-01 | Devarakonda et al. | Applicant |
| US5664118 | 1997-09-01 | Nishigaki et al. | Applicant |
| US5664119 | 1997-09-01 | Jeffries et al. | Applicant |
| US5666538 | 1997-09-01 | DeNicola | Applicant |
| US5668943 | 1997-09-01 | Attanasio et al. | Applicant |
| US5668992 | 1997-09-01 | Hammer et al. | Applicant |
| US5669009 | 1997-09-01 | Buktenica et al. | Applicant |
| US5671371 | 1997-09-01 | Kondo et al. | Applicant |
| US5675723 | 1997-10-01 | Ekrot et al. | Applicant |
| US5680288 | 1997-10-01 | Carey et al. | Applicant |
| US5684761 | 1997-11-01 | Hobbs et al. | Applicant |
| US5689637 | 1997-11-01 | Johnson et al. | Applicant |
| US5696895 | 1997-12-01 | Hemphill et al. | Applicant |
| US5696899 | 1997-12-01 | Kalwitz | Applicant |
| US5696949 | 1997-12-01 | Young | Applicant |
| US5696970 | 1997-12-01 | Sandage et al. | Applicant |
| US5701417 | 1997-12-01 | Lewis et al. | Applicant |
| US5704031 | 1997-12-01 | Mikami et al. | Applicant |
| US5708775 | 1998-01-01 | Nakamura | Applicant |
| US5708776 | 1998-01-01 | Kikinis | Applicant |
| US5712754 | 1998-01-01 | Sides et al. | Applicant |
| US5715456 | 1998-02-01 | Bennett et al. | Applicant |
| US5717570 | 1998-02-01 | Kikinis | Applicant |
| US5721935 | 1998-02-01 | DeSchepper et al. | Applicant |
| US5724529 | 1998-03-01 | Smith et al. | Applicant |
| US5726506 | 1998-03-01 | Wood | Applicant |
| US5727207 | 1998-03-01 | Gates et al. | Applicant |
| US5732266 | 1998-03-01 | Moore et al. | Applicant |
| US5737708 | 1998-04-01 | Grob et al. | Applicant |
| US5740378 | 1998-04-01 | Rehl et al. | Applicant |
| US5742514 | 1998-04-01 | Bonola | Applicant |
| US5742833 | 1998-04-01 | Dea et al. | Applicant |
| US5747889 | 1998-05-01 | Raynham et al. | Applicant |
| US5748426 | 1998-05-01 | Bedingfield et al. | Applicant |
| US5752164 | 1998-05-01 | Jones | Applicant |
| US5754396 | 1998-05-01 | Felcman et al. | Applicant |
| US5754449 | 1998-05-01 | Hoshal et al. | Applicant |
| US5754797 | 1998-05-01 | Takahashi | Applicant |
| US5758165 | 1998-05-01 | Shuff | Applicant |
| US5758352 | 1998-05-01 | Reynolds et al. | Applicant |
| US5761033 | 1998-06-01 | Wilhelm | Applicant |
| US5761045 | 1998-06-01 | Olson et al. | Applicant |
| US5761085 | 1998-06-01 | Giorgio | Applicant |
| US5761462 | 1998-06-01 | Neal et al. | Applicant |
| US5761707 | 1998-06-01 | Aiken et al. | Applicant |
| US5764924 | 1998-06-01 | Hong | Applicant |
| US5764968 | 1998-06-01 | Ninomiya | Applicant |
| US5765008 | 1998-06-01 | Desai et al. | Applicant |
| US5765198 | 1998-06-01 | McCrocklin et al. | Applicant |
| US5767844 | 1998-06-01 | Stoye | Applicant |
| US5768541 | 1998-06-01 | Pan-Ratzlaff | Applicant |
| US5768542 | 1998-06-01 | Enstrom et al. | Applicant |
| US5771343 | 1998-06-01 | Hafner et al. | Applicant |
| US5774645 | 1998-06-01 | Beaujard et al. | Applicant |
| US5774741 | 1998-06-01 | Choi | Applicant |
| US5777897 | 1998-07-01 | Giorgio | Applicant |
| US5778197 | 1998-07-01 | Dunham | Applicant |
| US5781703 | 1998-07-01 | Desai et al. | Applicant |
| US5781716 | 1998-07-01 | Hemphill et al. | Applicant |
| US5781744 | 1998-07-01 | Johnson et al. | Applicant |
| US5781767 | 1998-07-01 | Inoue et al. | Applicant |
| US5781798 | 1998-07-01 | Beatty et al. | Applicant |
| US5784555 | 1998-07-01 | Stone | Applicant |
| US5784576 | 1998-07-01 | Guthrie et al. | Applicant |
| US5787019 | 1998-07-01 | Knight et al. | Applicant |
| US5787459 | 1998-07-01 | Stallmo et al. | Applicant |
| US5787491 | 1998-07-01 | Merkin et al. | Applicant |
| US5790775 | 1998-08-01 | Marks et al. | Applicant |
| US5790831 | 1998-08-01 | Lin et al. | Applicant |
| US5793948 | 1998-08-01 | Asahi et al. | Applicant |
| US5793987 | 1998-08-01 | Quackenbush et al. | Applicant |
| US5794035 | 1998-08-01 | Golub et al. | Applicant |
| US5796185 | 1998-08-01 | Takata et al. | Applicant |
| US5796580 | 1998-08-01 | Komatsu et al. | Applicant |
| US5796981 | 1998-08-01 | Abudayyeh et al. | Applicant |
| US5797023 | 1998-08-01 | Berman et al. | Applicant |
| US5798828 | 1998-08-01 | Thomas et al. | Applicant |
| US5799036 | 1998-08-01 | Staples | Applicant |
| US5799196 | 1998-08-01 | Flannery | Applicant |
| US5801921 | 1998-09-01 | Miller | Applicant |
| US5802269 | 1998-09-01 | Poisner et al. | Applicant |
| US5802298 | 1998-09-01 | Imai et al. | Applicant |
| US5802305 | 1998-09-01 | McKaughan et al. | Applicant |
| US5802324 | 1998-09-01 | Wunderlich et al. | Applicant |
| US5802393 | 1998-09-01 | Begun et al. | Applicant |
| US5802552 | 1998-09-01 | Fandrich et al. | Applicant |
| US5802592 | 1998-09-01 | Chess et al. | Applicant |
| US5803357 | 1998-09-01 | Lakin | Applicant |
| US5805804 | 1998-09-01 | Laursen et al. | Applicant |
| US5805834 | 1998-09-01 | McKinley et al. | Applicant |
| US5809224 | 1998-09-01 | Schultz et al. | Applicant |
| US5809256 | 1998-09-01 | Najemy | Applicant |
| US5809287 | 1998-09-01 | Stupek, Jr. et al. | Applicant |
| US5809311 | 1998-09-01 | Jones | Applicant |
| US5809555 | 1998-09-01 | Hobson | Applicant |
| US5812748 | 1998-09-01 | Ohran et al. | Applicant |
| US5812750 | 1998-09-01 | Dev et al. | Applicant |
| US5812757 | 1998-09-01 | Okamoto et al. | Applicant |
| US5812858 | 1998-09-01 | Nookala et al. | Applicant |
| US5815117 | 1998-09-01 | Kolanek | Applicant |
| US5815647 | 1998-09-01 | Buckland et al. | Applicant |
| US5815652 | 1998-09-01 | Ote et al. | Applicant |
| US5821596 | 1998-10-01 | Miu et al. | Applicant |
| US5822547 | 1998-10-01 | Boesch et al. | Applicant |
| US5826043 | 1998-10-01 | Smith et al. | Applicant |
| US5835719 | 1998-11-01 | Gibson et al. | Applicant |
| US5835738 | 1998-11-01 | Blackledge, Jr. et al. | Applicant |
| US5838932 | 1998-11-01 | Alzien | Applicant |
| US5841964 | 1998-11-01 | Yamaguchi | Applicant |
| US5841991 | 1998-11-01 | Russell | Applicant |
| US5845061 | 1998-12-01 | Miyamoto et al. | Applicant |
| US5845095 | 1998-12-01 | Reed et al. | Applicant |
| US5850546 | 1998-12-01 | Kim | Applicant |
| US5852720 | 1998-12-01 | Gready et al. | Applicant |
| US5852724 | 1998-12-01 | Glenn, II et al. | Applicant |
| US5857074 | 1999-01-01 | Johnson | Applicant |
| US5857102 | 1999-01-01 | McChesney et al. | Applicant |
| US5864653 | 1999-01-01 | Tavallaei et al. | Applicant |
| US5864713 | 1999-01-01 | Terry | Applicant |
| US5867730 | 1999-02-01 | Leyda | Applicant |
| US5875307 | 1999-02-01 | Ma et al. | Applicant |
| US5875308 | 1999-02-01 | Egan et al. | Applicant |
| US5875310 | 1999-02-01 | Buckland et al. | Applicant |
| US5878237 | 1999-03-01 | Olarig | Applicant |
| US5878238 | 1999-03-01 | Gan et al. | Applicant |
| US5881311 | 1999-03-01 | Woods | Applicant |
| US5884027 | 1999-03-01 | Garbus et al. | Applicant |
| US5884049 | 1999-03-01 | Atkinson | Applicant |
| US5886424 | 1999-03-01 | Kim | Applicant |
| US5889965 | 1999-03-01 | Wallach et al. | Applicant |
| US5892898 | 1999-04-01 | Fujii et al. | Applicant |
| US5892928 | 1999-04-01 | Wallach et al. | Applicant |
| US5898846 | 1999-04-01 | Kelly | Applicant |
| US5898888 | 1999-04-01 | Guthrie et al. | Applicant |
| US5905867 | 1999-05-01 | Giorgio | Applicant |
| US5907672 | 1999-05-01 | Matze et al. | Applicant |
| US5909568 | 1999-06-01 | Nason | Applicant |
| US5911779 | 1999-06-01 | Stallmo et al. | Applicant |
| US5913034 | 1999-06-01 | Malcolm | Applicant |
| US5922060 | 1999-07-01 | Goodrum | Applicant |
| US5930358 | 1999-07-01 | Rao | Applicant |
| US5935262 | 1999-08-01 | Barrett et al. | Applicant |
| US5936960 | 1999-08-01 | Stewart | Applicant |
| US5938751 | 1999-08-01 | Tavallaei et al. | Applicant |
| US5941996 | 1999-08-01 | Smith et al. | Applicant |
| US5964855 | 1999-10-01 | Bass et al. | Examiner |
| US5983349 | 1999-11-01 | Kodama et al. | Applicant |
| US5987554 | 1999-11-01 | Liu et al. | Applicant |
| US5987627 | 1999-11-01 | Rawlings, III | Applicant |
| US6012130 | 2000-01-01 | Beyda et al. | Applicant |
| US6038624 | 2000-03-01 | Chan et al. | Applicant |
| EP866403A1 | 1998-09-01 | Applicant | |
| JP4333118 | 1992-11-01 | Applicant | |
| JP5233110 | 1993-09-01 | Applicant | |
| JP7093064 | 1995-04-01 | Applicant | |
| JP7261874 | 1995-10-01 | Applicant |
Non-Patent Literature (37)
- Compaq Computer Corporation, Phenix Technologies, LTD, and Intel Corporation, specification, 55 pages, May 5, 1994, “Plug & Play BIOS Specification.”Applicant
- Digital Equipment Corporation, datasheet, 140 pages, 1993, “DECchip 21050 PCI-TO-PCI Bridge.”Applicant
- Herr et al., Linear Technology Magazine, Jun. 1997, “Hot Swapping the PCI Bus.”Applicant
- Joint work by Intel Corporation, Compaq, Adaptec, Hewlett Packard, and Novell, presentation, 22 pages, Jun. 1996, “Intelligent I/O Architecture.”Applicant
- Lockareff, M., HTINews, http://www.hometoys.com/htinews/dec96/articles/lonworks.htm, Dec. 1996, “Loneworks—An Introduction.”Applicant
- Microsoft Corporation, file:///A|/Rem devs.htm, 4 pages, Copyright 1997, updated Aug. 13, 1997, “Supporting Removable Devices Under Windows and Windows NT.”Applicant
- NetFRAME Systems Incorporated, datasheet, Mar. 1996, “NetFRAME Cluster Server 8000.”Applicant
- NetFRAME Systems Incorporated, News Release, 3 pages, referring to May 9, 1994, “NetFRAME's New High-Availability ClusterServer Systems Avoid Scheduled as well as Unscheduled Downtime.”Applicant
- NetFRAME Systems Incorporated, datasheet, Feb. 1996, “NF450FT Network Mainframe.”Applicant
- NTRR, Ltd, http://www.nrtt.demon.co.uk/cantech.html, 5 pages, May 28, 1997, “CAN: Technical Overview.”Applicant
- PCI Special Interest Group, specification, 35 pages, Draft For Review Only, Jun. 15, 1997, “PCI Bus Hot Plug Specification.”Applicant
- Schofield, M.J., http://www.omegas.co.uk/CAN/canworks.htm, Copyright 1996, 1997, “Controller Area Network—How CAN Works.”Applicant
- Standards Overview, http://www.pc-card.com/stand overview.html#1, 9 pages, Jun. 1990, “Detailed Overview of the PC Card Standard.”Applicant
- ftp.cdrom.com/pub/os2/diskutil/, PHDX software, phdx.zip download, Mar. 1995, “Parallel Hard Disk Xfer.”Applicant
- Cmasters, Usenet post to microsoft.public.windowsnt.setup, Aug. 1997, “Re: FDISK switches.”Applicant
- Hildebrand, N., Usenet post to comp.msdos.programmer, May 1995, “Re: Structure of disk partition into.”Applicant
- Lewis, L., Usenet post to alt.msdos.batch, Apr. 1997, “Re: Need help with automating FDISK and FORMAT.”Applicant
- Netframe, http://www.netframe-support.com/technology/datasheets/data.htm, before Mar. 1997, “Netframe ClusterSystem 9008 Data Sheet.”Applicant
- Simos, M., Usenet post to comp.os.msdos.misc, Apr. 1997, “Re: Auto FDISK and FORMAT.”Applicant
- Wood, M. H., Usenet post to comp.os.netware.misc, Aug. 1996, “Re: Workstation duplication method for WIN95.”Applicant
- Lyons, Computer Reseller News, Issue 721, pp. 61-62, Feb. 3, 1997, “ACC Releases Low-Cost Solution for ISPs.”Applicant
- M2 Communications, M2 Presswire, 2 pages, Dec. 19, 1996, “Novell IntranetWare Supports Hot Pluggable PCI from NetFRAME.”Applicant
- Rigney, PC Magazine, 14(17): 375-379, Oct. 10, 1995, “The One for the Road (Mobile-aware capabilities in Windows 95).”Applicant
- Shanley, and Anderson, PCI System Architecture, Third Edition, p. 382, Copyright 1995.Applicant
- Gorlick, M., Conf. Proceedings: ACM/ONR Workshop on Parallel and Distributed Debugging, pp. 175-181, 1991, “The Flight Recorder: An Architectural Aid for System Monitoring.”Applicant
- IBM Technical Disclosure Bulletin, 92A+62947, pp. 391-394, Oct. 1992, Method for Card Hot Plug Detection and Control.Applicant
- Davis, T., Usenet post to alt.msdos.programmer, Apr. 1997, “Re: How do I create an FDISK batch file?”Applicant
- Davis, T., Usenet post to alt.msdos.batch, Apr. 1997, “Re: Need help with automating FDISK and FORMAT . . . ”Applicant
- NetFrame Systems Incorporated, Doc. No. 78-1000226-01, pp. 1-2, 5-8, 359-404, and 471-512, Apr. 1996, “NetFrame Clustered Multiprocessing Software: NW0496 DC-ROM for Novell® NetWare® 4.1 SMP, 4.1 and 3.12.”Applicant
- Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 15, pp. 297-302, Copyright 1995, “Intro To Configuration Address Space.”Applicant
- Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 16, pp. 303-328, Copyright 1995, “Configuration Transactions.”Applicant
- Sun Mirosystems Computer Company, Part No. 802-5355-10, Rev. A, May 1996, “Solstice SyMON User's Guid.”Applicant
- Sun Microsystems, Part No. 802-6569-11, Release 1.0.1, Nov. 1996, “Remote Systems Diagnostics Installation & User Guide.”Applicant
- Shanley and Anderson, PCI System Architecture, Third Edition, Chapters 15 & 16, pp. 297-328, CR 1995.Applicant
- PCI Hot-Plug Specification, Preliminary Revision for Review Only, Revision 0.9, pp. i-vi, and 1-25, Mar. 5, 1997.Applicant
- SES SCSI-3 Enclosure Services, X3T10/Project 1212-D/Rev 8a, pp. i, iii-x, 1-76, and I-1 (index), Jan. 16, 1997.Applicant
- Compaq Computer Corporation, Technology Brief, pp. 1-13, Dec. 1996, “Where Do I Plug the Cable? Solving the Logical-Physical Slot Numbering Problem.”Applicant