- Rename Bonaire target to be gfx704.
- Eliminate gfx800 and make Iceland and Tonga both use gfx802 as they use the same code.
- List target features supported by each processor in the processor table together with the default value.
- Add xnack flag to e_flags.
- Remove xnack from kernel metadata and kernel descriptor since it is now a whole code object property.
Details
- Reviewers
kzhuravl b-sumner nhaehnle tpr - Commits
- rGa697880b3895: [AMDGPU] Rename Bonaire target to be gfx704; remove gfx800 and make Iceland and…
rG31105cc99761: [AMDGPU] Rename Bonaire target to be gfx704; update target feature handling
rL320457: [AMDGPU] Rename Bonaire target to be gfx704; remove gfx800 and make Iceland and…
rL320378: [AMDGPU] Rename Bonaire target to be gfx704; update target feature handling
Diff Detail
Event Timeline
List target features supported by each processor in the processor table together with the default value.
Remove xnack from kernel metadata and kernel descriptor since it is now a whole code object property.
Eliminate gfx800 and make Iceland and Tonga both use gfx802 as they use the same code.
Is this correct? IIRC, Tonga's atomic add/sub must always have the glc bit enabled (iceland does not need that). This was the reason for having them as separate ccs.
docs/AMDGPUUsage.rst | ||
---|---|---|
126 | Should this APU have an xnack on by default? I remember we talked about defaulting xnack to on for all APUs. | |
144 | Should this APU have an xnack on by default? I remember we talked about defaulting xnack to on for all APUs. | |
525–530 | Should we mention anything about the fact that we will not link code objects with different xnack settings? |
Should this APU have an xnack on by default? I remember we talked about defaulting xnack to on for all APUs.