Hi Manisha, 2 comments: 1) The on/off should NOT affect currently running (in-flight) assertions. Note that the asserton/off tasks do not, so we need to be consistent + it makes sense to be this way. 2) Appropriate VPI control/callbacks will need to be added as well (clause 28 see the on/off tasks and corresponding VPI for reference) for: - scope control/callbacks (note: no levels in current API ... applies to whole scope, no need to extend this... Too fine grain) [for on/off this is the SysOn/Off callbacks/control] - assertion control/callbacks [for on/off this is the Enable/Disable callbacks/control] Note the handle can be a "vpiCollection" so lists are covered in API. Thx. -Bassam. -- Dr. Bassam Tabbara Synopsys, Inc. (650) 584-1973 -----Original Message----- From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Kulshrestha, Manisha Sent: Tuesday, February 21, 2006 9:25 AM To: sv-ac@eda.org Subject: RE: [sv-ac] Porposal assertion action control tasks Hi All, I am including a proposal for controlling action block execution. Please send your feedback. Do we need another errata on this issue or this proposal can be added to the errata on disable iff (which already has another proposal). Thanks. ManishaReceived on Tue Feb 21 10:15:00 2006
This archive was generated by hypermail 2.1.8 : Tue Feb 21 2006 - 10:15:39 PST