mem: Refactor port proxies to support secure accesses
authorAndreas Sandberg <andreas.sandberg@arm.com>
Tue, 13 Feb 2018 18:00:22 +0000 (18:00 +0000)
committerAndreas Sandberg <andreas.sandberg@arm.com>
Mon, 19 Feb 2018 14:24:46 +0000 (14:24 +0000)
commit7b96fc2456d71d0df2700384ab44c1ed01be2f03
tree912d232864b064dfd0f4d924b56e178a0c2d0dfe
parent6039da55d87fb27b149ac3da0ebce41bb55a3bee
mem: Refactor port proxies to support secure accesses

The current physical port proxy doesn't know how to tag memory
accesses as secure. Refactor the class slightly to create a set of
methods (readBlobPhys, writeBlobPhys, memsetBlobPhys) that always
access physical memory and take a set of Request::Flags as an
argument. The new port proxy, SecurePortProxy, uses this interface to
issue secure physical accesses.

Change-Id: I8232a4b35025be04ec8f91a00f0580266bacb338
Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com>
Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/8364
Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com>
src/mem/fs_translating_port_proxy.cc
src/mem/fs_translating_port_proxy.hh
src/mem/port_proxy.cc
src/mem/port_proxy.hh
src/mem/se_translating_port_proxy.cc
src/mem/se_translating_port_proxy.hh