openhcl/tdx: vCPU topology discrepancy between openhcl guests vs regular VMs
Open
Nobody has claimed this yet.
bug
tdx
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
We observe a discrepancy in vCPU to core mapping between openhcl guests (both CVMs and non-CMVs) vs other VMs that doesn't use openhcl.
This can lead to some performance issues for applications using vCPU affinity
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by investigating how vCPU-to-core topology is exposed for OpenHCL guests and regular VMs, then compare the mappings shown in the issue. Done means the topology is consistent and applications using vCPU affinity no longer encounter the reported discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100