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

hsakmt-dev should not install linux kernel headers #42

Closed
wants to merge 2 commits into from

Conversation

candrews
Copy link
Contributor

@candrews candrews commented Aug 8, 2019

hsakmt-dev should not install include/linux/* (currently just kfd_ioctl.h) as those are linux kernel headers provided by the linux kernel header packages (linux-headers-* on Debian/Ubuntu or kernel-headers-* on Red Hat / Fedora)

Ignore requests to bind to invalid NUMA nodes. This affects only
legacy applications (such as KFDTest) that allocate system memory
as paged memory with a GPU node ID.

Change-Id: I81e514af6d0c1ab2ed5229adeeca1fa0ab2a0685
Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
(cherry picked from commit 54d664d)
hsakmt-dev should not install include/linux/* (currently just kfd_ioctl.h) as those are linux kernel headers provided by the linux kernel header packages (`linux-headers-*` on Debian/Ubuntu or `kernel-headers-*` on Red Hat / Fedora)
@fxkamd
Copy link
Contributor

fxkamd commented Aug 20, 2019

I'll apply this one, not PR#41. We do need kfd_ioctl.h for building libhsakmt. Depending on the latest kernel headers to build our library is something we're trying to avoid. But you're right, we don't need to install this header file as the clients of libhsakmt don't need it.

@fxkamd
Copy link
Contributor

fxkamd commented Aug 20, 2019

Can I add a Signed-off-by: Craig Andrews <...> to your commits as certificate of origin? See also https://stackoverflow.com/questions/1962094/what-is-the-sign-off-feature-in-git-for.

@candrews
Copy link
Contributor Author

Can I add a Signed-off-by: Craig Andrews <...> to your commits as certificate of origin?

You absolutely can. If necessary, I can update any PRs/commits myself doing so, just let me know what's better/easier for you.

@fxkamd
Copy link
Contributor

fxkamd commented Aug 20, 2019

I'll do it on my local branch, where I'm cherry-picking your patches and running them through our internal build/test and code review process. Thanks!

@candrews
Copy link
Contributor Author

@fxkamd Do you have any news? I'm eager to get this merged and stop having to carry/maintain the patch :)

@kentrussell
Copy link
Contributor

We missed the branching for 2.8, but it's slated to be included in 2.9.

@candrews
Copy link
Contributor Author

candrews commented Oct 4, 2019

21f4754

@candrews candrews closed this Oct 4, 2019
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.

None yet

3 participants