From 85a1ac2ceac7728a05005fa63fa067da7794cbbb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Thu, 6 Aug 2020 03:00:02 +0000 Subject: [PATCH] cirosantilli2 --- README.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index d6a5fcd..d06e64c 100644 --- a/README.adoc +++ b/README.adoc @@ -25769,7 +25769,7 @@ while aarch64 only 7 minutes. I had previously documented on README 10 minutes at: 2eff007f7c3458be240c673c32bb33892a45d3a0 found with `git log` search for `10 minutes`. But then I checked out there, run it, and kernel panics before any messages come out. Lol? -Logs of the runs can be found at: https://github.com/cirosantilli-work/gem5-issues/tree/0df13e862b50ae20fcd10bae1a9a53e55d01caac/arm-hpi-slow +Logs of the runs can be found at: https://github.com/cirosantilli2/gem5-issues/tree/0df13e862b50ae20fcd10bae1a9a53e55d01caac/arm-hpi-slow The cycle count is higher for `arm`, 350M vs 250M for `aarch64`, not nowhere near the 5x runtime time increase. @@ -25777,7 +25777,7 @@ A quick look at the boot logs show that they are basically identical in structur ===== gem5 x86_64 DerivO3CPU boot panics -https://github.com/cirosantilli-work/gem5-issues/issues/2 +https://github.com/cirosantilli2/gem5-issues/issues/2 .... Kernel panic - not syncing: Attempted to kill the idle task! @@ -27490,7 +27490,7 @@ error while converting qcow2: Failed to get "write" lock When doing long simulations sweeping across multiple system parameters, it becomes fundamental to do multiple simulations in parallel. -This is specially true for gem5, which runs much slower than QEMU, and cannot use multiple host cores to speed up the simulation: https://github.com/cirosantilli-work/gem5-issues/issues/15[], so the only way to parallelize is to run multiple instances in parallel. +This is specially true for gem5, which runs much slower than QEMU, and cannot use multiple host cores to speed up the simulation: https://github.com/cirosantilli2/gem5-issues/issues/15[], so the only way to parallelize is to run multiple instances in parallel. This also has a good synergy with <>.