{"id":12080,"date":"2016-01-29T15:34:39","date_gmt":"2016-01-29T22:34:39","guid":{"rendered":"https:\/\/blogs.mentor.com\/verificationhorizons\/?p=12080"},"modified":"2026-03-27T08:40:26","modified_gmt":"2026-03-27T12:40:26","slug":"whats-going-on-with-my-systemverilog-queue","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/2016\/01\/29\/whats-going-on-with-my-systemverilog-queue\/","title":{"rendered":"What’s Going On With My SystemVerilog Queue?"},"content":{"rendered":"

I want my MTV!<\/p>\n

And while I’m at it, I’m also curious about what’s going on with my SystemVerilog queues. You too with your queues?<\/p>\n

What kinds of information do we want to know from our queues?<\/p>\n

How about what’s in them? Then how big they are. Maybe how many times they’ve been certain sizes (“this queue was empty for almost the entire simulation” – or “this queue was almost always larger than 100 elements”) – And then Why?<\/p>\n

“Why?” is the hard part. That’s other kinds of debug for another discussion… But we can certainly produce the report on queue size, activity and bins; let the queue debugging begin.<\/p>\n

What if we had a magic macro – a macro that would instrument a queue, so that we could better understand what it was doing?<\/p>\n

My Queue:<\/p>\n

int<\/strong> my_queue[$];\n\n<\/pre>\n
The “magic macro”:<\/p>\n
`QUEUE_VIEW_C(int<\/strong>, my_queue)\n\n<\/pre>\n
The magic macro takes two arguments – the type contained in the queue (int), and the queue name (my_queue). That’s *really* easy to use. The only change that is needed is to add this magic macro where there is a queue that needs some monitoring.<\/p>\n
OK. What kind of information do we really want in our reports?<\/p>\n
  Current Queue Size\n  Maximum Queue Size so far\n  The top 3 elements in the Queue (or the last 3, or both)\n  Queue Contents (the whole thing)\n  Queue size bins\n\n<\/pre>\n
Inside the macro we’ll build a queue monitor. It can monitor many things – for example in pseudocode, our queue monitor:<\/p>\n
 37 task<\/strong> monitor (ref<\/strong> T q[$]);\n 38   forever<\/strong> begin<\/strong>\n 39     @(q.size change);\n 40     size_bins[q.size()]++;\n 41     if<\/strong> (q.size() > maxsize) maxsize = q.size();\n 42     f0 = q[0];\n 43     f1 = q[1];\n 44     f2 = q[2];\n 45     $display(\"@%t: %s : size=%0d %0d %0d %0d q=[%p]\", \n 46       $time, name, q.size(), f0, f1, f2, q);\n 47   end<\/strong>\n 48 endtask\n\n<\/strong><\/pre>\n
Line 37 provides the actual queue as a reference argument. That’s how the queue will be tracked.
\nLine 38 and 39 provide an infinite loop which waits for the queue to change size.
\nOnce the queue changes size, Line 40 does the binning. In one line it increments the bin for the current queue size.
\nLine 41 captures the maximum size that this queue has attained.
\nLine 42, 43 and 44 capture the top of the queue, the second and the third elements (with range checking removed).
\nLine 45 just prints a nice snapshot of the queue: the current time, the queue viewer name, the size of the queue, the top 3 values, and finally using the magic “%p”, it prints the entire queue.<\/p>\n
Here’s some output from line 45:<\/p>\n
 # @ 123: qview_6.c_flow_q : size=0 0 0 0 q=['{}]\n # @ 152: qview_6.c_flow_q : size=1 2 0 0 q=['{2}]\n # @ 160: qview_6.c_flow_q : size=2 2 2 0 q=['{2, 2}]\n # @ 168: qview_6.c_flow_q : size=3 2 2 2 q=['{2, 2, 2}]\n # @ 181: qview_6.c_flow_q : size=4 6 2 2 q=['{6, 2, 2, 2}]\n # @ 188: qview_6.c_flow_q : size=5 2 6 2 q=['{2, 6, 2, 2, 2}]\n # @ 199: qview_6.c_flow_q : size=6 8 2 6 q=['{8, 2, 6, 2, 2, 2}]\n # @ 206: qview_6.c_flow_q : size=7 4 8 2 q=['{4, 8, 2, 6, 2, 2, 2}]\n # @ 214: qview_6.c_flow_q : size=8 2 4 8 q=['{2, 4, 8, 2, 6, 2, 2, 2}]\n # @ 223: qview_6.c_flow_q : size=9 6 2 4 q=['{6, 2, 4, 8, 2, 6, 2, 2, 2}]\n # @ 233: qview_6.c_flow_q : size=8 6 2 4 q=['{6, 2, 4, 8, 2, 6, 2, 2}]\n # @ 235: qview_6.c_flow_q : size=7 6 2 4 q=['{6, 2, 4, 8, 2, 6, 2}]\n # @ 236: qview_6.c_flow_q : size=8 2 6 2 q=['{2, 6, 2, 4, 8, 2, 6, 2}]\n # @ 238: qview_6.c_flow_q : size=7 2 6 2 q=['{2, 6, 2, 4, 8, 2, 6}]\n # @ 240: qview_6.c_flow_q : size=6 2 6 2 q=['{2, 6, 2, 4, 8, 2}]\n # @ 242: qview_6.c_flow_q : size=5 2 6 2 q=['{2, 6, 2, 4, 8}]\n # @ 245: qview_6.c_flow_q : size=4 2 6 2 q=['{2, 6, 2, 4}]\n # @ 248: qview_6.c_flow_q : size=3 2 6 2 q=['{2, 6, 2}]\n # @ 249: qview_6.c_flow_q : size=2 2 6 0 q=['{2, 6}]\n # @ 251: qview_6.c_flow_q : size=1 2 0 0 q=['{2}]\n # @ 254: qview_6.c_flow_q : size=0 0 0 0 q=['{}]\n # @ 317: qview_6.c_flow_q : size=1 7 0 0 q=['{7}]\n # @ 330: qview_6.c_flow_q : size=2 5 7 0 q=['{5, 7}]\n # @ 338: qview_6.c_flow_q : size=3 2 5 7 q=['{2, 5, 7}]\n # @ 345: qview_6.c_flow_q : size=4 1 2 5 q=['{1, 2, 5, 7}]\n # @ 355: qview_6.c_flow_q : size=5 3 1 2 q=['{3, 1, 2, 5, 7}]\n # @ 368: qview_6.c_flow_q : size=6 7 3 1 q=['{7, 3, 1, 2, 5, 7}]\n # @ 372: qview_6.c_flow_q : size=5 7 3 1 q=['{7, 3, 1, 2, 5}]\n # @ 373: qview_6.c_flow_q : size=4 7 3 1 q=['{7, 3, 1, 2}]\n # @ 375: qview_6.c_flow_q : size=3 7 3 1 q=['{7, 3, 1}]\n # @ 377: qview_6.c_flow_q : size=2 7 3 0 q=['{7, 3}]\n # @ 379: qview_6.c_flow_q : size=1 7 0 0 q=['{7}]\n # @ 381: qview_6.c_flow_q : size=0 0 0 0 q=['{}]\n\n<\/pre>\n
And finally, at the end of simulation, I might want a report about the bins<\/p>\n
 50 function<\/strong> void<\/strong> summary(ref<\/strong> T q[$]);\n 51   $display(\"@%t: %s : maxsize=%0d currentsize=%0d q=[%p]\", \n 52     $time, name, maxsize, q.size<\/strong>(), q);\n 53   $display(\"@%t: %s : sizebins=%p\", $time, name, size_bins);\n 54 endfunction\n\n<\/strong><\/pre>\n
 # @ 10000: qview_2.c_flow_q : maxsize=10 currentsize=2 q=['{2, 2}]\n # @ 10000: qview_2.c_flow_q : sizebins='{0:98, 1:181, 2:171, 3:167, 4:152, 5:136, 6:121, 7:89, 8:45, 9:14, 10:1 }\n\n<\/pre>\n
That’s a pretty boring report on bins. How about the best kind of summary or report; a graph. It’s easy to throw the bin results into a Google Doc Spreadsheet and draw a graph.<\/p>\n
\"Bins<\/a>
Bins for Queue Size<\/em><\/strong><\/figcaption><\/figure>\n
Or maybe just put the “Queue Viewer” for the queue “c_flow_q” into the waveform window<\/p>\n
\"Queue<\/a>
Queue Viewer for the c_flow_q variable<\/em><\/strong><\/figcaption><\/figure>\n
Hopefully this note wets your appetite for more kinds of debug. A magic macro – a one line change that provides lots of visibility.<\/p>\n
How do you debug your SystemVerilog queues? What other kinds of information are you interested in?<\/p>\n
Catch me at DVCON 2016 – we can talk debug some more, I’ll be in the Mentor Booth – #501.<\/p>\n","protected":false},"excerpt":{"rendered":"
I want my MTV! And while I’m at it, I’m also curious about what’s going on with my SystemVerilog queues….<\/p>\n","protected":false},"author":71540,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[751],"industry":[],"product":[],"coauthors":[],"class_list":["post-12080","post","type-post","status-publish","format-standard","hentry","category-news","tag-systemverilog"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12080","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/users\/71540"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/comments?post=12080"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12080\/revisions"}],"predecessor-version":[{"id":14486,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/12080\/revisions\/14486"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/media?parent=12080"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/categories?post=12080"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/tags?post=12080"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/industry?post=12080"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/product?post=12080"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/coauthors?post=12080"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}