Skip to content

Move the apertures configurations to the agent#23

Open
ammallya wants to merge 2 commits intoamd-stagingfrom
users/lmoriche/move-aspace-apertures-to-agent_t
Open

Move the apertures configurations to the agent#23
ammallya wants to merge 2 commits intoamd-stagingfrom
users/lmoriche/move-aspace-apertures-to-agent_t

Conversation

@ammallya
Copy link
Copy Markdown
Contributor

No description provided.

In a future change, to solve address space compatibility issues
between device specific architectures and generic architectures, all
address spaces will be made global.

This future change will make it impossible to specialize the generic
address spaces and hold architecture dependent apertures
configurations.

In order to determine the dependency of a generic segment address, we
will now need to use agent.

address_space_t::lower:  This is were the conversion from a generic
address space to a local or private_* address space using the agent
specific apertures will be done.  For now, just add the unused agent_t.

amd_dbgapi_address_dependency: add a wave_id argument and validate it.
Lower the segment address using the wave's agent, then call
address_space_t::address_dependency.

Notable change: reading/writing memory with amd_dbgapi_read_memory/
amd_dbgapi_write_memory now returns an INVALID_ARGUMENT_COMPATIBILITY
error if the address space is the generic address space and the wave_id
is WAVE_NONE. Prior to this change, the memory operation was executed
if the generic segment address was a global address.
Since the apertures configurations are agent dependent, move the
apertures configurations from the generic address space to the agent.
Use the agent's os_info to set the memory regions.
@ammallya
Copy link
Copy Markdown
Contributor Author

@lmoriche_amdeng @lancesix_amdeng @shvahedi_amdeng can you please prioritize this for the first release ( around Feb/Mar) to early customers/ alongside bring up

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.

2 participants