AMD AMD5K86 - FLUSH (Cache Flush)

AMD~
1 8524B/O-Mar1996 AMD5~6 Processor Technical Reference Manual
5.2.23 FLUSH (Cache Flush)
Summary
Sampled and
Acknowledged
Details
Signal Descriptions
Input
PLUSH causes the processor to writeback (if necessary) and
invalidate each line in its data and instruction caches. The pro-
cessor generates a fIUsli-acknowledge special bus cycle at the
end of the entire operation. The signal is also used to invoke an
output-float test at RESET.
The processor samples FLuSH every clock and recognizes it at
the next instruction boundary. FLOSH is a falling-edge-trig-
gered interrupt and is latched when sampled. When PLUSH is
recognized, the processor acknowledges it by driving a flush-
acknowledge special bus cycle after all modified lines in the
data cache are written back and after all lines in both caches
are invalidated.
PLUSH is sampled during memory cycles (including cache
writethroughs and writebacks), cache accesses, I/O cycles,
locked cycles, special bus cycles, and interrupt acknowledge
operations in the normal operating modes (Real, Protected,
and Virtual-8086) and in SMM; or in the Shutdown, Halt, or
Stop Grant states; or while AHOLD, BUFF, HLDA, or RESET is
asserted. PLUSH is not sampled in the Stop Clock state, or
while INIT or PRDY is asserted.
If asserted at the falling edge of RESET, FLU SH invokes the
processor's three-state (float) test. System logic can drive the
signal either synchronously or asynchronously (see the data
sheet for synchronously driven setup and hold times).
PLUSH is the third-highest-priority external interrupt. For
details on its relationship to other interrupts and exceptions,
see Section 5.1.3 on page 5-14 and Table 5-3 on page 5-17.
FLUSH allows system logic to control the data that the proces-
sor sees during cache accesses after changing operating modes
or data environments. It also provides control for special cache
coherency purposes. For example, FLUSH may be asserted
when the processor enters SMM or in systems running
extended memory managers if there is any change that may
affect physical addresses. Depending on how an L2 cache
serves the processor and other caching devices, system logic
may want to cause the L2 cache to invalidate its same locations
when system logic asserts PLUSH to the processor, or it may
5-67