EasyManua.ls Logo

AMD AMD5K86 - KEN (External Cache Enable)

AMD AMD5K86
416 pages
Print Icon
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...
AMD~
18524B/O-Marl996
AMD5J!16
Processor
Technical
Reference
Manual
5.2.33
INV (Invalidate
Cache
Line)
Summary
Sampled
Details
Signal
Descriptions
Input
During
an
inquire
cycle,
the
state
of
INV
determines
whether
the
addressed
cache
line,
if
found
in
the
processor's
instruction
or
data
cache,
transitions
to
the
invalid
or
shared
state.
INV
is
sampled
with
the
same
timing
as
EADS.
See
the
descrip-
tion
of
EADS
on
page
5-59.
If
INV
is
asserted
when
EADS
is
asserted
at
the
beginning
of
an
inquire
cycle,
the
processor
transitions
the
line
(if
found)
to
the
invalid
state,
regardless
of
the
state
in
which
the
cache
line
was
found;
such
cycles
are
sometimes
called
invalidate
cycles,
or
simply
invalidations.
If
INV
is
negated
when
EADS
is
asserted,
the
processor
transitions
the
line
(if
found)
to
the
shared
state.
In
either
case,
if
the
line
is
found
in
the
modified
state,
the
processor
writes
it
back
to
memory
before
changing
its
state.
INV
is
typically
asserted
during
a
write
by
another
caching
master.
In
such
cases,
INV
can
be
generated
by
watching
W/R
from
another
bus
master
and
asserting
INV
to
the
processor,
along
with
EADS,
only
on
writes.
This
method
invalidates
a
copy
that
the
processor
may
have
cached,
whether
modified
or
not,
for
the
same
location
being
written
by
the
other
bus
mas-
ter.
The
processor's
assertion
of
III1'M
and/or
HIT
does
not
influence
how
INV
affects
a
line
found
in
the
cache.
Those
two
outputs
simply
indicate
whether
the
line
was
found
(HIT)
and
whether
a
write
back
will follow (III1'M).
If
INV
is
asserted
dur-
ing
the
inquire,
the
resulting
state
of
the
line
(invalid) is
entirely
determined
by
INV,
without
reference
to
III1'M
and/or
HIT.
If
INV
is
negated
during
the
inquire,
the
resulting
state
of
a
hit
line
(shared)
is
also
entirely
determined
by
INV,
but
sys-
tem
logic will
not
know
whether
a
write
back
is
imminent
with-
out
monitoring
III1'M,
and
another
bus
master
will
not
be
able
to
cache
the
line
in
the
exclusive
state
without
monitoring
HIT.
For
a
comparison
of
the
states
that
III1'M,
HIT,
and
INV
can
assume,
see
Table
5-11
on
page
5-73.
5-89

Table of Contents

Related product manuals