Driver API

[matyas-streamhpc]

No description provided.

[MKKnorr]

Just a first superficial review. I think this might need some more in-depth changes

[MKKnorr]

I think the reference-file is not needed. A proper "understand" section instead would be better. This way a lot of the stuff in the how-to section could also be incorporated there, as it is not strictly a how-to right now

[MKKnorr]

I think a lot of the stuff that currently is in the how-to section actually belongs in the understand section. How-to should be condensed to mostly just give instructions on... well, "how to" port from the cuda driver api to the hip api. The parts explaining what the driver api is used for would better fit in the understand section.

[amd-jnovotny]

Here is a batch of edits for you to review and process. I'll review the rest of the document today. Sorry that this task wound up being split between two reviewers.

[amd-jnovotny]

Here are the rest of my editorial suggestions.

[amd-jnovotny]

@matyas-streamhpc Please let me know when it's ready for review. Looks like some edits (that were in the hidden ... click to expand section) are still outstanding. No rush if you're busy.

[amd-jnovotny]

Overall, it looks very good now, so I'll approve. I've added a couple of minor edits and a few questions involving capitalization consistency and the use of must vs. should.

[yiakwy-xpu-ml-framework-team]

Note __frcp_rn is not supported in ROCM 6.2.

Many customer codes invovles PTX inline asm. We need a table to show

• How amd asm is different from PTX and practices in porting
• Existing C primitives support AMD asm instruction (ISA CDNA3) and many existing tools pointing to old RDNA or GCN arch (for PC and DIY users, not datacenter users).

[jujiang-del]

Do we really need a separate doc for HIP driver APIs? The content doesn't cover all as supported in
https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDA_Driver_API_functions_supported_by_HIP.md
Some of ctx APIs are deprecated, only for porting support.
RST file for driver porting guide looks good.

[neon60]

Do we really need a separate doc for HIP driver APIs? The content doesn't cover all as supported in https://github.com/ROCm/HIPIFY/blob/amd-staging/docs/tables/CUDA_Driver_API_functions_supported_by_HIP.md Some of ctx APIs are deprecated, only for porting support. RST file for driver porting guide looks good.

@jujiang-del Update the PR based on the comment. Removed the separate doc and kept the groups.