Skip to content

Object Pinning #129

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

Closed
qinsoon opened this issue Sep 3, 2020 · 1 comment
Closed

Object Pinning #129

qinsoon opened this issue Sep 3, 2020 · 1 comment
Labels
A-interface Area: Interface/API A-space Area: Space/PageResource C-feature Category: Feature

Comments

@qinsoon
Copy link
Member

qinsoon commented Sep 3, 2020

We should add an API for pinning objects, such as fn pin_object(obj: ObjectReference) -> bool, which returns true if the object is pinned, or false if it cannot be pinned.

Whether an object can be pinned depends on its space:

  • for spaces such as semispace, objects cannot be pinned (unless we do some heavyweight operations to move the object to a pinnable space).
  • for spaces such as marksweep and immix, objects can be pinned if required.
  • for spaces such as immortal, objects are naturally pinned, and there is no further action needed to pin the objects.
@qinsoon qinsoon added C-feature Category: Feature A-space Area: Space/PageResource A-interface Area: Interface/API labels Sep 3, 2020
qinsoon added a commit to qinsoon/mmtk-core that referenced this issue Mar 28, 2023
@qinsoon
Copy link
Member Author

qinsoon commented May 14, 2023

Done in #703. If there is any other issue with object pinning, consider creating a new issue which is more specific to the issue.

@qinsoon qinsoon closed this as completed May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-interface Area: Interface/API A-space Area: Space/PageResource C-feature Category: Feature
Projects
None yet
Development

No branches or pull requests

1 participant