Allow multiple instances of MMTk to co-exist

[qinsoon]

In GitLab by @qinsoon on Nov 29, 2019, 17:48

• Remove global states of MMTk, and encapsulate states with MMTk instances

[qinsoon]

In GitLab by @qinsoon on Jan 7, 2020, 11:20

assigned to @qinsoon

[qinsoon]

In GitLab by @qinsoon on Jan 7, 2020, 11:28

I am refactoring global variables/states into an MMTK struct, which is an instance of MMTk. To start with, I have a singleton MMTK instance as a global variable. When the refactoring is done, we can remove the global MMTK instance, and allow multiple instances (we need to spend some time dealing with lifetime declarations and our MMTk API).

Progress for removing global states for MMTk:

• [x] Global PLAN
• [x] Global states for phase
• [x] Global GC statistics
• [x] Global VM map, Mmapper (Note: probably this should remain as globals)
• [x] Global reference processor
• [x] Global option map
• [x] Misc

[qinsoon]

In GitLab by @qinsoon on Jan 15, 2020, 18:40

mentioned in merge request !19

[qinsoon]

In GitLab by @qinsoon on Jan 16, 2020, 11:50

mentioned in merge request !20

[qinsoon]

In GitLab by @qinsoon on Jan 19, 2020, 18:58

mentioned in merge request !21

[qinsoon]

In GitLab by @qinsoon on Jan 23, 2020, 13:23

mentioned in merge request !22

[qinsoon]

In GitLab by @qinsoon on Jan 26, 2020, 19:10

mentioned in merge request !23

[qinsoon]

In GitLab by @qinsoon on Jan 31, 2020, 13:16

mentioned in merge request !24

[qinsoon]

In GitLab by @qinsoon on Feb 4, 2020, 14:28

mentioned in merge request !26

[qinsoon]

Closing this as listed tasks were all done. We have removed global states annd our API now supports multiple MMTk instances. However, we haven't verified that the internal implementation can properly support multiple instances. I am creating a new issue to track this.