Sean Wilson has uploaded a new patch set (#2). (
https://gem5-review.googlesource.com/3745 )
Change subject: mem: Replace EventWrapper use with EventFunctionWrapper
..
mem: Replace EventWrapper use with EventFunctionWrapper
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3741
Change subject: sim: Remove DelayFunction
..
sim: Remove DelayFunction
`DelayFunction` is unused.
Change-Id:
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3749
Change subject: sim, x86: Replace EventWrapper use with EventFunctionWrapper
..
sim, x86: Replace EventWrapper use with
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3745
Change subject: mem: Replace EventWrapper use with EventFunctionWrapper
..
mem: Replace EventWrapper use with EventFunctionWrapper
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3748
Change subject: dev: Replace EventWrapper use with EventFunctionWrapper
..
dev: Replace EventWrapper use with EventFunctionWrapper
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3742
Change subject: mem: Move the Rank construction logic to the Rank
constructor
..
mem: Move the Rank construction logic to the
Hello Jason Lowe-Power,
I'd like you to do a code review. Please visit
https://gem5-review.googlesource.com/3740
to review the following change.
Change subject: misc: Add .travis.yml to kick off builds on github
..
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3746
Change subject: cpu, gpu-compute: Replace EventWrapper use with
EventFunctionWrapper
..
cpu, gpu-compute: Replace EventWrapper
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3747
Change subject: arm: Replace EventWrapper use with EventFunctionWrapper
..
arm: Replace EventWrapper use with EventFunctionWrapper
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3743
Change subject: sim: Add generic EventFunctionWrapper
..
sim: Add generic EventFunctionWrapper
Add EventFunctionWrapper, an event
Sean Wilson has uploaded this change for review. (
https://gem5-review.googlesource.com/3744
Change subject: mem: Replace EventWrapper in PacketQueue with
EventFunctionWrapper
..
mem: Replace EventWrapper in PacketQueue
Nikos Nikoleris has submitted this change and it was merged. (
https://gem5-review.googlesource.com/2908 )
Change subject: tests: Add ARM MOESI_CMP_directory regressions
..
tests: Add ARM MOESI_CMP_directory regressions
Nikos Nikoleris has submitted this change and it was merged. (
https://gem5-review.googlesource.com/2907 )
Change subject: arm: Refactor the VExpress_EMM system creation
..
arm: Refactor the VExpress_EMM system creation
Nikos Nikoleris has submitted this change and it was merged. (
https://gem5-review.googlesource.com/2906 )
Change subject: scons: Make MOESI_CMP_directory the default ARM ruby
protocol
..
scons: Make MOESI_CMP_directory
Nikos Nikoleris has submitted this change and it was merged. (
https://gem5-review.googlesource.com/2904 )
Change subject: ruby, arm: Forward invalidations to the local exclusive
monitor
..
ruby, arm: Forward invalidations
Nikos Nikoleris has submitted this change and it was merged. (
https://gem5-review.googlesource.com/2905 )
Change subject: config: Warn not fail for ARM systems configured with ruby
..
config: Warn not fail for ARM systems
Right, that's what I though, although I tried to change the type to uint32_t
and it still didn't work.
Anyway, I avoided this by using a topology which does not require that much
directories such as MeshDirCorners_XY. Using that topology, I was able to
simulate 1024 in a 32x32 mesh. Going for
Hi Gabe,
I wasn't around when we implemented the original device model. I suspect
the reasoning was that a touch screens are more reliable when using VNC
since they use absolute coordinates. IIRC, most virtualisation solution
nowadays default to touch screen emulation for this reason.
I started
Hi Juan,
There is probably something from with a configuration script somewhere
that tries to set the interleaving match bits to start at bit 256.
PyBind enforces that the value is small enough to fit in the target C++
type (uint8_t), which 256 clearly doesn't. This is why you get the
somewhat
Hello Jason Lowe-Power,
I'd like you to reexamine a change. Please visit
https://gem5-review.googlesource.com/3700
to look at the new patch set (#2).
Change subject: mem-garnet: Fix garnet stats
..
mem-garnet: Fix garnet
I'm trying to launch simulations with more than 256 cores, this is my
simulation parameters and the output:
./build/NULL/gem5.opt configs/example/garnet_synth_traffic.py
--num-cpus=512 --num-dirs=512 --mem-size=8192MB --network=garnet2.0
--topology=Mesh_XY --mesh-rows=1 --sim-cycles=1000
* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/simple-atomic: FAILED!
* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/simple-timing:
FAILED!*** diff[simout]: SKIPPED
* build/RISCV/tests/opt/quick/se/00.hello/riscv/linux/o3-timing: FAILED!
*
22 matches
Mail list logo