Claims
- 1. A method for providing centralized access to instrumentation count event information generated by simulation testing of a hardware simulation model, wherein said simulation testing is performed within a batch simulation farm by multiple simulation clients communicating with an instrumentation server, said method comprising:
generating an entity list within a simulation client, wherein said entity list includes an identifier for each design entity within said hardware simulation model that has at least one instantiated instrumentation count event; delivering said entity list from said simulation client to said instrumentation server; and associating said entity list with an identifier for said hardware simulation model within said instrumentation server such that instrumentation count event information is accessible from said instrumentation server by individual design entity information.
- 2. The method of claim 1, wherein said entity list is generated during model build processing of said hardware simulation model prior to simulation of said hardware simulation model by said simulation client.
- 3. The method of claim 1, wherein said associating said entity list to an HDL simulation model identifier comprises generating a translation table that includes entries indexed in accordance with said design entity identifiers.
- 4. The method of claim 3, wherein said translation table includes entries indexed in accordance with each design entity identifier included with each entity list file received within said instrumentation server, said generation of said translation table including mapping said hardware simulation model identifier to each translation table entry indexed by a design entity identifier corresponding to a design entity included within said hardware simulation model.
- 5. The method of claim 1, further comprising:
simulating said hardware simulation model within a simulation client; delivering an aggregate count event packet from said simulation client to said instrumentation server, wherein said aggregate count event packet includes count event data recorded during said simulation; and within said instrumentation server, storing said count event data within cumulative count data storage files.
- 6. The method of claim 5, wherein said storing said count event data within cumulative count data storage files further comprises:
associating said count event data with a specified time period within a higher level count event directory; and associating said count event data with a specified hardware simulation model within a lower level directory, wherein said lower level directory is subsumed by said higher level directory such that count event data can be queried first by time and second by hardware simulation model identity.
- 7. A system for providing centralized access to instrumentation count event information generated by simulation testing of a hardware simulation model, wherein said simulation testing is performed within a batch simulation farm by multiple simulation clients communicating with an instrumentation server, said system comprising:
processing means for generating an entity list within a simulation client, wherein said entity list includes an identifier for each design entity within said hardware simulation model that has at least one instantiated instrumentation count event; processing means for delivering said entity list from said simulation client to said instrumentation server; and processing means for associating said entity list with an identifier for said hardware simulation model within said instrumentation server such that instrumentation count event information is accessible from said instrumentation server by individual design entity information.
- 8. The system of claim 7, wherein said entity list is generated during model build processing of said hardware simulation model prior to simulation of said hardware simulation model by said simulation client.
- 9. The system of claim 7, further comprising processing means for generating a translation table that includes entries indexed in accordance with said design entity identifiers.
- 10. The system of claim 9, wherein said translation table includes entries indexed in accordance with each design entity identifier included with each entity list file received within said instrumentation server, said system further comprising processing means for mapping said hardware simulation model identifier to each translation table entry indexed by a design entity identifier corresponding to a design entity included within said hardware simulation model.
- 11. The system of claim 7, further comprising:
processing means for simulating said hardware simulation model within a simulation client; processing means for delivering an aggregate count event packet from said simulation client to said instrumentation server, wherein said aggregate count event packet includes count event data recorded during said simulation; and processing means within said instrumentation server for storing said count event data within cumulative count data storage files.
- 12. The system of claim 11, wherein said processing means for storing said count event data within cumulative count data storage files further comprises:
processing means for associating said count event data with a specified time period within a higher level count event directory; and processing means for associating said count event data with a specified hardware simulation model within a lower level directory, wherein said lower level directory is subsumed by said higher level directory such that count event data can be queried first by time and second by hardware simulation model identity.
- 13. A computer program product for providing centralized access to instrumentation count event information generated by simulation testing of a hardware simulation model, wherein said simulation testing is performed within a batch simulation farm by multiple simulation clients communicating with an instrumentation server, said computer program product comprising:
program instruction means for generating an entity list within a simulation client, wherein said entity list includes an identifier for each design entity within said hardware simulation model that has at least one instantiated instrumentation count event; program instruction means for delivering said entity list from said simulation client to said instrumentation server; and program instruction means for associating said entity list with an identifier for said hardware simulation model within said instrumentation server such that instrumentation count event information is accessible from said instrumentation server by individual design entity information.
- 14. The computer program product of claim 13, wherein said entity list is generated during model build processing of said hardware simulation model prior to simulation of said hardware simulation model by said simulation client.
- 15. The computer program product of claim 13, further comprising program instruction means for generating a translation table that includes entries indexed in accordance with said design entity identifiers.
- 16. The computer program product of claim 15, wherein said translation table includes entries indexed in accordance with each design entity identifier included with each entity list file received within said instrumentation server, said computer program product further comprising program instruction means for mapping said hardware simulation model identifier to each translation table entry indexed by a design entity identifier corresponding to a design entity included within said hardware simulation model.
- 17. The computer program product of claim 13, further comprising:
program instruction means for simulating said hardware simulation model within a simulation client; program instruction means for delivering an aggregate count event packet from said simulation client to said instrumentation server, wherein said aggregate count event packet includes count event data recorded during said simulation; and program instruction means within said instrumentation server for storing said count event data within cumulative count data storage files.
- 18. The computer program product of claim 17, wherein said program instruction means for storing said count event data within cumulative count data storage files further comprises:
program instruction means for associating said count event data with a specified time period within a higher level count event directory; and program instruction means for associating said count event data with a specified hardware simulation model within a lower level directory, wherein said lower level directory is subsumed by said higher level directory such that count event data can be queried first by time and second by hardware simulation model identity.
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present application is related to the following co-pending U.S. patent applications: U.S. patent application Ser. No. ______ (Docket No. AUS920010960US1) filed on _, titled “Maintaining Data Integrity Within A Distributed Simulation Environment”; U.S. patent application Ser. No. ______ (Docket No. AUS920010962US1) filed on ______, titled “Centralized Disablement Of Instrumentation Events Within A Batch Simulation Farm Network”; U.S. patent application Ser. No. ______ (Docket No. AUS920000861US1) filed on ______, titled “Fail Thresholding In A Batch Simulation Farm Network”; U.S. patent application Ser. No. ______ (Docket No. AUS920000652US1) filed on ______, titled “Tracking Coverage Results In A Batch Simulation Farm Network”; U.S. patent application Ser. No. ______ (Docket No. AUS920000651US1) filed on ______, titled “Non-Redundant Collection Of Harvest Events Within A Batch Simulation Farm Network”; and U.S. patent application Ser. No. ______ (Docket No. AUS920010961US1) filed on ______, titled “Annealing Harvest Testcase Collection Within A Batch Simulation Farm”. The above-mentioned patent applications are assigned to the assignee of the present invention and are incorporated herein by reference.