Skip to content

tdisp: Push locking interface up to the caller of TdispClient rather than enforcing a particular lock #4518

Open
Open
tdisp: Push locking interface up to the caller of TdispClient rather than enforcing a particular lock#4518
Assignees
mfrohlich-msft
Labels
tdispRelated to bring-up of TDISP in OpenHCL

Description

@mfrohlich-msft
Michael Frohlich (mfrohlich-msft)
opened on Sep 28, 2026

TdispClientState already uses &mut self and therefore the caller (in this case, vpci_relay) should get control over locking mechanisms, not the tdisp exports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

tdispRelated to bring-up of TDISP in OpenHCL

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions