gt;1), Instr: MOV_R_M : ld al, DS:[esi]
==
Is this a bug in the current version of GEM5 where vaddr and paddr are not
being mapped?
Alain
On Apr 5, 2024, at 12:45 AM, Alain Aoun via gem5-users
wrote:
Hi,
I am simulation an elf_i386 (32-bit x
Hi,
Is it possible to force x86 processor to run in Real Mode when simulating in SE
or Protected mode is the only possible configuration?
Thanks,
Alain
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to
Hi,
I am simulation an elf_i386 (32-bit x86) assembly code in SE mode. In my
assembly code, there is mov al, [esi] where esi is set to 0x1970.
When running my simulation I get the following error: "panic: Tried to read
unmapped address 0x1970."
I am initializing the DRAM with a binary disk
Alain Aoun via gem5-users
mailto:gem5-users@gem5.org>> wrote:
Hello,
I am new to GEM5 and I would appreciate any guidance.
I would like to measure the performance of a assembly benchmark code. The
benchmark accesses memory addresses where data is pre-dumped at these addresses
in a RAW di
Hello,
I am new to GEM5 and I would appreciate any guidance.
I would like to measure the performance of a assembly benchmark code. The
benchmark accesses memory addresses where data is pre-dumped at these addresses
in a RAW disk image. My current setup consist of the image disk (containing the
Hello,
I am new to GEM5 and I would appreciate any guidance to start my experiment in
memory access performance.
I would like to measure the performance of a benchmark binary code generated by
compiling an assembly code that I wrote. The assembly code accesses memory
addresses where data is