arch-arm: Handle empty object_file scenario in ArmFsWorkload
authorGiacomo Travaglini <giacomo.travaglini@arm.com>
Wed, 1 Apr 2020 16:19:49 +0000 (17:19 +0100)
committerGiacomo Travaglini <giacomo.travaglini@arm.com>
Tue, 14 Apr 2020 08:51:24 +0000 (08:51 +0000)
commit06a92e0d8c9042c2b8cd027b3c187f94c56e9b91
tree0d57d48e19f2a34dfceaf38761a6da98343ea1cc
parent351790353a8ff01a3fb559327dd49d357c9bad12
arch-arm: Handle empty object_file scenario in ArmFsWorkload

At the moment it is actually possible to pass en empty object file
to the ArmFsWorkload (OsKernel) class. We need to handle this
situation as well.
In case no bootloader nor object file is passed, we default to
AArch64 (default value for ArmFsWorkload)

Change-Id: I3b4aa8b8d61a8fac08da218125984b3bb1d38fb9
Signed-off-by: Giacomo Travaglini <giacomo.travaglini@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/27707
Tested-by: Gem5 Cloud Project GCB service account <345032938727@cloudbuild.gserviceaccount.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Gabe Black <gabeblack@google.com>
src/arch/arm/fs_workload.cc