Alon Flaisher Alon Gluska Eli Singerman Intel Corporation

Slides:



Advertisements
Similar presentations
Using Formal Verification to Replace Mainstream Simulation Erik Seligman Intel Brandon Smith Intel
Advertisements

1 System Level Verification of OCP-IP based SoCs using OCP-IP eVC Himanshu Rawal eInfochips, Inc.,4655 Old Ironsides Drive, Suite 385,Santa Clara, CA
April 30, A New Tool for Designer-Level Verification: From Concept to Reality April 30, 2014 Ziv Nevo IBM Haifa Research Lab.
Acceptance Testing.
Putting It All Together: Using Formal Verification In Real Life Erik Seligman CS 510, Lecture 19, March 2009.
Abstraction and Modular Reasoning for the Verification of Software Corina Pasareanu NASA Ames Research Center.
Testing and Quality Assurance
Xiushan Feng* ASIC Verification Nvidia Corporation Automatic Verification of Dependency 1 TM Jayanta Bhadra
INCREASED PRODUCTIVITY FOR ASSERTION-BASED VERIFICATION (ABV) INCREASED PRODUCTIVITY FOR ASSERTION-BASED VERIFICATION (ABV) DESIGNED FROM THE GROUND UP.
The Secrets of Practical Verification… © 2008 Think Verification.
Chapter 4 Quality Assurance in Context
Taking a Waterfall Project Agile REF: Paul Geberth GCSS-J Project Manager Establishment of an Agile Project.
Ensuring Robustness via Early- Stage Formal Verification Multicore Power Management: Anita Lungu *, Pradip Bose **, Daniel Sorin *, Steven German **, Geert.
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
6/14/991 Symbolic verification of systems with state machines David L. Dill Jeffrey Su Jens Skakkebaek Computer System Laboratory Stanford University.
Alternate Software Development Methodologies
MS-SoC Best Practices – Advanced Modeling & Verification Techniques for first-pass success By Neyaz Khan Greg Glennon Dan Romaine.
1 Speed, Drunkenness, and the Wall Does High Level Design/ESL Make Sense? Kris Konigsfeld Sr. Principal Engineer Oregon CPU Architecture Intel Corporation.
Leveraging Assertion Based Verification by using Magellan Michal Cayzer.
Reliability Centered Maintenance From a Data Center Perspective March 2013.
The Future of Formal: Academic, IC, EDA, and Software Perspectives Ziyad Hanna VP of Research and Chief Architect Jasper Design Automation Ziyad Hanna.
Testing: Who 3, What 4, Why 1, When 2, How 5 Lian Yu, Peking U. Michal Young, U. Oregon.
ECE Synthesis & Verification1 ECE 667 Spring 2011 Synthesis and Verification of Digital Systems Verification Introduction.
DSI Division of Integrated Systems Design Functional Verification Environments Development Goals Our main goals are in the field of developing modular.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Formal verification Marco A. Peña Universitat Politècnica de Catalunya.
Formal Techniques for Verification Using SystemC By Nasir Mahmood.
Complete and Integrated Lifecycle Management. Challenges 1.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Streamline Verification Process with Formal Property Verification to Meet Highly Compressed Design Cycle Prosenjit Chatterjee, nVIDIA Corporation.
CENTRE FOR FORMAL DESIGN AND VERIFICATION OF SOFTWARE
1 Debugging and Testing Overview Defensive Programming The goal is to prevent failures Debugging The goal is to find cause of failures and fix it Testing.
Presenter : Ching-Hua Huang 2013/7/15 A Unified Methodology for Pre-Silicon Verification and Post-Silicon Validation Citation : 15 Adir, A., Copty, S.
Proof Carrying Code Zhiwei Lin. Outline Proof-Carrying Code The Design and Implementation of a Certifying Compiler A Proof – Carrying Code Architecture.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
The First in GPON Verification Classic Mistakes Verification Leadership Seminar Racheli Ganot FlexLight Networks.
1 Hybrid-Formal Coverage Convergence Dan Benua Synopsys Verification Group January 18, 2010.
Unit Testing 101 Black Box v. White Box. Definition of V&V Verification - is the product correct Validation - is it the correct product.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
- 1 - ©2009 Jasper Design Automation ©2009 Jasper Design Automation JasperGold for Targeted ROI JasperGold solutions portfolio delivers competitive.
February 22-25, 2010 Designers Work Less with Quality Formal Equivalence Checking by Orly Cohen, Moran Gordon, Michael Lifshits, Alexander Nadel, and Vadim.
Verification of Behavioral Consistency in C by Using Symbolic Simulation and Program Slicer Takeshi Matsumoto Thanyapat Sakunkonchak Hiroshi Saito Masahiro.
Introduction to Hardware Verification ECE 598 SV Prof. Shobha Vasudevan.
Winter 2007SEG2101 Chapter 121 Chapter 12 Verification and Validation.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Problem: design complexity advances in a pace that far exceeds the pace in which verification technology advances. More accurately: (verification complexity)
Softheme Service Model Software Outsourcing Solutions.
Cookie-cutter properties to assist non Formal experts Bin Xue.
Practical Methods in Coverage- Oriented Verification of the Merom Microprocessor Alon Gluska.
42 nd DAC, June 16, 2005 Formal Verification – Is It Real Enough? Yaron Wolfsthal Haifa Research Lab Rebecca Gott Systems and Technology Group.
Unit Microprocessor.
Agile Project Management
Progile Automated Verification Engineer • PAVE •
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Engineering (CSI 321)
Architecture & System Performance
Architecture & System Performance
Mobile Application Test Case Automation
Programming Problem steps must be able to be fully & unambiguously described Problem types; Can be clearly described Cannot be clearly described (e.g.
Speaker’s Name, SAP Month 00, 2017
Software Independent Verification and Validation (IV&V)
Software Processes.
Aspect Validation: Connecting Aspects and Formal Methods
M Achutha KiranKumar V Bindumadhava S S Abhijith A Bharadwaj
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Formal Verification of Partial Good Self-Test Fencing Structures
Baisc Of Software Testing
Test Process “V” Diagram
by Neyaz Khan Senior PMTS Maxim Integrated Products
Presentation transcript:

Case study: Integrating FV and DV in the Verification of Intel® Core™2 Duo Microprocessor Alon Flaisher Alon Gluska Eli Singerman Intel Corporation Israel Design Center

Presentation Goals Share how the integration of FV with dynamic verification improved the productivity & quality of Merom verification Highlight some of the barriers in effective deployment of FV Update how FV is used in today’s CPU designs and what are the future challenges A. Flaisher

Outline Challenges Applying FV in Merom Our FV/DV synergy approach Examples Looking forward A. Flaisher

Challenges in Applying FV in Merom Allocate resources for FV Replace traditional dynamic verification (DV) activities Choose the best designs to FV Quickly establish new FV environments A. Flaisher

Our Approach – FV/DV Integration Replaced DV activities For each DUT decided what would be the effect on DV 75% of the proofs replaced DV activities, mainly coverage Enabled allocating resources for FV FV was also applied by VE (non FV experts) Familiar with the design, owned both activities Compared the complexity of the design vs. the proof Provided more flexibility in assigning engineers to FV FVE established FV environments for VE Better utilized expertise Joint decision where to apply FV Joint test plans and checking A. Flaisher

Example 1: ALU Cluster Independent execution units FV done in 2nd half of the project Cluster level FV using symbolic simulation (STE/FL) FVE built a Cluster Formal Environment Active unit driven symbolically Remaining units driven with X’s The unit owner (VE) coded the spec/checkers for each micro- instruction in FL Thousands of micro-instructions Some are very simple to code, once you know the spec A. Flaisher

Example 1: ALU Cluster (Cont.) FV/DV approach provided much higher verification quality for comparable investment! Higher quality verification 98% of the micro-instructions fully verified! Unit dependencies also verified Zero bugs found in silicon Reduction of effort Done instead of coverage (which requires huge investment) Good utilization of expertise FVers built the CFE and carried out highly complex proofs DVers wrote most specs A. Flaisher

Example 2: MS Unit The MS unit Unit was completely FV by an expert VE Translates instructions to uop sequences Needs to support all combination of uops and events (any ROM) Unit was completely FV by an expert VE MS team chose FV as the main verification tool Used BMC on unit boundaries 1400 vars, bound 40 Reference model for checking Control ROM Decoders uip IA instruction uops MS Unit Clears A. Flaisher

Example 2: MS Unit (Cont.) FV/DV provided much higher quality for less effort! FV found corner case bugs impractical for simulation Prevented bugs from being released Replaced most DV activities Enabled by the MS validation team Control ROM Decoders uip IA instruction uops MS Unit Clears A. Flaisher

Looking Forward FV integration to mainstream verification continues to grow in current CPU designs More FV resources in Sandy Bridge (Intel’s 2010 TOC) Good acceptance throughout the project Single spec language for RTL assertions and FV (SVA) Aggressive ABV methodology improves assertion FV ROI Sharing (unit level) checkers through SV reference-models A. Flaisher

Looking Forward (Cont.) Good results from applying FV for bug-hunting Integrate FV for bug hunting in early stages Integrate FV to get highest confidence in later stages Key capabilities are still missing Sharing FV/DV environments Unit level capacity Solutions for system level properties Predictability and complexity analysis … A. Flaisher

Q&A