summaryrefslogtreecommitdiff
path: root/src/dev
diff options
context:
space:
mode:
authorGabe Black <gabeblack@google.com>2019-09-11 13:45:24 -0700
committerGabe Black <gabeblack@google.com>2019-10-02 01:28:32 +0000
commitf89f85d255e2192fa2aab5dd168eb9372c41d09c (patch)
treea6171c32b16ea29870035f6062b4abbae5e8d017 /src/dev
parent5fdaa0d719cb1d2c6847ff1ee69fa54ceae55172 (diff)
downloadgem5-f89f85d255e2192fa2aab5dd168eb9372c41d09c.tar.xz
x86: Switch from MessageReq and Resp to WriteReq and Resp.
Originally MessageReq was intended to mark a packet as a holding a message destined for a particular recipient and which would not interact with other packets. This is similar to the way a WriteReq would behave if writing to a device register which needs to be updated atomically. Also, while the memory system *could* recognize a MessageReq and know that it didn't need to interact with other packets, that was never implemented. Change-Id: Ie54301d1d8820e206d6bae96e200ae8c71d2d784 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/20823 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Jason Lowe-Power <jason@lowepower.com>
Diffstat (limited to 'src/dev')
-rw-r--r--src/dev/x86/intdev.hh2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/dev/x86/intdev.hh b/src/dev/x86/intdev.hh
index f71c9ff9d..348ec57b8 100644
--- a/src/dev/x86/intdev.hh
+++ b/src/dev/x86/intdev.hh
@@ -76,7 +76,7 @@ class IntSlavePort : public SimpleTimingPort
Tick
recvAtomic(PacketPtr pkt)
{
- panic_if(pkt->cmd != MemCmd::MessageReq,
+ panic_if(pkt->cmd != MemCmd::WriteReq,
"%s received unexpected command %s from %s.\n",
name(), pkt->cmd.toString(), getPeer());
pkt->headerDelay = pkt->payloadDelay = 0;