446c0ff6ba
Current way of initializing GICv3 in the gem5 bootloader doesn't work when there is a PE labelled with non-zero Aff1, Aff2 or Aff3 in the MPIDR_EL1 register (For example in a multi-cluster configuration). This is because the bootloader is considering Aff0 only mrs x0, mpidr_el1 // extract the primary CPU. ldr x1, =0xff00ffffff and x2, x0, #0xff // use Aff0 as cpuid for now... With this patch we are solving the issue, by considering every affinity number. Now the primary cpu is the cpu with Aff3..Aff0 = 0. The bootloader was also using Aff0 (stored in x2, see above) to let every CPU index their own redistributor memory mapped frames. In this model every secondary CPU was in charge of initializing their own redistributor registers. This can't be used anymore as we have a tuple of affinity numbers now rather than a single flat index. We are addressing the issue by letting the primary cpu initialize every redistributor in the system. This is done by iterating over consecutive frames and by reading GICR_TYPER.Last, which is set to 1 if the current frame is the last one. Change-Id: I2bcad286c2282bf1c47618e5391bf1c2e2b27013 Signed-off-by: Giacomo Travaglini <giacomo.travaglini@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/59393 Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Tested-by: kokoro <noreply+kokoro@google.com> Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>
This is the gem5 simulator. The main website can be found at http://www.gem5.org A good starting point is http://www.gem5.org/about, and for more information about building the simulator and getting started please see http://www.gem5.org/documentation and http://www.gem5.org/documentation/learning_gem5/introduction. To build gem5, you will need the following software: g++ or clang, Python (gem5 links in the Python interpreter), SCons, zlib, m4, and lastly protobuf if you want trace capture and playback support. Please see http://www.gem5.org/documentation/general_docs/building for more details concerning the minimum versions of these tools. Once you have all dependencies resolved, type 'scons build/<CONFIG>/gem5.opt' where CONFIG is one of the options in build_opts like ARM, NULL, MIPS, POWER, SPARC, X86, Garnet_standalone, etc. This will build an optimized version of the gem5 binary (gem5.opt) with the the specified configuration. See http://www.gem5.org/documentation/general_docs/building for more details and options. The main source tree includes these subdirectories: - build_opts: pre-made default configurations for gem5 - build_tools: tools used internally by gem5's build process. - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - include: include files for use in other programs - site_scons: modular components of the build system - src: source code of the gem5 simulator - system: source for some optional system software for simulated systems - tests: regression tests - util: useful utility programs and files To run full-system simulations, you may need compiled system firmware, kernel binaries and one or more disk images, depending on gem5's configuration and what type of workload you're trying to run. Many of those resources can be downloaded from http://resources.gem5.org, and/or from the git repository here: https://gem5.googlesource.com/public/gem5-resources/ If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.