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.

Sign up for GitHub

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

Jump to bottom

Add safe handling memory read/write instead of naive CR3 switch #9

Open
wbenny opened this issue Aug 31, 2018 · 2 comments
Open

Add safe handling memory read/write instead of naive CR3 switch #9

wbenny opened this issue Aug 31, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@wbenny
Copy link
Owner

wbenny commented Aug 31, 2018

No description provided.

@wbenny wbenny added the enhancement New feature or request label Aug 31, 2018
@hzqst
Copy link

hzqst commented Jan 29, 2019

https://github.com/intel/haxm/blob/d29c7cdabb2797cd41f590e52c435eabfcd432d2/core/vtlb.c#L1115
is your friend.
note that GPA to HVA mapping is a hard job for vmm host since you are not able to use MmMapIoSpace
or MmGetVirtualForPhysical or some other kernel apis to do those mapping stuffs. espicially on Windows 10 RS4.

@wbenny
Copy link
Owner Author

wbenny commented Jan 29, 2019 •
edited

Thanks for the link. FWIW, some time ago I've already added this: https://github.com/wbenny/hvpp/blob/master/src/hvpp/hvpp/ia32/memory.cpp#L85, which behaves similarly to MmMapIoSpace (with the benefit of mapping even non-IO space). It's just currently not used for anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wbenny @hzqst