I agree that it's not a very serious problem. I think I remember my
cubemate at HP trying to get SPARC EIO traces to work in M5 at one point
which is why I'm thinking they do exist, but if we want EIO to be Alpha
only I'm fine with that. Maybe we should put something like the
following in files whi
EIO is Alpha only right now and will almost certainly remain so... not
because you couldn't port it to other ISAs, but if we decided we did
want to have an ISA-independent EIO-like capability we'd almost
certainly develop something else from scratch. The actual EIO code is
really there only for Si
It happens in AlphaLiveProcess. I had the inclination that EIO is only
Alpha capable, I think I saw it on our wiki. Is that inherent or just the
way it is because we just don't have it for something else? I'm not sure
we'll develop eio for non-alpha anyway. But if people object, let me know,
I
Actually not if the EIO process object is generic. Where would this
normally happen for a live process? In a subclass? I'm really surprised
I don't remember... It's been a while :)
Gabe
Gabe Black wrote:
> This might be a reasonable fix for the immediate term, but I don't think
> eio is limited t
This might be a reasonable fix for the immediate term, but I don't think
eio is limited to Alpha. A more appropriate place for this is probably
in the EIO process object constructor.
Gabe
[EMAIL PROTECTED] wrote:
> changeset 2c7b9d01d542 in /z/repo/encumbered
> details: http://repo.m5sim.org/encu
changeset 2c7b9d01d542 in /z/repo/encumbered
details: http://repo.m5sim.org/encumbered?cmd=changeset;node=2c7b9d01d542
summary: fix multicore eio.
diffstat:
0 files changed
diffs (25 lines):
diff -r 25ae7c9393d9 -r 2c7b9d01d542 eio/eio.cc
--- a/eio/eio.ccTue Nov 04 11:40:05 2008 -0500
+