alloc: access to the memory map through uncached addresses #253
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes access to the platform memory map to go through uncached address range. This will make alloc functions truly shared between cores and also save us many invalidate operations. Memory map needs to be statically defined, so cannot be allocated itself in ucached zone. Signed-off-by: Tomasz Lauda <tomasz.lauda@linux.intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes access to the platform memory map to go through uncached
address range. This will make alloc functions truly shared
between cores and also save us many invalidate operations.
Memory map needs to be statically defined, so cannot be
allocated itself in ucached zone.
Signed-off-by: Tomasz Lauda tomasz.lauda@linux.intel.com