x86: Switch from MessageReq and Resp to WriteReq and Resp.
authorGabe Black <gabeblack@google.com>
Wed, 11 Sep 2019 20:45:24 +0000 (13:45 -0700)
committerGabe Black <gabeblack@google.com>
Wed, 2 Oct 2019 01:28:32 +0000 (01:28 +0000)
commitf89f85d255e2192fa2aab5dd168eb9372c41d09c
treea6171c32b16ea29870035f6062b4abbae5e8d017
parent5fdaa0d719cb1d2c6847ff1ee69fa54ceae55172
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>
src/arch/x86/interrupts.cc
src/arch/x86/intmessage.hh
src/dev/x86/intdev.hh