Smoke test to verify pinned memory

[charan-003]

Following up on #8649

Adding a Smoke test to verify pinned memory

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: a90b0d3b-7a6c-44b1-9559-c5e7ea849d6b

📥 Commits

Reviewing files that changed from the base of the PR and between cea7dcd and 8056854.

📒 Files selected for processing (1)

• test/cuda_smoke/cuda_runtime_smoke.cu

---

📝 Walkthrough

Summary by CodeRabbit

• Tests
  • Added CUDA smoke tests for pinned host memory workflows, including allocation, data transfer, kernel execution, and validation.
  • Added CUDA smoke tests for zero-copy mapped memory with device capability detection.

Walkthrough

PR adds two CUDA smoke tests to validate pinned host memory workflows. The first test exercises basic pinned memory allocation via cudaMallocHost, host-to-device copy, kernel execution, and result validation. The second test verifies mapped zero-copy pinned memory by checking device capability, allocating with cudaHostAllocMapped, retrieving a device pointer, and validating kernel execution on the mapped view.

Changes

Pinned host memory smoke tests

Layer / File(s)	Summary
Basic pinned host memory workflow test/cuda_smoke/cuda_runtime_smoke.cu	Test allocates pinned memory with cudaMallocHost, performs explicit host↔device copies around increment_kernel execution, asserts results, and validates error status at cleanup.
Mapped pinned host memory with capability check test/cuda_smoke/cuda_runtime_smoke.cu	Test checks device support for host memory mapping via cudaDevAttrCanMapHostMemory, allocates mapped pinned memory, retrieves device pointer view via cudaHostGetDevicePointer, runs kernel directly on mapped memory, and validates host-side results.

Suggested reviewers

• bernhardmgruber

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[charan-003]

@bernhardmgruber added a smoke test to verify pinned memory