Requirements for the Next Version of SCE-API. 2 5/14/2015 11:32 PM Overview l Basic Requirements meet SCE-MI 1.0 requirements backwards compatibility.

Slides:



Advertisements
Similar presentations
1CADENCE DESIGN SYSTEMS, INC. SCE-MI 2.0, Cadence Summary (Accellera ITC Meeting) Feb 17, 2005.
Advertisements

1 Microsoft Access 2002 Tutorial 9 – Automating Tasks With Macros.
A Breakthrough Common Emulation API 15th November 2001 SCE-API.
OPERATING SYSTEMS Threads
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 4: Multithreaded Programming.
Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8 th Edition Chapter 4: Threads.
Threads.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 5: Threads Overview Multithreading Models Threading Issues Pthreads Solaris.
Review of “Embedded Software” by E.A. Lee Katherine Barrow Vladimir Jakobac.
1 SWE Introduction to Software Engineering Lecture 5.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 3: Processes.
Creating Test Environments HDL Model HDL Testbench Simulation Engine API stimulus check Testbench Program stimulus check Non-HDL languages may be used.
4.7.1 Thread Signal Delivery Two types of signals –Synchronous: Occur as a direct result of program execution Should be delivered to currently executing.
Chapter 4: Threads READ 4.1 & 4.2 NOT RESPONSIBLE FOR 4.3 &
Chapter 4: Threads. 4.2 Silberschatz, Galvin and Gagne ©2005 Operating System Concepts Chapter 4: Threads Overview Multithreading Models Threading Issues.
Design Synopsys System Verilog API Donations to Accellera João Geada.
1 MPI-2 and Threads. 2 What are Threads? l Executing program (process) is defined by »Address space »Program Counter l Threads are multiple program counters.
What is Concurrent Programming? Maram Bani Younes.
Ryan McAlister CONNECTORS. Introduction Integration and interaction As important as developing functionality More challenging decisions Transfer control.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 4: Threads.
1 Lecture 4: Threads Operating System Fall Contents Overview: Processes & Threads Benefits of Threads Thread State and Operations User Thread.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Lecture 4 Operating Systems.
Chapter 4: Threads. 4.2 Chapter 4: Threads Overview Multithreading Models Threading Issues Pthreads Windows XP Threads Linux Threads Java Threads.
14.1 Silberschatz, Galvin and Gagne ©2009 Operating System Concepts with Java – 8 th Edition Chapter 4: Threads.
ICOM 5995: Performance Instrumentation and Visualization for High Performance Computer Systems Lecture 7 October 16, 2002 Nayda G. Santiago.
An Introduction to Software Architecture
1CADENCE DESIGN SYSTEMS, INC. Cadence Proposed Transaction Level Interface Enhancements for SCE-MI SEPTEMBER 11, 2003.
Web Services Glossary Summary of Holger Lausen
System Verilog Testbench Language David W. Smith Synopsys Scientist
Interfaces to External EDA Tools Debussy Denali SWIFT™ Course 12.
CIS 540 Principles of Embedded Computation Spring Instructor: Rajeev Alur
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
CS333 Intro to Operating Systems Jonathan Walpole.
Infrastructure design & implementation of MIPS processors for students lab based on Bluespec HDL Students: Danny Hofshi, Shai Shachrur Supervisor: Mony.
A Design and Verification Company Zaiq’s Transaction API Proposal v2.
SCE-MI Meeting 1 San Jose’, 14 th Nov Author: Andrea Castelnuovo SCE-MI Integrating Emulation in a system level design methodology San Jose’, 14/11/2003.
Discussion of ITC Goals. Historical Goals From SCE-API Marketing presentation Circa 2001.
Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 5: Threads Overview Multithreading Models Threading Issues Pthreads Solaris.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition Chapter 4: Threads Modified from the slides of the text book. TY, Sept 2010.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 4: Threads.
Way beyond fast © 2002 Axis Systems, Inc. CONFIDENTIAL Axis Common Transaction Interface (CTI) Architecture Highlights 9/11/2003 Ching-Ping Chou Axis Systems,
Discussion of ITC Goals. Historical Goals From SCE-API Marketing presentation Circa 2001.
Source Level Debugging of Parallel Programs Roland Wismüller LRR-TUM, TU München Germany.
CIS 540 Principles of Embedded Computation Spring Instructor: Rajeev Alur
Discussion of ITC Goals. Historical Goals From SCE-API Marketing presentation Circa 2001.
DPI+ Proposals John Stickley, Duaine Pryor Mentor Emulation Division.
Chapter 4: Threads 羅習五. Chapter 4: Threads Motivation and Overview Multithreading Models Threading Issues Examples – Pthreads – Windows XP Threads – Linux.
Silberschatz, Galvin and Gagne ©2009Operating System Concepts – 8 th Edition Chapter 4: Threads.
OPERATING SYSTEM CONCEPT AND PRACTISE
Chapter 4: Threads.
Coupling and Cohesion 1.
CS399 New Beginnings Jonathan Walpole.
Chapter 5: Threads Overview Multithreading Models Threading Issues
Operating System (013022) Dr. H. Iwidat
CS533 Concepts of Operating Systems
Chapter 4: Threads 羅習五.
Threads CSSE 332 Operating Systems Rose-Hulman Institute of Technology
Chapter 4: Threads.
Chapter 4: Threads.
Chapter 4: Threads.
What is Concurrent Programming?
An Introduction to Software Architecture
Chapter 4: Threads.
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
What is Concurrent Programming?
Chapter 4: Threads.
Chapter 4: Threads.
Chapter 4: Threads.
Presentation transcript:

Requirements for the Next Version of SCE-API

2 5/14/ :32 PM Overview l Basic Requirements meet SCE-MI 1.0 requirements backwards compatibility l Extracted Requirements zaiq mentor cadence axis l Ease of Modeling Requirements l Control and Debug Requirements

3 5/14/ :32 PM Satisfy SCE-MI 1.0 requirements l Performance in emulation and simulation implies a transaction based interface implies loose coupling of HDL engine and HVL engine. l support for multiple HDL execution engine types emulation simulation cycle event l support for multiple truly independent channels for reuse l support for multiple HVL test bench environments support for arbitrary threading systems in native mode. support for a single threaded model. semantics can be syntactically bound into arbitrary HVLs. l Automated infrastructure generation l Support synchronization of asynchronous message passing l Support zero-time-sequential-operations

4 5/14/ :32 PM Backwards Compatibility to SCE-MI 1.0 l SCE-MI 1.0 models must work in the new environment. l New and old models must coexist without penalty.

5 5/14/ :32 PM Relation to Other Accelera Standards l SystemVerilog also defines an HDL-C interface called DPI. Based on foreign function calls C-Calls-HDL (function export) HDL-Calls-C (function import) Proposed DPI task import / export could provide the necessary performance. There is some desire in Accelera to rationalize ITC and SV- CC work. l PLI, VHPI, VPI... no requirement for PLI support because it conflicts with the performance requirement.

6 5/14/ :32 PM Relationship to non-Accelera Standards l Emerging System C TLM standard l Current System C channels Is a C++ to C++ interface. Ideas could be borrowed.

7 5/14/ :32 PM Coexistence With Thread Systems l Transaction interface must coexist with application defined threading systems System C / SCV Verisity Verilog / System Verilog VHDL Vera POSIX p_threads quickthreads CoWare customer written custom environments l Customers will drive choice of thread system.

8 5/14/ :32 PM Extracted Requirements

9 5/14/ :32 PM Extracted Requirements (Zaiq) l General Goals Many SCE-MI 1.0 Requirements simulation and emulation support threading on the non-HVL side. multiple HVL support. Transaction level modeling Ease simulation to emulation transition. Ease and standardize construction of BFM / Transactors standardize control so complete tests work unchanged. l Specific support variable size transactions eliminate uncontrolled clock through encapsulation / abstraction. l Approach to Satisfy Requirements Define a transactor application layer built on top of SCE-MI to standardize transactor functionality. add a single standardized threading system. add control and debug functions.

10 5/14/ :32 PM Extracted Requirements (Mentor) l General Goals Satisfy SCE-MI 1.0 requirements Strong backwards compatibility with SCE-MI 1.0 improve ease of modeling for the HDL designer. Make better use of multithreaded systems on the HVL side. Coexist and support standard definitions of transactor functionality at the application layer. l Specific eliminate uncontrolled clock continue to support zero time sequential operations. support synchronization on message arrival. enforce repeatability l Approach build on top of SCE-MI add more abstract transaction layer, encapsulating clock control. make HDL interface more acceptable to HDL designers make use of user specified thread systems

11 5/14/ :32 PM Extracted Requirements (Cadence) l General Goals Many SCE-MI 1.0 Requirements simulation and emulation, cycle and event based engines support threading on the non-HVL side. multiple HVL support. Transaction level modeling create standard structure for construction of BFM / Transactors l Specific support variable size transactions eliminate uncontrolled clock l Approach to Satisfy Requirements use SCE-MI 1.0 as transport layer remain with macro based message passing paradigm, but replace macros. Force all transactors to conform to certain rules (standard definition of transaction) Remove automation around macros? Remove clock generation as well as clock control? Do not add control features

12 5/14/ :32 PM Extracted Requirements (Axis) l General Goals Many SCE-MI 1.0 Requirements simulation and emulation, cycle and event based engines support threading on the non-HVL side. multiple HVL support. Transaction level modeling standardize control so complete tests work unchanged. l Specific support variable size transactions eliminate uncontrolled clock optional application layer to separate instruction and data channels? l Approach to Satisfy Requirements replace entire SCE-MI with transport API based xbVC terminals remain with macro based (structural) message passing paradigm, but replace macros with different ones. create application layer based on separate paired instruction and data channels and memory controller. Force all transactors to conform to certain rules (standard definition of transaction) in particular, force separate instruction and data channels and specific instructions. Force a single standardized threading system. Add control features. Add many miscellaneous features

13 5/14/ :32 PM Loosely Coupled Activity Areas l Basic transaction level modeling interface l Application layer for standard transaction functions. l Control and debug l Interaction with application layer thread systems