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.

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

Change memory region to memory pool API and proper change in order to follow the current impelmentation #5

Closed
wants to merge 11 commits into from

Conversation

facao
Copy link
Contributor

@facao facao commented Mar 29, 2016

No description provided.

facao and others added 11 commits March 23, 2016 13:39
…commented code

No definition of HSA_AMD_MEMORY_POOL_INFO_ALLOC_MAX_SIZE
- add call to allow_access on am_alloc with amHostPinned flag
- remove call to hsa_memory_register and hsa_memory_deregister, those
are noop for AMD
- move initialization to am_host_memory_pool and am_memory_pool on
HSADevice constructor
- remove unnecessary check for system memory accessibility because
system memory is always accessible via call to
hsa_amd_memory_pool_allow_access.
- discover system memory region from host agent instead of gpu agent,
@whchung
Copy link
Collaborator

whchung commented Mar 29, 2016

could you help change the pull request so it goes to a branch, instead of master? I'd like to run more tests before taking it to master.

@whchung
Copy link
Collaborator

whchung commented Mar 29, 2016

Fan, could you try create a branch on your local fork, cherry-pick your commits into the branch, and submit a new pull request? By default it would be sent to a branch which shares the same name as yours.

@whchung
Copy link
Collaborator

whchung commented Mar 29, 2016

Fan, I've created a branch "hsa_pool_api". Could you help try alter this pull request so its goes there, or submit a new one if you can't do it in this pull request?

BitBucket allow users to create new branches when submitting pull requests. But it seems Github don't have this feature for some reason.

@whchung
Copy link
Collaborator

whchung commented Mar 29, 2016

Close #5 as it has been replaced by #8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants