-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Minor vm additions #5002
Minor vm additions #5002
Conversation
Prevent unmapping predefined locations
Add upgrade() method
@@ -844,15 +858,13 @@ namespace vm | |||
{ | |||
if (location == vm::user64k || location == vm::user1m) | |||
{ | |||
g_mutex.lock_upgrade(); | |||
lock.upgrade(); | |||
|
|||
if (!loc) | |||
{ | |||
// Deferred allocation | |||
loc = _find_map(0x10000000, 0x10000000, location == vm::user64k ? 0x201 : 0x401); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to remove this ternary op
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and change base on _find_map back to 0x30.. (github doesnt let me comment on that line).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing them won't change anything...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both vm::user locs are "weak" - their exact address is either dynamic or undocumented, but that's enough to classify them differently. Other areas are hardcoded really hard. And _find_map only needs to start at the end of vm::main. Inbetween lies "uncertain" area which can be adjusted from the outside. That's how I see it.
No description provided.