From: Yonghao Chen (firstname.lastname@example.org)
Date: Thu May 05 2005 - 06:28:32 PDT
It can be argured either way. If it turns dormant upon the fisrt time check event within the limit, it will be consistent with timer based mode, but then it will be not with the pure event based check $skew, as the LRM suggests. For timer based mode, turning dormant upon the tcheck event within the limit makes sense, otherwise you will ALWAYS get a violation as limit expires, and that can become unwanted. On the other hand, for event based mode, the check will issue violation only when tcheck event is detected, so there is no potentially undesired beihavior as in timer based mode.
> $timeskew in event-based mode where remain_active_flag = 0 :
> Does it turn dormant after first timecheck event or after first violation?
> The difference is where two timecheck events occur, one before the
> time limit and one after the time limit.
> Currently, LRM says it turns dormant after the first violation.
> Shalom.Bresticker @freescale.com Tel: +972 9 9522268
> Freescale Semiconductor Israel, Ltd. Fax: +972 9 9522890
> POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 5441478
> [ ]Freescale Internal Use Only [ ]Freescale Confidential Proprietary
This archive was generated by hypermail 2.1.4
: Thu May 05 2005 - 06:04:12 PDT
sponsored by Boyd Technology, Inc.