EasyManua.ls Logo

AMD K5

AMD K5
406 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
5-66 Bus Interface
AMD-K5 Processor Technical Reference Manual 18524C/0Nov1996
use the Flush-Acknowledge special bus cycle to initiate such
action.
Entry into SMM may require the assertion of FLUSH. If the
SMM physical memory space overlaps physical main memory
that is cacheable, FLUSH must be asserted with SMI (the
FLUSH will be performed first, because it is a higher-priority
interrupt). If this is not done, accesses to the SMM memory
space after entering SMM may hit cached locations in the main
memory space. In addition, if SMM memory is itself cacheable,
the SMM service routine should execute the WBINVD (write-
back and invalidate) instruction when leaving SMM, just prior
to executing the RSM instruction.
The processor performs the FLUSH operation using the same
microcode that executes for the WBINVD (writeback and inval-
idate) instruction. The only difference is the special bus cycle
driven upon completion of the operation. A writeback and
invalidation operation can be time consuming because all mod-
ified lines in the data cache are written back to memory. If
writebacks are not required, the INVD instruction or RESET
can be used to invalidate all contents of the caches.
When FLUSH is recognized at an instruction boundary, the
processor performs the following actions in the order shown:
1. Flush PipelineThe processor invalidates all instructions
remaining in the pipeline.
2. Writeback and InvalidateThe processor writes back any
modified lines in the data cache, and then (after all write-
backs) simultaneously invalidates all lines in the instruc-
tion and data caches. The invalidations are done by clearing
the valid bits in both the linear and physical tag directories.
3. AcknowledgeAfter the writeback and invalidation com-
pletes, the processor drives a FLUSH-acknowledge special
bus cycle. This cycle is identified by D/C = 0, M/IO = 0, W/R
= 1, BE7–BE0 = EFh and A31–A3 = 0. System logic must
return BRDY in response to this cycle.
AHOLD, BOFF, and HOLD are all recognized and behave nor-
mally while FLUSH is asserted, and they will intervene in an
in-progress FLUSH operation. For example, if BOFF is
asserted while a FLUSH operation is writing modified lines
back to memory, an in-progress writeback will be aborted.

Table of Contents

Related product manuals