Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stock JikesRVM crashes at boot time #168

Closed
qinsoon opened this issue Apr 17, 2024 · 1 comment · Fixed by #170
Closed

Stock JikesRVM crashes at boot time #168

qinsoon opened this issue Apr 17, 2024 · 1 comment · Fixed by #170

Comments

@qinsoon
Copy link
Member

qinsoon commented Apr 17, 2024

I was using FastAdaptiveImmix with stock JikesRVM (from https://github.com/JikesRVM/JikesRVM) and simply running rvm without any workload. Roughly half of the runs failed with one of the following issues.

@qinsoon
Copy link
Member Author

qinsoon commented Apr 18, 2024

We can modify the addresses in build/targets/x86_64_m32-linux.properties to work around the issues. I tried the following settings and did not see any issue.

target.bootimage.code.address=0x84000000
target.bootimage.data.address=0x80000000
target.bootimage.rmap.address=0x87000000
target.max-mappable.address=0xd0000000

However, if we do this, we need to update VM space in mmtk-jikesrvm to be consistent, and set the vm layout for mmtk-core so it does not overlap.

The binding declares VM space addresses:

// set vm space
builder
.options
.vm_space_start
.set(unsafe { Address::from_usize(0x6000_0000) });
builder.options.vm_space_size.set(0x800_0000);

mmtk-core heap range (VM space should not overlap with it):
https://github.com/mmtk/mmtk-core/blob/1bfd55809bf88d0085a891c13f5f507dc4f16904/src/util/heap/layout/vm_layout.rs#L126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant