System for copying device driver stub into allocated portion of system memory corresponding to receiving resource to enable device driver execution from resource memory

• US 5,404,494 A
• Filed: 01/22/1993
• Issued: 04/04/1995
• Est. Priority Date: 12/27/1991
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Garney, John I.
• Primary Examiner(s): Lee, Thomas C.
• Assistant Examiner(s): MEKY, MOUSTAFA M
• Application Number:
  US08/007,580
• Time in Patent Office: 802 Days
• Field of Search: 395/275, 395/200, 395/375, 395/650, 395/700, 395/500, 364/231.5, 364/231.6, 364/247.3
• US Class Current: 710/10
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: G06F 9/4415 Self describing peripheral devices

Abstract

Device drivers for removable system resources are configured dynamically in a computer system which has a processor, a system memory and an interface for receiving removable system resources (generally denoted feature cards). A feature card includes a card memory area that stores a device driver for controlling the feature card. The feature card device driver is separated into two parts: 1) a full device driver portion, and 2) a stub device driver portion. The full device driver provides all of the device driver functionality necessary to control each and every function of the feature card. The device driver stub is a small compact portion of processing logic for linking the full device driver with operating system software located in the computer system. There is an upper bound for the size of a device driver stub of a given feature card. Any system will have a known number of card slots. Therefore, by allocating enough space per slot in computer system memory to contain the largest permitted card device driver stub, one can ensure that there will always be enough computer system memory to contain every device driver stub required by the system at a given time.

Claims

1. In a computer system having a processor, a system memory, and an interface for receiving a removable system resource, said interface including a plurality of sockets for receiving said removable system resource, a process for dynamically configuring device drivers of removable computer system resources, said process comprising the steps of:

allocating a portion of said system memory, said allocating step further including the step of allocating a plurality of sub-portions of said portion, said sub-portions equal in number to the number of sockets, such that each socket has a corresponding sub-portion;

providing a resource memory in a removable system resource;

loading a device driver into said resource memory, said device driver for controlling said removable system resource;

loading a device driver stub into said resource memory, said device driver stub for enabling said device driver;

receiving an indication that said removable system resource has been coupled to said interface subsequent to initialization of said processor, said receiving step further including the step of identifying a receiving socket of the plurality of sockets, said receiving socket coupling said removable system resource to said computer system;

copying said device driver stub into a sub-portion of said allocated portion of system memory corresponding to said receiving socket;

executing said device driver stub from said system memory;

enabling access to said device driver, said access being enabled by said device driver stub, said enabling step further including the step of allowing memory mapping to said device driver residing in said resource memory; and

executing said device driver from said resource memory.

2. The process as set forth in claim 1 wherein said resource memory further includes a device driver information block (DDIB) header, said process further including the step of copying said DDIB header into said sub-portion corresponding to said receiving socket.

3. The process as claimed in claim 2 wherein said DDIB header includes link data and a device driver stub unique identification, said process further including the step of linking said device driver stub with a different device driver stub stored in system memory.

4. The process as claimed in claim 3 wherein said step of linking said device driver stub further includes the step of forward linking said device driver stub with a succeeding device driver stub and backward linking said device driver stub with a preceding device driver stub, said succeeding and preceding device driver stubs residing in system memory.

5. The process as set forth in claim 1 further including the steps of:

receiving an indication that a removable system resource has been decoupled from said interface; and

disabling access to said device driver, said access being disabled by said device driver stub.

6. The process as claimed in claim 5 wherein said resource memory further includes a device driver information block (DDIB) header, said DDIB header including link data and a device driver stub unique identification, said process further including the steps of:

copying said DDIB header into said sub-portion corresponding to said receiving socket upon receiving said indication that said removable system resource has been coupled to said interface;

linking said device driver stub with a different device driver stub stored in system memory upon receiving said indication that said removable system resource has been coupled to said interface; and

unlinking said device driver stub from said different device driver stub stored in system memory upon receiving said indication that said removable system resource has been decoupled from said interface.

7. In a computer system having a processor, a system memory, and an interface for receiving a removable system resource, said interface including a plurality of receiving means for receiving said removable system resource, a device for dynamically configuring device drivers of removable computer system resources, said device comprising:

a resource memory in said removable system resource, said resource memory comprising a device driver for controlling said removable system resource, said resource memory further including a device driver stub for enabling said device driver;

means for allocating a portion of said system memory, said means for allocating a portion of system memory further including means for allocating a plurality of sub-portions of said portion, said sub-portions equal in number to the number of receiving means, such that each receiving means has a corresponding sub-portion;

means for receiving an indication that a removable system resource has been coupled to said interface subsequent to initialization of said processor, said means for receiving an indication that a removable system resource has been coupled to said interface further including means for identifying an occupied receiving means of the plurality of receiving means, said occupied receiving means coupling said removable system resource to said computer system;

means for copying said device driver stub into said allocated portion of system memory, said means for copying said device driver stub into said allocated portion of system memory copying said device driver stub into a sub-portion corresponding to said occupied receiving means;

means for executing said device driver stub from said system memory;

means for enabling access to said device driver, said access being enabled by said device driver stub, said means for enabling access to said device driver further including means for allowing memory mapping to said device driver residing in said resource memory; and

means for executing said device driver from said resource memory.

8. The device as set forth in claim 7 wherein said resource memory further includes a device driver information block (DDIB) header, said device further including means for copying said DDIB header into said sub-portion corresponding to said occupied receiving means.

9. The device as claimed in claim 8 wherein said DDIB header includes link data and a device driver stub unique identification, said device further including means for linking said device driver stub with a different device driver stub stored in system memory.

10. The device as claimed in claim 9 wherein said means for linking said device driver stub further includes means for forward linking said device driver stub with a succeeding device driver stub and backward linking said device driver stub with a preceding device driver stub, said succeeding and preceding device driver stubs residing in system memory.

11. The device as set forth in claim 7 further including:

means for receiving an indication that a removable system resource has been decoupled from said interface; and

means for disabling access to said device driver, said access being disabled by said device driver stub.

12. In a computer system having a processor, a system memory, and an interface for receiving a removable system resource, said interface including a plurality of sockets for receiving said removable system resource, a device for dynamically configuring device drivers of removable computer system resources, said device comprising:

a resource memory in said removable system resource, said resource memory comprising a device driver for controlling said removable system resource, said resource memory further including a device driver stub for enabling said device driver;

an allocater for allocating a portion of said system memory, said allocater including means for allocating a plurality of sub-portions of said portion;

a coupling indicator for receiving an indication that a removable system resource has been coupled to said interface subsequent to initialization of said processor, said coupling indicator further including a socket indicator for identifying a receiving socket of the plurality of sockets, said receiving socket coupling said removable system resource to said computer system;

a stub copier for copying said device driver stub into said allocated portion of system memory, said stub copier copying said device driver stub into a sub-portion corresponding to said receiving socket;

a stub executor for executing said device driver stub from said system memory;

a linker for enabling access to said device driver, said access being enabled by said device driver stub, said linker further including a memory mapper for allowing memory mapping to said device driver residing in said resource memory; and

a device driver executor for executing said device driver from said resource memory.

13. The device as set forth in claim 12 wherein said resource memory further includes a device driver information block (DDIB) header, said device further including a DDIB header copier for copying said DDIB header into said sub-portion corresponding to said receiving socket.

14. The device as claimed in claim 13 wherein said DDIB header includes link data and a device driver stub unique identification, said device further including stub linker for linking said device driver stub with a different device driver stub stored in system memory.

15. The device as claimed in claim 14 wherein said stub linker further includes chain linker for forward linking said device driver stub with a succeeding device driver stub and backward linking said device driver stub with a preceding device driver stub, said succeeding and preceding device driver stubs residing in system memory.

16. The device as claimed in claim 13 wherein said resource memory further includes a device driver information block (DDIB) header, said DDIB header including link data and a device driver stub unique identification, said device further including:

DDIB copier for copying said DDIB header into said sub-portion corresponding to said receiving socket upon receiving said indication that said removable system resource has been coupled to said interface;

stub linker for linking said device driver stub with a different device driver stub stored in system memory upon receiving said indication that said removable system resource has been coupled to said interface; and

stub unlinker for unlinking said device driver stub from said different device driver stub stored in system memory upon receiving said indication that said removable system resource has been decoupled from said interface.

17. The device as set forth in claim 12 further including:

a decoupling indicator for receiving an indication that a removable system resource has been decoupled from said interface; and

a disabler for disabling access to said device driver, said access being disabled by said device driver stub.

18. A computer system which dynamically configures device drivers of removable computer system resources, said computer system comprising:

a processor;

a system memory;

an interface for receiving a removable system resource, said interface including a plurality of receiving means for receiving said removable system resource;

a resource memory in said removable system resource, said resource memory comprising a device driver for controlling said removable system resource, said resource memory further including a device driver stub for enabling said device driver;

means for allocating a portion of said system memory, said means for allocating a portion of system memory further including means for allocating a plurality of sub-portions of said portion, said sub-portions equal in number to the number of receiving means, such that each receiving means has a corresponding sub-portion;

means for receiving an indication that a removable system resource has been coupled to said interface subsequent to initialization of said processor, said means for receiving an indication that a removable system resource has been coupled to said interface further including means for identifying an occupied receiving means of the plurality of receiving means, said occupied receiving means coupling said removable system resource to said computer system

means for copying said device driver stub into said allocated portion of system memory, said means for copying said device driver stub into said allocated portion of system memory copying said device driver stub into a sub-portion corresponding to said occupied receiving means;

means for executing said device driver stub from said system memory;

means for enabling access to said device driver, said access being enabled by said device driver stub, said means for enabling access to said device driver further including means for allowing memory mapping to said device driver residing in said resource memory; and

means for executing said device driver from said resource memory.

19. The computer system as set forth in claim 18 wherein said resource memory further includes a device driver information block (DDIB) header, said computer system further including means for copying said DDIB header into said sub-portion corresponding to said receiving socket.

20. The computer system as set forth in claim 18 further including:

a decoupling indicator for receiving an indication that a removable system resource has been decoupled from said interface; and

a disabler for disabling access to said device driver, said access being disabled by said device driver stub.