Transaction checking for system architecture validation

• US 6,496,792 B1
• Filed: 07/06/1998
• Issued: 12/17/2002
• Est. Priority Date: 07/06/1998
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Magnusson, Eric J.
• Primary Examiner(s): CHOI, KYLE JAEHUN
• Application Number:
  US09/111,126
• Time in Patent Office: 1,625 Days
• Field of Search: 703/16, 703/17, 703/21, 703/27, 714/37, 714/39, 714/45, 714/49, 714/736
• US Class Current: 703/27
• 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

A method and apparatus for a transaction checking for system architecture validation are provided. Tracking data is received from trackers in the system. The tracking data is parsed to construct queues. These queues are compared with each other. For one embodiment, the queues are further compared with predicted behavior of the element that was tested. Discrepancies between the queues and the queue and predicted behavior are flagged.

Claims

1. A method comprising:

receiving tracking data generated by at least a first tracker and a second tracker of a simulation environment, the first tracker tracking transactions crossing a first transaction interface and the second tracker tracking transactions crossing a second transaction interface;

parsing the transaction data into a plurality of queues including a first general queue associated with a first device residing on the first transaction interface, a second general queue associated with a second device residing on the second transaction interface, a first destination queue associated with the first device, and a second destination queue associated with the second device, the first general queue to store transaction records corresponding to transactions originated by the first device, the second general queue to store transaction records corresponding to transactions originated by the second device, the first destination queue to store transaction records corresponding to transactions targeted for the first device, and the second destination queue to store transaction records corresponding to transactions targeted for the second device; and

verifying bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and the second destination queue.

2. The method of claim 1, further comprising verifying bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and the first destination queue.

3. The method of claim 1, further comprising detecting any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on the first destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first destination queue.

4. The method of claim 3, further comprising:

flagging the unaccounted-for transactions;

generating an error record; and

adding the flagged unaccounted-for transactions to the error record.

5. The method of claim 1, further comprising detecting any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second destination queue.

6. The method of claim 5, further comprising:

flagging the unaccounted-for transactions;

generating an error record; and

adding the flagged unaccounted-for transactions to the error record.

7. The method of claim 1, further comprising verifying bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and a second predicted behavior queue, wherein the second predicted behavior queue comprising behavioral model transactions based on a specification of the second device.

8. The method of claim 1, further comprising verifying bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and a first predicted behavior queue, wherein the first predictive behavior queue comprising behavioral model transactions based on a specification of the first device.

9. The method of claim 1, further comprising detecting any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on a first predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first predicted behavior queue.

10. The method of claim 9, further comprising:

flagging the unaccounted-for transactions;

generating and error record; and

adding the flagged unaccounted-for transactions to the error record.

11. The method of claim 1, further comprising detecting any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on a second predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second predicted behavior queue.

12. The method of claim 11, further comprising:

flagging the unaccounted-for transactions;

generating an error record; and

adding the flagged unaccounted-for transactions to an error record.

13. The method of claim 1, wherein the tracking data is generated by the first tracker and the second tracker saving each incoming and outgoing data.

14. The method of claim 1, further comprising constructing a transaction record from which the plurality of queues are generated.

15. The method of claim 1, further comprising updating system configuration in accordance with a current programming state.

16. The method of claim 1, wherein the tracking data comprises transaction records including a bus-specific tag and a bus-independent tag.

17. The method of claim 16, wherein the bus-independent tag includes one or more of the following status and event indications:

transaction time, cycle type, address, data information.

18. The method of claim 17, wherein the bus-specific tag includes one or more of the following status and event indications:

locked status, cycle translation, cache coherency, buffer management, chip-select assertion, transaction termination, event handling, timing, system arbitration events.

19. The method of claim 16, further comprising:

verifying the bus-specific tag and the bus-independent tag by comparing the tags with a first predicted behavior queue and a second predicted behavior queue; and

determining discrepancies between actual behavior as indicated by the tags and the predicted behavior as indicated by the predicted behavior queues.

20. A system comprising:

at least a first tracker and a second tracker to generate tracking data, the first tracker tracking transactions crossing a first transaction interface and the second tracker tracking transactions crossing a second transaction interface;

a parser to parse the transaction data into a plurality of queues including a first general queue associated with a first device residing on the first transaction interface, a second general queue associated with a second device residing on the second transaction interface, a first destination queue associated with the first device, and a second destination queue associated with the second device, the first general queue to store transaction records corresponding to transactions originated by the first device, the second general queue to store transaction records corresponding to transactions originated by the second device, the first destination queue to store transaction records corresponding to transactions targeted for the first device, and the second destination queue to store transaction records corresponding to transactions targeted for the second device; and

a transaction processor to verify bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and the second destination queue.

21. The system of claim 20, where the transaction processor is further to verify bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and the first destination queue.

22. The system of claim 20, wherein the transaction processor is further to detect any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on the first destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first destination queue.

23. The system of claim 22, wherein the transaction processor is further to:

flag the unaccounted-for transactions;

generate an error record; and

add the flagged unaccounted-for transactions to the error record.

24. The system of claim 20, wherein the transaction processor is further to detect any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second destination queue.

25. The system of claim 24, wherein the transaction processor is further to:

flag the unaccounted-for transactions;

generate an error record; and

add the flagged unaccounted-for transactions to the error record.

26. The system of claim 20, wherein the transaction processor is further to verify bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and a second predicted behavior queue, wherein the second predictive behavior queue comprising behavioral model transactions based on a specification of the second device.

27. The system of claim 20, wherein the transaction processor is further to verify bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and a first predicted behavior queue, wherein the first predictive behavior queue comprising behavioral model transactions based on a specification of the first device.

28. The system of claim 20, wherein the transaction processor is further to detect any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on a first predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first predicted behavior queue.

29. The system of claim 28, wherein the transaction processor is further to:

flag the unaccounted-for transactions;

generate an error record; and

add the flagged unaccounted-for transactions to the error record.

30. The system of claim 20, wherein the transaction processor is further to detect any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on a second predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second predicted behavior queue.

31. The system of claim 30, wherein the transaction process is further to:

flag the unaccounted-for transactions;

generate an error record; and

add the flagged unaccounted-for transactions to the error record.

32. A method comprising:

receiving tracking data generated by at least a first tracker and a second tracker of a simulation environment, the first tracker tracking transactions crossing a first transaction interface and the second tracker tracking transactions crossing a second transaction interface;

parsing the transaction data into a plurality of queues including a first general queue associated with a first device residing on the first transaction interface, a second general queue associated with a second device residing on the second transaction interface, a first destination queue associated with the first device, and a second destination queue associated with the second device, the first general queue to store transaction records corresponding to transactions originated by the first device, the second general queue to store transaction records corresponding to transactions originated by the second device, the first destination queue to store transaction records corresponding to transactions targeted for the first device, and the second destination queue to store transaction records corresponding to transactions targeted for the second device; and

verifying bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and a second predicted behavior queue, wherein the second predictive behavior queue comprising behavioral model transactions based on a specification of the second device.

33. The method of claim 32, further comprising verifying bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and a first predicted behavior queue, wherein the first predictive behavior queue comprising behavioral model transactions based on a specification of the first device.

34. The method of claim 32, further comprising detecting any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on the first predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first predicted behavior queue.

35. The method of claim 34, further comprising:

flagging the unaccounted-for transactions;

generating and error record; and

adding the flagged unaccounted-for transactions to the error record.

36. The method of claim 32, further comprising detecting any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second predicted behavior queue.

37. The method of claim 36, further comprising:

flagging the unaccounted-for transactions;

generating an error record; and

adding the flagged unaccounted-for transactions to an error record.

38. A transaction processing unit comprising:

a tracking data receiver to receive tracking data generated by at least a first tracker and a second tracker of a simulation environment, the first tracker tracking transactions crossing a first transaction interface and the second tracker tracking transactions crossing a second transaction interface

a parser to parse the transaction data into a plurality of queues including a first general queue associated with a first device residing on the first transaction interface, a second general queue associated with a second device residing on the second transaction interface, a first destination queue associated with the first device, and a second destination queue associated with the second device, the first general queue to store transaction records corresponding to transactions originated by the first device, the second general queue to store transaction records corresponding to transactions originated by the second device, the first destination queue to store transaction records corresponding to transactions targeted for the first device, and the second destination queue to store transaction records corresponding to transactions targeted for the second device; and

a transaction processor to verify bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and a second predicted behavior queue, wherein the second predictive behavior queue comprising behavioral model transactions based on a specification of the second device.

39. The transaction processing unit of claim 38, further comprising a transaction record generator for generating a transaction record from the tracking data.

40. The transaction processing unit of claim 38, wherein the transaction processor is further to verify bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and a first predicted behavior queue, wherein the first predictive behavior queue comprising behavioral model transactions based on a specification of the first device.

41. The transaction processing unit of claim 38, wherein the transaction processor is further to detect any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on a first predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first predicted behavior queue.

42. The transaction processing unit of claim 38, wherein the transaction processor is further to detect any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second predicted behavior queue.

43. The transaction processing unit of claim 38, wherein the transaction processor is further to verify bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and the second destination queue.

44. The transaction processing unit of claim 38, wherein the transaction processor is further to verify bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and the first destination queue.

45. The transaction processing unit of claim 38, wherein the transaction processor is further to detect any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on the first destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first destination queue.

46. The transaction processing unit of claim 38, wherein the transaction processor is further to detect any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second destination queue.

47. The transaction processing unit of claim 38, wherein the transaction processor is further to generate an error record including the unaccounted-for transactions.

48. The transaction processing unit of claim 47, wherein the unaccounted-for transactions comprise extra transactions, missing transactions, or corrupted transactions.

49. An apparatus comprising:

means for receiving tracking data generated by at least a first tracker and a second tracker of a simulation environment, the first tracker tracking transactions crossing a first transaction interface and the second tracker tracking transactions crossing a second transaction interface

means for parsing the transaction data into a plurality of queues including a first general queue associated with a first device residing on the first transaction interface, a second general queue associated with a second device residing on the second transaction interface, a first destination queue associated with the first device, and a second destination queue associated with the second device, the first general queue to store transaction records corresponding to transactions originated by the first device, the second general queue to store transaction records corresponding to transactions originated by the second device, the first destination queue to store transaction records corresponding to transactions targeted for the first device, and the second destination queue to store transaction records corresponding to transactions targeted for the second device; and

means for verifying bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and a second predicted behavior queue, wherein the second predictive behavior queue comprising behavioral model transactions based on a specification of the second device.

50. The apparatus of claim 49, further comprising means for generating a transaction record from the tracking data.

51. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for verifying bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and a first predicted behavior queue, wherein the first predictive behavior queue comprising behavioral model transactions based on a specification of the first device.

52. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for detecting any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on a first predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first predicted behavior queue.

53. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for detecting any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second predicted behavior queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second predicted behavior queue.

54. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for verifying bus transactions originated by the first device and targeted for the second device by comparing corresponding transaction records from the first general queue and the second destination queue.

55. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for verifying bus transactions originated by the second device and targeted for the first device by comparing corresponding transaction records from the second general queue and the first destination queue.

56. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for detecting any unaccounted-for transactions for the first device by testing whether there are any transaction records remaining on the first destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the first device were originated have been matched up with corresponding transaction records from the first destination queue.

57. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for detecting any unaccounted-for transactions for the second device by testing whether there are any transaction records remaining on the second destination queue after all transaction records from general queues associated with other devices from which transactions targeted for the second device were originated have been matched up with corresponding transaction records from the second destination queue.

58. The apparatus of claim 49, wherein the means for verifying bus transactions originated by the first device is further for generating an error record including the unaccounted-for transactions.

59. The apparatus of claim 58, Wherein the unaccounted-for transactions comprise extra transactions, missing transactions, or corrupted transactions.