Thanks Gabe! That worked.
diff --git a/src/arch/x86/fs_workload.cc b/src/arch/x86/fs_workload.cc
index 3f46eba..f895cb6 100644
--- a/src/arch/x86/fs_workload.cc
+++ b/src/arch/x86/fs_workload.cc
@@ -189,6 +189,12 @@ FsWorkload::initState()
// 32 bit data segment
SegDescriptor dsDesc = i
Hello Gabe,
Thanks for the response! Can you tell me how I can find the compiler version
used to generate libpython.3.8.a. ?
Regards,
Raghul S
From: Gabe Black
Sent: Thursday, October 15, 2020 9:25 PM
To: gem5 users mailing list
Cc: Neelakantan,Aravind ; Shivakumar,Raghul
Subject: Re: [gem5
As far as I know those patches should no longer be necessary, although I
haven't tried to run KVM on x86 recently. Other problems could be that KVM
isn't enabled in your BIOS or your operating system, or that the
permissions on the device file gem5 needs to start a VM isn't set properly.
Unfortunat
It looks like your libpython3.8.a was not built with the same compiler as
the one you're trying to build gem5 with. Extra information it sets aside
for LTO (link time optimization) is apparently not compatible between the
two versions.
Gabe
On Thu, Oct 15, 2020 at 5:14 PM Shivakumar,Raghul via ge
Ayaz,
As far as I know, those patches were superseded by this one:
https://gem5-review.googlesource.com/c/public/gem5/+/12278
src/arch/x86/system.cc was deleted in master, and I can find bits of the
patch scattered around different files, so it kind of looks like it's been
applied already? Maybe
Hello Ryan,
I think, if you are using an Intel machine, you will still need to apply
those patches. The conversation on this issue might be useful for you:
https://github.com/darchr/gem5art-experiments/issues/60
-Ayaz
On Thu, Oct 15, 2020 at 5:20 PM Gambord, Ryan via gem5-users <
gem5-users@gem
Hello all,
I'm working off commit b1b8af04439240c532d3530a02773b75b9853f77
I get the following error when I try to run a full-system
(configs/example/fs.py) with the X86KvmCPU:
panic: KVM: Failed to enter virtualized mode (hw reason: 0x8021)
I used to have kvm working with a pre-2018 versio
Hello All,
I am trying to build the gem5 simulator which I cloned from
https://github.com/gem5/gem5.git branch -stable. I am getting the following
error message( image).
My environment settings are as follows:
GCC - version 9.3.0
Python - version 3.8.2
Scons - version 3.1.2
[cid:image001.png@01
Krishnan,
I am having some trouble with getting X86KvmCPU to run on my server. Could
you share the commit hash you are using successfully?
Ryan Gambord
On Thu, Oct 15, 2020 at 1:49 AM krishnan gosakan via gem5-users <
gem5-users@gem5.org> wrote:
> [This email originated from outside of OSU.
Hey Farhad,
I've added a Jira ticket about this bug:
https://gem5.atlassian.net/browse/GEM5-798.
I'm afraid to say we don't have a solution right now, but we suspect it may
be similar to this bug: https://gem5.atlassian.net/browse/GEM5-332. You can
see the comments on this bug for more informatio
Yes, I did :).
--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616
web: https://www.bobbybruce.net
On Thu, Oct 15, 2020 at 1:48 PM Gabe Black wrote:
> I think you mean the TimingSimpleCPU, not the AtomicTimingCPU.
>
> Gabe
>
> On Thu, Oct 15, 2020 at 1:41 PM Bobby Bruce vi
I think you mean the TimingSimpleCPU, not the AtomicTimingCPU.
Gabe
On Thu, Oct 15, 2020 at 1:41 PM Bobby Bruce via gem5-users <
gem5-users@gem5.org> wrote:
> Hey Krishnan,
>
> Linux does take about 45 minutes or so to run using AtomicSimpleCPU.
> You're not doing anything wrong in this regard.
Hey Krishnan,
Linux does take about 45 minutes or so to run using AtomicSimpleCPU. You're
not doing anything wrong in this regard. I'm afraid there's no information
I can give you on making it faster. Anything to make this significantly
faster, would be sacrificing the accuracy of simulation. This
A ok, that makes sense, thanks for the quick answer.
On 10/15/2020 6:57 PM, Giacomo Travaglini wrote:
Hi Dimitrios;
The problem is that your binary is dynamically linked. You need to point the
elf loader to the aarch64 interpreter(linker) which is usually provided within
the toolchain.
Pleas
Hi Dimitrios;
The problem is that your binary is dynamically linked. You need to point the
elf loader to the aarch64 interpreter(linker) which is usually provided within
the toolchain.
Please have a look at:
https://stackoverflow.com/questions/5054/how-to-run-a-dynamically-linked-executabl
Hi,
I am trying to run a simple binary compiled on an ARM machine using gem5
SE mode and ARM ISA. The same binary I can run it using FS mode. The
error message on SE is:
"panic: panic condition fd < 0 occurred: Failed to open file
/lib/ld-linux-aarch64.so.1."
What are the requirements fo
Hi all,
Just following up on this. Any help would be appreciated!
Thanks,
Farhad
From: Farhad Yusufali
Sent: October 13, 2020 9:37 PM
To: gem5-users@gem5.org
Subject: SE Mode crashing with multithread workload
Hi all,
My gem5 version is fa70478413e4650d0058cbf
Thanks Gabe. You are right that the executable was actually built successfully.
My concerns were that these errors may lead to strange behaviour later.
Hopefully, the simulator will work fine.
Best,
Xiongfei
From: Gabe Black [mailto:gabebl...@google.com]
Sent: Thursday, 15 October 2020 9:34 PM
Those are not errors, or at least not errors that will prevent the build
from being successful. The linker errors (DWARF error: ...) are unfortunate
but don't prevent the build from finishing. I don't know what, if anything,
might be affected by them. The other message is just a warning.
Gabe
On
Hi all,
When I built gem5 simulator for ARM, I met the below errors. Any idea how to
fix them?
Thanks.
Cheers,
Xiongfei
=
/home/xiongfei/gem5_working/gem5_20.1/build/ARM/gem5.opt
You may want to ru
Hi all.
I hope everyone is doing good. I recently started working with gem5
simulator. I am trying to do some modification to the page table walker
(pagetable_walker). My problem is that booting linux under full system
emulation is very slow. It takes nearly 30 to 40 minutes to boot. I am
using Ato
Hi all,
Just a quick upate on this thread.
I have a small patch that solves the last problem I was describing and allows
not having default values (but using the defaults defined in the core config)
when using a custom simulation script (e.g., a modification of se.py that
doesn't use all the
22 matches
Mail list logo
