RE: [sv-cc] $assertkill vs vpiAssertionKill

Thanks a lot Shalom !!! 
I do not noticed that difference between ..SysKill and ...Skill (I saw only
difference between scope handle and assertion handle )
Once again thanks,
Radek
 
BTW Don't You think that vpiAssertionSysKill should be allowed on assertion
handle to provide the same functionality as $assertkill ?

 
  _____  

From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] 
Sent: Monday, October 13, 2014 7:55 AM
To: Radosław Nawrot; sv-cc@eda.org
Cc: 'Katarzyna Hrynkiewicz'; 'Miłosz Gawryś'; 'Tomasz Skuta'; sv-ac@eda.org
Subject: RE: [sv-cc] $assertkill vs vpiAssertionKill



Hi, Radek.

 

I looked at this and found that there are two different assertion callbacks
(39.4.1, 39.4.2):

 

- cbAssertionSysKill. The assertion system has been temporarily suspended.
While suspended, no assertion attempts are processed, and no
assertion-related callbacks occur. The assertion system can be suspended and
resumed an arbitrary number of times during a single simulation run.

- cbAssertionKill. An attempt is killed (e.g., as a result of a control
action, see 39.5.2).

 

and VPI types (39.5.1, 39.5.2):

 

- vpiAssertionSysKill discards all attempts in progress and disables any
further assertions from being started. This control has no effect on
preexisting assertion callbacks. 

- vpiAssertionKill discards the given attempt, but leaves the assertion
enabled and does not reset any state used by this assertion (e.g., past()
sampling).

 

Per Table 20-8, $assertkill corresponds to cbAssertionSysKill.

 

Regards,

Shalom

 

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Rados?aw
Nawrot
Sent: Friday, October 10, 2014 16:15
To: sv-cc@eda.org
Cc: 'Katarzyna Hrynkiewicz'; 'Miłosz Gawryś'; 'Tomasz Skuta'
Subject: [sv-cc] $assertkill vs vpiAssertionKill

 

Hello,

While reading LRM I've found some context that in my opinion should  be
clarified

39.5.2 Assertion control

..

vpi_control(vpiAssertionKill, assertionHandle, attemptStartTime)

- vpiAssertionKill discards the given attempt, but leaves the assertion
enabled and does not

reset any state used by this assertion (e.g., past() sampling).

 

20.12 Assertion control system tasks

...

$assertkill[(levels[, list])] is equivalent to $assertcontrol(5, 15, 7,
levels [,list])

$assertcontrol:

- Kill: A value of 5 for this argument shall abort execution of any
currently executing attempts for the

specified assertions and then stop the checking of all specified assertions
until a subsequent

$assertcontrol with a control_type of 3 (On).


My question is:
Do $assertkill  task and vpi_control(vpiAssertionKill,..) routine  should
work in the same way?
If yes   - should assertion be on or off after kill?

Regards,

Radek 

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.