From: ralf@uni-koblenz.de
To: Ulf Carlsson <grim@zigzegv.ml.org>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: cdrom
Date: Wed, 9 Sep 1998 14:42:40 +0200 [thread overview]
Message-ID: <19980909144240.E1340@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.96.980902174807.334B-100000@calypso.saturn>; from Ulf Carlsson on Wed, Sep 02, 1998 at 05:58:15PM +0200
On Wed, Sep 02, 1998 at 05:58:15PM +0200, Ulf Carlsson wrote:
> On Wed, 2 Sep 1998 ralf@uni-koblenz.de wrote:
>
> > As I recently told you on IRC - the patch as you've posted it is not
> > correct. It will misstreat VCEI exceptions.
>
> My idea is based on that we write the wrong cache line back, and that's
> why we receive the invalid instruction errors.
>
> Maybe this is foolish, but anyway: If we have data from main memory cached
> in the secondary cache and then overwrite that data line in main memory
> with an instruction line and cache the instruction. We receive a VCEI when
> we try to access the cached line, and our handler writes the data back
> instead of the intstruction and causes the invalid instructions. Well,
> this is the only idea I have at the moment.
Note that we don't have to care about if the line contains data or
instructions. All we know is that the l2 line corrosponding to the
instruction which threw the vcei exception is in some state other than
invalid. We cannot accidently writeback an instruction line to memory
because the Hit_Writeback_Inv_SD cacheop we're using will only write
dirty lines back.
Ralf
next prev parent reply other threads:[~1998-09-09 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-31 16:56 cdrom Ulf Carlsson
1998-08-31 22:19 ` cdrom Thomas Bogendoerfer
1998-08-31 23:26 ` cdrom ralf
1998-09-01 14:55 ` cdrom ralf
1998-09-01 17:50 ` cdrom Ulf Carlsson
1998-09-01 18:05 ` cdrom Alex deVries
1998-09-01 22:08 ` cdrom ralf
1998-09-02 15:58 ` cdrom Ulf Carlsson
1998-09-09 12:42 ` ralf [this message]
1998-09-01 19:19 ` cdrom Alex deVries
1998-09-01 21:56 ` cdrom ralf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19980909144240.E1340@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=grim@zigzegv.ml.org \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox