-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[GPU] Allow unlimited allocations #25955
base: master
Are you sure you want to change the base?
[GPU] Allow unlimited allocations #25955
Conversation
@@ -3,13 +3,15 @@ | |||
// | |||
|
|||
#include "intel_gpu/runtime/debug_configuration.hpp" | |||
#include "intel_gpu/runtime/device.hpp" |
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.
[random spot]
Shouldn't we apply the same extended limit for OpenCL buffers?
cl_mem_flags flags = 0;
flags |= CL_MEM_ALLOW_UNRESTRICTED_SIZE_INTEL;
cl_mem buffer = clCreateBuffer(context, flags, size, host_ptr, errcode_ret);
switch (get_allocation_type()) { | ||
case allocation_type::usm_host: | ||
_buffer.allocateHost(_bytes_count); | ||
_buffer.allocateHost(_bytes_count, &properties[0]); |
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.
Accessing an empty vector (in case of engine->get_device_info().vendor_id == INTEL_VENDOR_ID) at index 0 with operator[] could cause UB probably
And specs say (regarding the properties argument): The list is terminated with the special property 0. So it should be either nullptr or vector with single 0 value by default
2ef733b
to
7ef750c
Compare
7ef750c
to
63ab88e
Compare
Tickets: