[shimV2] Implements the VM VPMem Controller#2652
Merged
rawahars merged 1 commit intomicrosoft:mainfrom Mar 27, 2026
Merged
Conversation
Contributor
Author
|
Related to: #2651 which is the same pattern but for SCSI |
This change implements the VPMem controller operations for the new V2 shim. Signed-off-by: Justin Terry <terryjustin@microsoft.com>
jterry75
force-pushed
the
v2_shim/implement_vpmem_controller
branch
from
b3d70e4 to
687523f
Compare
jterry75
changed the title
rawahars
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change implements the VPMem controller operations for the new V2 shim.
Each of the Controller, Disk, Mount types independently maintain their own state and reference counting to ensure that all usage of disks and eventual guest mount paths are reference counted for sharing ensuring clean creation and cleanup across the lifetime of the caller. This could be a container, pod, or static lease.