Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
#11830: Remove more constants from common_runtime_address_map #13785
#11830: Remove more constants from common_runtime_address_map #13785
Changes from 4 commits
f70a5df
eb651e8
1185dc1
ca81983
c7ed45c
bc4231b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The idea with moving
L1_KERNEL_CONFIG
is that it shouldn't belong in the HAL because it is a host side concept.HalL1MemAddrType::UNRESERVED
should point toMEM_MAP_END
(we could rename UNRESERVED to MEMORY_MAP_END) to be more clear.The original idea was to create a L1 Buffer (that is allocated bottom up) to hold the kernel config and users of
HalL1MemAddrType::KERNEL_CONFIG
would query device to get the kernel config buffer address. This won't work for ethernet cores because our allocator does not allocate buffers on ethernet cores.To handle all programmable core types in the same manner,
Device
could reserve space for kernel config on all programmable core types and then updatel1_unreserved_base
that is passed intoAllocatorConfig
to follow kernel configThere 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.
Can we file a separate issue to track this as an enhancement? Today it is behind Hal, and this PR just leaves it there.
Currently UNRESERVED is being set differently depending on core type.
I don't see it being set to the equivalent of MEM_MAP_END anywhere, for instance I see this:
((L1_KERNEL_CONFIG_BASE + L1_KERNEL_CONFIG_SIZE - 1) | (max_alignment - 1)) + 1;
Maybe I don't have the necessary background to make this change.