UVM: Some Thoughts Before DVCon
It is time to talk about what happens next with UVM
The Design and Verification Conference (DVCon) has become the premier event to discuss front-end design issues with an emphasis on verification. If one listens to the Conversation Central interview of DVCon leadership it is clear how singularly important DVCon is. As one of the three organizers of the UVM Tutorial on Monday, I know the conference organizers had to rearrange the room layout to accommodate a greater than expected number of registrant. It is clear how important the topic of verification is and UVM in particular has become.
It seems to me that DVCon is the right place to discuss what comes next with UVM. I have three thoughts about UVM that I think merit discussion.
1. UVM needs a period of stability
While the experts at the Accellera Verification IP Technical Subcommittee (VIP-TSC) standardization table (all good people) continue to hone UVM and debate a few more features they need, they have been unable to make significant progress on those features since last DVCon. The one major item promised beyond OVM, an update to phasing, remains an open topic. Mentor has suggested in committee that we allow another year to pass and suspend committee action on this. Maybe the natural market forces would allow several options to surface, be user-tested and then merit consideration by the VIP-TSC.
This is in keeping with Karen Bartleson’s 9th Commandment for Effective Standards: “Start with Donations; Not From Scratch.” This is what is happening now with Phasing. The design by committee process is moving slowly. It is not the slow part that concerns me, however.
Completing the “last” thing has many in the verification community waiting until it is done before they migrate and adopt UVM. The best thing the committee could do to encourage use is to give the users certainty that UVM will not change in the next 12 months. At the same time, the committee could commit to take input from users at the end of those 12 months as a guide to what it does next.
2. UVM needs a simple path to first use
Accellera has an approved and published standard, an open-source implementation and embedded UVM User’s Guide. This is a lot to digest. And while one may expect the User’s Guide to help, it calls the reader to supplement it with “education, experience and professional judgment.” It warns that “not all aspects of this guide may be applicable in all circumstances.”
Users should be offered an unambiguous, easy-to-use and understand means to adopt UVM without having to know everything about it before starting to use it. UVM was not made for just those who have large verification teams and central CAD groups. Those large teams are the ones who are already using UVM. The first step to UVM adoption for the rest of the world should not be too high as it currently is.
UVM needs a simple path for fast adoption.
3. UVM needs to bridge the system domain
Accellera System Initiative has come to life from the unification of Accellera and OSCI. While the vision to bring the two organizations together is without fault, the lack of a publicly visible plan to leverage each others strengths is noted by Gabe Moretti in his recent blog on DVCon when he wrote: “First we build it and then we figure out how to use it has never been a good architectural approach, especially in electronics.” His comment was in response to the questions to be asked at DVCon’s Monday lunch about what the new organization should look like. Gabe certainly thought “the creators of the organization must have some ideas of the focus, mission and goals.”
I certainly do. In the case of UVM, I think it needs a bridge between the SystemVerilog world in which it was written and the SystemC world of design and modeling. As teams move to higher levels of abstraction for system-level architectural exploration and definition, the need for efficient and reusable functional models has become an imperative.
It is no secret to the Accellera VIP-TSC that Mentor Graphics thinks this is needed. Our presentation to committee members on a UVM API to facilitate this outlines exactly what we think should be done to address reusable functional models in the system world. [Accellera requires registration to download the Mentor presentation. Accellera members can register here. Guests require VIP-TSC leadership permission and can request it here.]
UVM must grow and bridge the system world. The Accellera SystemC Verification Working Group (VWG) knows this. They have a meeting planned at the DATE conference to discuss future evolutions related to SystemC and Verification on 14 March 2012 from 1230-1340 in Conference Room 4 which I plan to attend. The VWG meeting is open to external participants, not just Accellera members.
I don’t know what your thoughts about what should happen next with UVM are. Feel free to share them here if you wish or join me at DVCon or DATE and we can discuss it with the whole community. Maybe there is hope we can make progress on these three areas in the coming year.
Posted February 17th, 2012, by Dennis Brophy
- Evolving Product Lifecycle Requires New Debugging Skills
- Portable Stimulus Specification Released for Public Review
- Reusing Existing Descriptions with New Languages
- DAC 54 Spotlight on “Portable Stimulus”
- Going With The Flow – Overview
- DVCon China: Formal Technology Is Set for Growth in Asia
- Design & Verification IP Forum 2017
- Portable Stimulus: Standard vs. Tool vs. Language
- Portable Stimulus the Hot Topic at DVCon U.S. ’17
- The Walking LRM