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

Unclear usage of NM_OPEN_NO_MMAP #33

Closed
GoogleCodeExporter opened this issue Mar 30, 2015 · 1 comment
Closed

Unclear usage of NM_OPEN_NO_MMAP #33

GoogleCodeExporter opened this issue Mar 30, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Doing a search through the repo for NM_OPEN_NO_MMAP I can't find where it is 
actually used. In fact the effect it's supposed to have is determined entirely 
by nr_arg2 in the nm_req structure. As long as the parent desc has the same 
nr_arg2 req.nr_arg2, even 0, the mmap address is used.

This should be revised, it's in the public API and it's confusing.

Original issue reported on code.google.com by ciprian....@linaro.org on 11 Nov 2014 at 1:27
@vmaffione
Copy link
Collaborator

Not valid, the flag is used by nm open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vmaffione @GoogleCodeExporter