You copied the Doc URL to your clipboard.

Invalidation of dirty lines

Sometimes, one or more dirty lines become invalidated from the cache.

Cause

This can only occur if an invalidate instruction is issued, or a core is reset with dirty lines in the cache.

Reason

A particular operation caused one or more dirty lines to become invalidated from the cache. This is likely to lead to data corruption. Although it is legal for this to occur, because it is sufficiently rare to want to do such a thing, the model issues a warning when this occurs.

Example

<name>: Reset received whilst dirty lines exist in the cache.
  (Both secure and non-secure worlds)
    UD-ns-0000e6803cf64ae0-ish-iHittable-oHittable
    uD-ns-0000e6823ce64bd0-ish-iHittable-oHittable-prefetched
    uD-ns-0000e6803cf64ae8-ish-iHittable-oHittable
    UD- s-0000e6803ce64ac8-nsh-iHittable-oHittable-prefetched
Total : 4
u/UNot-unique/Unique, in terms of ACE terminology.
d/DNot-dirty/Dirty, in terms of ACE terminology.
prefetched/rmon/wmonInternal flags related to the implementation in the model of exclusive monitors.
Was this page helpful? Yes No