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

Check with is_in_mmtk_spaces instead of is_mapped_address #123

Merged
merged 1 commit into from
Jan 29, 2024

Conversation

qinsoon
Copy link
Member

@qinsoon qinsoon commented Jan 28, 2024

Objects in VM spaces are not 'mmapped' by MMTk, so is_mapepd_address will return false for those. But they are still considered as in MMTk spaces (the VM space).

Note that malloc'd objects are not mapped by MMTk, and not in MMTk spaces, so both methods will return false for malloc'd objects. However, this seems irrelevant in this scan object code.

@qinsoon qinsoon added the backport-v1.9.2+RAI Backport the change to the branch v1.9.2+RAI label Jan 28, 2024
@qinsoon qinsoon requested a review from udesou January 29, 2024 05:00
Copy link
Contributor

@udesou udesou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@qinsoon qinsoon merged commit 6f38359 into mmtk:master Jan 29, 2024
9 checks passed
mergify bot pushed a commit that referenced this pull request Jan 29, 2024
Objects in VM spaces are not 'mmapped' by MMTk, so `is_mapepd_address`
will return `false` for those. But they are still considered as in MMTk
spaces (the VM space).

Note that malloc'd objects are not mapped by MMTk, and not in MMTk
spaces, so both methods will return `false` for malloc'd objects.
However, this seems irrelevant in this scan object code.

(cherry picked from commit 6f38359)
qinsoon added a commit that referenced this pull request Jan 29, 2024
) (#124)

This is an automatic backport of pull request #123 done by
[Mergify](https://mergify.com).


---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the
[documentation](https://docs.mergify.com/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on
`<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you
can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com
</details>

Co-authored-by: Yi Lin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v1.9.2+RAI Backport the change to the branch v1.9.2+RAI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants