Subject: [sv-cc] Minutes of the SV-CC conf call on 19-Nov-2003
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Wed Nov 19 2003 - 10:08:08 PST
Attendees: (apologies for any mispelled name, we need to update our comittee list soon for cross-checking)
Avinash Mani
Swapnajit Mittra
Bassam Tabbara
Joao Geada
Ghassan Khoory
John Stickley
Francoise Martinole
Doug Warmke
Michael Rohleder
Clint Olsen
Ralph Duncan
Minutes from last F2F meeting: Ralph proposed, Joao accepted
Feedback from last F2F (given by Swapnajit):
- only feedback: proposal to change the name of the VCD I/F to 'data trace' (the name should not be VCD)
- Bassam is concerned about trace, since this does not 100% match the capabilities of the reader I/F
(but might not have the same amount of time to spend for finishing the write I/F )
- Doug thinks the name is O.K.
- Michael believes we could come up with any other name
Technical topics:
Bassam started with the Assertion API:
a) pg. 251
- first issue is that the name of the parameter of the function vpi_register_assertion_cb is not descriptive enough.
It is actually the start time of the attempt, renamed the paramter this way.
Additionally one more parameter has been added to show the reason for the attempt
b) pg. 252
Added a pointer to the callback and changed the descriptive text accordingly, also changed event to the more
descriptive attempt time
c) pg. 253
- last argument called attempt is again not descriptive enough (see a))
Joao continued with the errata on the coverage time
- renamed ...QUERY to ...CHECK
- changed the descriptive text to better show the permitted return values and their meaning
Michael: wants to see the information that this is the complete possible; Joao will update the document
Michael: Reason for renaming QUERY to CHECK; Joao this has been done earlier
- mapped the same language to describe the name parameter (no longer mention 'file names', but logical name)
Francoise: could we say location name ?
Joao: no, where the information ends up is defined by the tool, so this is not the location...
- cmView was a remainder of the original Synopsys donation,
remove the name of this Synopsys tool to be tool inspecific
- refined the meaning of vpiCovered to be
- Bassam even proposed an even better errata, saying ""
Michael: have we checked whether it is possible to query all possible combinations
Michael: is it possible to have a set of examples for each possible case, and what is the return value to be expected for it
Francoise: what are the possible return values; Joao enumerated them ...
Joao: any objection for including Bassam's proposal; -- nobody had any objection against this --
Joao will send an update with all requested modifications (Bassams improved proposal + the two requested clarifications done by
Michael)
Joao & Francoise are concerned about the last review, especially since cmView slipped through the fingers. Need a new review again.
Bassam reviewed the modified Data trace (formerly VCD) donation
- result of feedback from the F2F meeting
- concentrated on reader API, since this seems to be the more important part of the donation
Francoise: writer interface is primary used by foreign code/models
Bassam: No, mostly used by 3rd party vendors to write information into the Novas DB
Michael: Could you comment on the type of data mostly written by them
Bassam: mostly additional annotations to data (e.g. strings, e.g. names)
- load list renamed to load collection
Francoise: collection concept in VHPI is to group data
Bassam: I used this concept
- traverse value stream object -> collection of traverse object
Francoise: object model diagrams are now messed up
Bassam: rely on Francoise to help him to draw this thing correctly
Doug: is concerned about the overhead for setting up a collection; believes the overhead could be really high.
. Concern is caused by examples.
Bassam: For any traverse object you could now return a traverse object collection.
Doug: Could be ambigous, if it returns local change object or some global objects
. The problem is when forming the collection.
. Is it possible to show an example how to invoke $dumpvars without any arguments ? ...
(some longer discussions about the examples in the donation ...)
Francoise: there should be an automatic call to create a collection that creates all related information in one call,
just provide the scope handle and then it should provide the complete collection.
Bassam: Yes, that would be a useful addition
Swapnajit: Is 'jump function' already covered by vpi_control; Bassam: Yes
Francoise: Traverse just gives a value at a time, you could not get a set of values, one for each load object at a time.
. this would provide a much higher performance
. would like to understand the use case for this API
Bassam: Yes, this could be a useful addition
Michael: Has some different experiences from former work at OMI
Joao: believe the key problem is how to get this information, not how to transfer it
Swapnajit requested a new revision including the following
(example of $dumpvars,object model diagram, how to create a collection)
--NOTE: The content of this message may contain personal views which are not neccessarily the views of Motorola, unless specifically stated.
___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Software Technologist Fax: +49-89-92103-680 |( \ / / | Motorola, Semiconductor Products, System Design | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@motorola.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \
The information contained in this email has been classified as: Motorola General Business Information (x) Motorola Internal Use Only ( ) Motorola Confidential Proprietary ( )
*** This note may contain Motorola Confidential Proprietary or Motorola Internal Use Only Information and is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you! ***
This archive was generated by hypermail 2b28 : Wed Nov 19 2003 - 10:12:31 PST