Interface for interfacing simulation tests written in a high-level programming language to a simulation model

• US 5,732,247 A
• Filed: 03/22/1996
• Issued: 03/24/1998
• Est. Priority Date: 03/22/1996
• Status: Expired due to Fees

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Dearth, Glenn A., Whittemore, Paul M., Medeiros, David A., Ih, Bennet H., Plouffe, George R. Jr.
• Primary Examiner(s): Chin, Gary
• Assistant Examiner(s): Fiul, Dan
• Application Number:
  US08/620,439
• Time in Patent Office: 732 Days
• Field of Search: 395/500, 395/163.09, 395/920, 364/146, 364/488, 364/489, 364/490, 364/491, 364/578, 371/27.2, 371/27.4, 340/515
• US Class Current: 703/13
• CPC Class Codes: G06F 11/261 by simulating additional hardware, e.g. fault simulation
• CPC Class Codes: G06F 30/33 Design verification, e.g. functional simulation or model checking

Abstract

An interface subsystem for use in a system including one or more simulation systems facilitates simulation of one or more simulation models under control of one or more tests. The interface subsystem allows the tests and simulation systems to transfer information therebetween and enables said tests to control the simulation systems in simulating the simulation model during a simulation run. The simulation systems include transactors which provide information to the simulation model at the beginning of a simulation run, pause a simulation run in response to detection of a selected event, and generate simulation result information. The interface subsystem includes, associated with each test, a simulation information generator, a simulation control indicator generator, and a information receiver; associated with each simulation system an information receiver associated with each transactor and a simulator interface module; and an interface core. The a simulation information generator provides simulation information to be transferred to said simulation system for use during a simulation run and the simulation control indicator generator generates a simulation control indicator for controlling said simulation system. Each test'"'"'s information receiver receives simulation result information generated during a simulation run. Each simulation system'"'"'s simulator interface module (a) receives simulation information and providing the received simulation to an information receiver for use by the associated transactor, (b) receives simulating result information from said at least one transactor to be provided to said at least one test, and (c) controls said at least one simulation system to initiate a simulation run in response to receipt of a control indicator. Each transactor'"'"'s information receiver receives simulation information for use by the associated transactor during a simulation run. The interface core transfers (a) simulation information from a test to the simulator interface module of a simulating system for provision to one transactor'"'"'s information receiver for use by a transactor during a simulation run, (b) said simulation control indicator to the simulator interface module of a simulation system for controlling the simulation system in a simulation run, and (c) simulation result information from the transactors to the tests during a simulation run.

Claims

1. For use in a system including at least one simulation system for facilitating simulation of at least one simulation model under control of at least one test, an interface subsystem for allowing said at least one test and said at least one simulation system to transfer information therebetween and for enabling control by said at least one test of said simulation system in simulating said simulation model during a simulation run, said at least one simulation system including at least one transactor for (a) providing information to said simulation model to control the simulation model, (b) pausing a simulation run in response to detection of a selected event, and (c) generating simulation result information, said interface subsystem comprising:

A. each said at least one test including a simulation information generator for providing simulation information to be transferred to said simulation system for use during a simulation run and a simulation control indicator generator for generating a simulation control indicator for controlling said simulation system, each said at least one test further having associated therewith at least one information receiver for receiving simulation result information;

B. each said at least one simulation system including;

i. associated with said at least one transactor, an information receiver for receiving simulation information for use by the associated transactor during a simulation run;

ii. a simulator interface module associated with each said at least one said simulation system for (a) receiving simulation information and providing the received simulation to an information receiver for use by the associated transactor, (b) receiving simulating result information from said at least one transactor to be provided to said at least one test, and (c) controlling said at least one simulation system to initiate a simulation run in response to receipt of a control indicator; and

C. an interface core for transferring (i) said simulation information from said at least one test to the simulator interface module of a selected one of said at least one simulating system for provision to a selected one of said at least one of said transactor'"'"'s information receiver for use by a transactor during a simulation run, (ii) said simulation control indicator for controlling a selected one of said at least one simulation system, and (iii) for transferring said simulation remit information from said at least one transactor to said information receiver of a selected one of said at least one test.

2. An interface subsystem as defined in claim 1, in which the at least one simulation model is in the form of a hardware description language description of an electronic circuit.

3. An interface subsystem as defined in claim 1 in which the at least one test is defined by a computer program product in the form of a high-level computer programming language.

4. An interface subsystem as defined in claim 1 in which said information receiver of said at least one test comprises a mailbox.

5. An interface subsystem as defined in claim 1 in which said information receiver of said at least one transactor comprises a mailbox.

6. An interface subsystem as defined in claim 1 in which said interface core provides at least one bi-directional information transfer link to each of said at least one test and each of said at least one simulator interface module.

7. An interface subsystem as defined in claim 6 in which at least one of said at least one bi-directional information transfer link comprises two uni-directional information transfer links for transferring information in opposite directions.

8. An interface subsystem as defined in claim 6 in which each said uni-directional information transfer link comprises a remote procedure call link.

9. An interface subsystem as defined in claim 1 in which said at least one said test generates said simulation information in the form of at least one simulation information message packet, said simulation information message packet including simulation system identification informationidentifying one of said at least one simulation system to receive the simulation information message packet.

10. An interface subsystem as defined in claim 7 in which each said at least one simulation system has an associated simulation system identifier, said simulation system identification information in each said simulation information message packet identifying the simulation system identifier of the at least one simulation system to receive the simulation information message packet.

11. An interface subsystem as defined in claim 9 in which said simulation information message packet further includes transactor identification information for identifying one of said at least one transactor to receive the simulation information in said simulation information message packet.

12. An interface subsystem as defined in claim 11 in which each at least one transactor has an associated transactor identifier, said transactor identification information in each said simulation information message packet identifying the transactor identifier of the at least one transactor to receive the simulation information in said simulation information message packet.

13. An interface subsystem as defined in claim 11 in which at least one said transactor has a plurality of associated information receivers each identified by an information receiver identifier, said simulation information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

14. An interface subsystem as defined in claim 1 in which said at least one said transactor generates said simulation result information in the form of at least one simulation result information message packet, said simulation result information message packet including test identification information identifying one of said at least one test to receive the simulation result information message packet.

15. An interface subsystem as defined in claim 14 in which each said at least one test has an associated test identifier, said test identification information in each said simulation information message packet identifying the test identifier of the at least one test to receive the simulation result information message packet.

16. An interface subsystem as defined in claim 14 in which at least one said test has a plurality of associated information receivers each identified by an information receiver identifier, said simulation result information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

17. An interface subsystem as defined in claim 1 further comprising a simulation information control module for controlling the simulation information generator of said at least one test.

18. An interface subsystem as defined in claim 17 in which said simulation information control module enables said simulation information generator to provide simulation information for said at least one simulation system when said simulation system is not engaged in a simulation run.

19. An interface subsystem as defined in claim 18 in which said simulation information control module disables said simulation information generator from providing simulation information for said at least one simulation system when said simulation system is engaged in a simulation run.

20. An interface subsystem as defined in claim 1 in which said at least one transactor during a simulation run generates supplemental information requests requesting supplemental simulation information from said at least one test, said interface core transferring said supplemental information request so said at least one test to obtain said supplemental simulation information therefrom.

21. An interface subsystem as defined in claim 1 in which said at least one test includes a mailbox for storing supplemental simulation information, the interface core in response to a supplemental information request from said at least one transactor retrieving said supplemental simulation information from said mailbox for provision to said at least one transactor.

22. An interface subsystem as defined in claim 1 further including at least one auxiliary processing module for performing an auxiliary processing operation, said at least one transactor generating an auxiliary processing request, said simulator interface module in response to an auxiliary processing request enabling said interface core to enable said auxiliary processing module to perform said auxiliary processing operation.

23. An interface subsystem as defined in claim 22 in which said auxiliary processing module during an auxiliary processing operation generates auxiliary processed information, the interface core providing said auxiliary processed information to the simulator interface module of said at least one simulation system for provision to said at least one transactor.

24. An interface subsystem as defined in claim 1 further comprising a plurality of tests, each including a simulation information generator for providing simulation information to be transferred to said test for use during a simulation run and a simulation control indicator generator for generating a simulation control indicator for controlling said simulation system, said interface subsystem further including a simulation control synchronization module for synchronizing the tests in providing respective simulation information and simulation control indicators to the at least one simulation system.

25. An interface subsystem as defined in claim 24 in which the simulation control synchronization module enables the tests to provide simulation information to said at least one simulation system prior to a simulation run.

26. An interface subsystem as defined in claim 25 in which said simulation control synchronization module further enables one of the tests to provide a simulation control indicator after all of the tests which are to provide simulation information for a simulation run have provided simulation information.

27. An interface subsystem as defined in claim 1 in which said at least one test provides at least one callback mechanism, said interface core using said callback mechanism in transferring said simulation result information to said information receiver.

28. An interface subsystem as defined in claim 27 in which callback mechanism is identified by a callback identifier, said at least one test providing said callback identifier to said interface core, the interface core using said callback identifier to initiate use of said callback mechanism.

29. An interface subsystem as defined in claim 28 in which said interface core provides an information transfer link to said at last one test, said interface core and said at least one test each including an information transfer link establishment module for establishing said information transfer link, said at least one test using the information transfer link establishment module to provide the callback identifier.

30. An interface subsystem as defined in claim 1 in which said at least simulation system provides at least one callback mechanism, said interface core using said callback mechanism in transferring said simulation result information to said information receiver.

31. An interface subsystem as defined in claim 30 in which callback mechanism is identified by a callback identifier, said at least one simulation system providing said callback identifier to said interface core, the interface core using said callback identifier to initiate use of said callback mechanism.

32. An interface subsystem as defined in claim 31 in which said interface core provides an information transfer link to said at last one simulation system, said interface core and said at least one simulation system each including an information transfer link establishment module for establishing said information transfer link, said at least one simulation system using the information transfer link establishment module to provide the callback identifier.

33. For use in a system including at least one simulation system for facilitating simulation of at least one simulation model under control of at least one test, an interface subsystem computer program product for use in connection with a computer to allow said at least one test and said at least one simulation system to transfer information therebetween and for enabling control by said at least one test of said simulation system in simulating said simulation model during a simulation run, said at least one simulation system including at least one transactor for (a) providing information to said simulation model to control the simulation model, (b) pausing a simulation run in response to detection of a selected event, and (c) generating simulation result information, said interface subsystem computer program product comprising a computer readable medium having thereon:

A. each said at least one test including simulation information generator code devices for enabling said computer to provide simulation information to be transferred to said test for use during a simulation run and simulation control indicator generator code devices for enabling said computer to generate a simulation control indicator for controlling said simulation system, each said at least one test further having associated therewith information receiver code devices for enabling said computer to receive simulation result information;

B. each said at least one simulation system including;

i. associated with said at least one transactor, information receiver code devices for enabling said computer to receive simulation information for use in connection with the associated transactor during a simulation run;

ii. simulator interface code devices associated with each said at least one said simulation system for enabling said computer to (a) receive simulation information and provide the received simulation to a transactor'"'"'s information receiver for use by the associated transactor, (b) receive simulation result information from said at least one transactor to be provided to said at least one test, and (c) control said at least one simulation system to initiate a simulation run in response to receipt of a control indicator; and

C. interface core code devices for enabling said computer to transfer (i) said simulation information from said at least one test for processing in response to the simulator interface code devices for a selected one of said at least one simulating system for provision to a selected one of said at least one of said transactor'"'"'s information receiver code devices for use by a transactor during a simulation run, (ii) said simulation control indicator for controlling a selected one of said at least one simulation system, and (iii) for transferring said simulation result information from said at least one transactor for processing by said computer in response to information receiver code devices associated of a selected one of said at least one test.

34. An interface subsystem as defined in claim 33, in which the at least one simulation model is in the form of a hardware description language description of an electronic circuit.

35. An interface subsystem as defined in claim 33 in which the at least one test is defined by a computer program product in the form of a high-level computer programming language.

36. An interface subsystem computer program product as defined in claim 33 in which said information receiver code devices associated with said at least one test enable said computer to provide a mailbox.

37. An interface subsystem computer program product as defined in claim 33 in which said information receiver code devices associated with said at least one transactor enable said computer to provide a mailbox.

38. An interface subsystem computer program product as defined in claim 33 in which said interface core code devices enable said computer to provide at least one bi-directional information transfer link to each of said at least one test and each of said at least one simulator interface module.

39. An interface subsystem computer program product as defined in claim 38 in which at least one of said at least one bi-directional information transfer links comprises two uni-directional information transfer links for transferring information in opposite directions.

40. An interface subsystem computer program product as defined in claim 39 in which each said uni-directional information transfer link comprises a remote procedure call link.

41. An interface subsystem computer program product as defined in claim 33 in which said at least one said test generates said simulation information in the form of at least one simulation information message packet, said simulation information message packet including simulation system identification information identifying one of said at least one simulation system to receive the simulation information message packet.

42. An interface subsystem computer program product as defined in claim 41 in which each said at least one simulation system has an associated simulation system identifier, said simulation system identification information in each said simulation information message packet identifying the simulation system identifier of the at least one simulation system to receive the simulation information message packet.

43. An interface subsystem computer program product as defined in claim 41 in which said simulation information message packet further includes transactor identification information for identifying one of said at least one transactor to receive the simulation information in said simulation information message packet.

44. An interface subsystem computer program product as defined in claim 43 in which each at least one transactor has an associated transactor identifier, said transactor identification information in each said simulation information message packet identifying the transactor identifier of the at least one transactor to receive the simulation information in said simulation information message packet.

45. An interface subsystem computer program product as defined in claim 43 in which at least one said transactor has a plurality of associated information receivers each identified by an information receiver identifier, said simulation information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

46. An interface subsystem computer program product as defined in claim 33 in which said at least one said transactor generates said simulation result information in the form of at least one simulation result information message packet, said simulation result information message packet including test identification information identifying one of said at least one test to receive the simulation result information message packet.

47. An interface subsystem computer program product as defined in claim 46 in which each said at least one test has an associated test identifier, said test identification information in each said simulation information message packet identifying the test identifier of the at least one test to receive the simulation result information message packet.

48. An interface subsystem computer program product as defined in claim 46 in which at least one said test has associated information receiver code devices enabling said computer to provide a plurality of information receivers each identified by an information receiver identifier, said simulation result information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

49. An interface subsystem computer program product as defined in claim 33 further comprising a simulation information control code devices for enabling said computer to control the simulation information generator of said at least one test.

50. An interface subsystem computer program product as defined in claim 49 in which said simulation information control code devices enable said computer to control the simulation information generator to provide simulation information for said at least one simulation system when said simulation system is not engaged in a simulation run.

51. An interface subsystem computer program product as defined in claim 50 in which said simulation information control computer program product enables said computer to disable said simulation information generator from providing simulation information for said at least one simulation system when said simulation system is engaged in a simulation run.

52. An interface subsystem computer program product as defined in claim 33 in which said at least one transactor during a simulation run generates supplemental information requests requesting supplemental simulation information from said at least one test, said interface core code devices enabling said computer to transfer said supplemental information request so said at least one test to obtain said supplemental simulation information therefrom.

53. An interface subsystem computer program product as defined in claim 52 in which said at least one test includes a mailbox for storing supplemental simulation information, the interface core code devices enabling said computer to, in response to a supplemental information request from said at least one transactor, retrieve said supplemental simulation information from said mailbox for provision to said at least one transactor.

54. An interface subsystem computer program product as defined in claim 33 further including at least one auxiliary processing module for performing an auxiliary processing operation, said at least one transactor generating an auxiliary processing request, said simulator interface computer program product enabling said computer, in response to an auxiliary processing request enabling said interface core, to enable said auxiliary processing module to perform said auxiliary processing operation.

55. An interface subsystem computer program product as defined in claim 54 in which said auxiliary processing module during an auxiliary processing operation generates auxiliary processed information, the interface core code devices enabling said computer to provide said auxiliary processed information to the simulator interface module of said at least one simulation system for provision to said at least one transactor.

56. An interface subsystem computer program product as defined in claim 33 further comprising a plurality of tests, each including simulation information generation code devices for enabling said computer to providing simulation information to be transferred to said test for use during a simulation run and simulation control indicator generation code devices for enabling said computer to generate a simulation control indicator for controlling said simulation system, said interface subsystem further including simulation control synchronization code devices for enabling the computer to synchronize the tests in providing respective simulation information and simulation control indicators to the at least one simulation system.

57. An interface subsystem computer program product as defined in claim 56 in which the simulation control synchronization code devices enable the tests to provide simulation information to said at least one simulation system prior to a simulation run.

58. An interface subsystem computer program product as defined in claim 57 in which said simulation control synchronization code devices further enable one of the tests to provide a simulation control indicator after all of the tests which are to provide simulation information for a simulation run have provided simulation information.

59. An interface subsystem computer program product as defined in claim 33 in which said at least one test code device provides at least one callback mechanism code device, said interface core code devices enabling said computer to use said callback mechanism code device in transferring said simulation result information to said information receiver code device.

60. An interface subsystem computer program product as defined in claim 59 in which callback mechanism code device is identified by a callback identifier, said at least one test code device enabling said computer to provide said callback identifier for use said interface core code devices, the interface core code devices enabling said computer to use said callback identifier to initiate use of said callback mechanism.

61. An interface subsystem computer program product as defined in claim 60 in which said interface core code devices enables said computer to provide an information transfer link to said at last one test code device, said interface core code devices and said at least one test code device each including an information transfer link establishment module for enabling said computer to establish said information transfer link, said computer using the information transfer link establishment module to provide the callback identifier.

62. An interface subsystem computer program product as defined in claim 33 in which said at least simulation system code device provides at least one callback mechanism, said interface core code devices enabling said computer to use said callback mechanism in transferring said simulation result information to said information receiver code devices.

63. An interface subsystem computer program product as defined in claim 62 in which callback mechanism is identified by a callback identifier, said at least one simulation system code devices enabling said computer to provide said callback identifier for processing by said interface core code devices, the interface core code devices enabling said computer to use said callback identifier to initiate use of said callback mechanism.

64. An interface subsystem computer program product as defined in claim 63 in which said interface core code devices enable said computer to provide an information transfer link to said at last one simulation system code device, said interface core code devices and said at least one simulation system code devices each including an information transfer link establishment module for enabling said computer to establish said information transfer link, said at least one simulation system code devices enabling said computer to use the information transfer link establishment module to provide the callback identifier.

82. A method as defined in claim 61 in which said simulation information generator control step includes the step of providing simulation information for said at least one simulation system when said simulation system is not engaged in a simulation run.

83. A method as defined in claim 82 in which said simulation information generator control step includes the step of disabling said simulation information generator from providing simulation information for said at least one simulation system when said simulation system is engaged in a simulation run.

65. A method of controlling a system including at least one simulation system for facilitating simulation of at least one simulation model under control of at least one test, an interface subsystem for allowing said at least one test and said at least one simulation system to transfer information therebetween and for enabling control by said at least one test of said simulation system in simulating said simulation model during a simulation run, said at least one simulation system including at least one transactor for (a) providing information to said simulation model to control the simulation model, (b) pausing a simulation run in response to detection of a selected event, and (c) generating simulation result information, said method comprising the steps of:

A. providing each said at least one test with a simulation information generator for providing simulation information to be transferred to said simulation system for use during a simulation run and a simulation control indicator generator for generating a simulation control indicator for controlling said simulation system, each said at least one test further having associated therewith at least one information receiver for receiving simulation result information;

B. providing each said at least one simulation system;

i. associating with said at least one transactor an information receiver for receiving simulation information for use by the associated transactor during a simulation run;

ii. a simulator interface module associated with each said at least one said simulation system for (a) receiving simulation information and providing the received simulation to an information receiver for use by the associated transactor, (b) receiving simulating result information from said at least one transactor to be provided to said at least one test, and (c) controlling said at least one simulation system to initiate a simulation run in response to receipt of a control indicator; and

C. providing an interface core for transferring (i) said simulation information from said at least one test to the simulator interface module of a selected one of said at least one simulating system for provision to a selected one of said at least one of said transactor'"'"'s information receiver for use by a transactor during a simulation run, (ii) said simulation control indicator for controlling a selected one of said at least one simulation system, and (iii) for transferring said simulation result information from said at least one transactor to said information receiver of a selected one of said at least one test.

66. A method as defined in claim 65, in which the at least one simulation model is in the form of a hardware description language description of an electronic circuit.

67. A method as defined in claim 65 in which the at least one test is defined by a computer program product in the form of a high-level computer programming language.

68. A method as defined in claim 65 in which said information receiver of said at least one test comprises a mailbox.

69. A method as defined in claim 65 in which said information receiver of said at least one transactor comprises a mailbox.

70. A method as defined in claim 65 in which said interface core provides at least one bi-directional information transfer link to each of said at least one test and each of said at least one simulator interface module.

71. A method as defined in claim 70 in which at least one of said at least one bi-directional information transfer link comprises two uni-directional information transfer links for transferring information in opposite directions.

72. A method as defined in claim 70 in which each said uni-directional information transfer link comprises a remote procedure call link.

73. A method as defined in claim 65 in which said at least one said test is enabled to generate said simulation information in the form of at least one simulation information message packet, said simulation information message packet including simulation system identification information identifying one of said at least one simulation system to receive the simulation information message packet.

74. A method as defined in claim 73 in which each said at least one simulation system has an associated simulation system identifier, said simulation system identification information in each said simulation information message packet identifying the simulation system identifier of the at least one simulation system to receive the simulation information message packet.

75. A method as defined in claim 73 in which said simulation information message packet further includes transactor identification information for identifying one of said at least one transactor to receive the simulation information in said simulation information message packet.

76. A method as defined in claim 75 in which each at least one transactor has an associated transactor identifier, said transactor identification information in each said simulation information message packet identifying the transactor identifier of the at least one transactor to receive the simulation information in said simulation information message packet.

77. A method as defined in claim 75 in which at least one said transactor has a plurality of associated information receivers each identified by an information receiver identifier, said simulation information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

78. A method as defined in claim 65 in which said at least one said transactor generates said simulation result information in the form of at least one simulation result information message packet, said simulation result information message packet including test identification information identifying one of said at least one test to receive the simulation result information message packet.

79. A method as defined in claim 78 in which each said at least one test has an associated test identifier, said test identification information in each said simulation information message packet identifying the test identifier of the at least one test to receive the simulation result information message packet.

80. A method as defined in claim 78 in which at least one said test has a plurality of associated information receivers each identified by an information receiver identifier, said simulation result information message packet further including information receiver identification information for identifying one of said plurality of information receivers to receive the simulation information in said simulation information message packet.

81. A method as defined in claim 65 further comprising the step of controlling the simulation information generator of said at least one test.

84. A method as defined in claim 65 in which said at least one transactor during a simulation run generates supplemental information requests requesting supplemental simulation information from said at least one test, said interface core being enabled to transfer said supplemental information request so said at least one test to obtain said supplemental simulation information therefrom.

85. A method as defined in claim 84 in which said at least one test includes a mailbox for storing supplemental simulation information, the interface core in response to a supplemental information request from said at least one transactor being enabled to retrieve said supplemental simulation information from said mailbox for provision to said at least one transactor.

86. A method as defined in claim 65 further including at least one auxiliary processing module for performing an auxiliary processing operation, said at least one transactor generating an auxiliary processing request, said simulator interface module in response to an auxiliary processing request enabling said interface core to, in turn, to enable said auxiliary processing module to perform said auxiliary processing operation.

87. A method as defined in claim 86 in which said auxiliary processing module during an auxiliary processing operation generates auxiliary processed information, the interface core being enabled to provide said auxiliary processed information to the simulator interface module of said at least one simulation system for provision to said at least one transactor.

88. A method as defined in claim 65 for use in connection with a system comprising a plurality of tests, each including a simulation information generator for providing simulation information to be transferred to said test for use during a simulation run and a simulation control indicator generator for generating a simulation control indicator for controlling said simulation system, said method further including the step of synchronizing the tests in providing respective simulation information and simulation control indicators to the at least one simulation system.

89. A method as defined in claim 88 in which the simulation control synchronization step includes the step of enabling the tests to provide simulation information to said at least one simulation system prior to a simulation run.

90. A method as defined in claim 89 in which said simulation control synchronization step further includes the step of enabling one of the tests to provide a simulation control indicator after all of the tests which are to provide simulation information for a simulation run have provided simulation information.

91. An interface subsystem as defined in claim 65 in which said at least one test provides at least one callback mechanism, said interface core using said callback mechanism in transferring said simulation result information to said information receiver.

92. An interface subsystem as defined in claim 91 in which callback mechanism is identified by a callback identifier, said at least one test providing said callback identifier to said interface core, the interface core using said callback identifier to initiate use of said callback mechanism.

93. An interface subsystem as defined in claim 92 in which said interface core provides an information transfer link to said at last one test, said interface core and said at least one test each including an information transfer link establishment module for establishing said information transfer link, said at least one test using the information transfer link establishment module to provide the callback identifier.

94. An interface subsystem as defined in claim 65 in which said at least simulation system provides at least one callback mechanism, said interface core using said callback mechanism in transferring said simulation result information to said information receiver.

95. An interface subsystem as defined in claim 94 in which callback mechanism is identified by a callback identifier, said at least one simulation system providing said callback identifier to said interface core, the interface core using said callback identifier to initiate use of said callback mechanism.

96. An interface subsystem as defined in claim 95 in which said interface core provides an information transfer link to said at last one simulation system, said interface core and said at least one simulation system each including an information transfer link establishment module for establishing said information transfer link, said at least one simulation system using the information transfer link establishment module to provide the callback identifier.