ver: bump to v0.8.0 - #65
Draft
safl wants to merge 1 commit into
Draft
Conversation
safl
marked this pull request as draft
August 25, 2026 20:55
This was referenced Aug 25, 2026
safl
force-pushed
the
ver_v0_8_0
branch
2 times, most recently
from
August 26, 2026 08:21
f13d095 to
11bffca
Compare
safl
added a commit
to safl/xNVMe
that referenced
this pull request
Aug 26, 2026
uPCIe grew the primitives needed to share a controller under vfio: a runtime record describing a controller in offsets, the control plane a controller's server speaks with its clients, and a heap that carries its own description. None of them exist at v0.7.0, which is what this tree vendored until now, so the whole tree moves to v0.8.0 rather than mixing versions. Taken verbatim from safl/upcie#65, which tags the layer safl/upcie#63 adds. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
The control plane lands a new public surface: a runtime record, the protocol a controller's server speaks with its clients, and a heap that carries its own description. Consumers vendor these headers by version rather than by commit, so the number has to move before xNVMe can pin them. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
safl
added a commit
to safl/xNVMe
that referenced
this pull request
Aug 26, 2026
uPCIe grew the primitives needed to share a controller under vfio: a runtime record describing a controller in offsets, the control plane a controller's server speaks with its clients, and a heap that carries its own description. None of them exist at v0.7.0, which is what this tree vendored until now, so the whole tree moves to v0.8.0 rather than mixing versions. Taken verbatim from safl/upcie#65, which tags the layer safl/upcie#63 adds. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
safl
added a commit
to safl/xNVMe
that referenced
this pull request
Aug 26, 2026
uPCIe grew the primitives needed to share a controller under vfio: a runtime record describing a controller in offsets, the control plane a controller's server speaks with its clients, and a heap that carries its own description. None of them exist at v0.7.0, which is what this tree vendored until now, so the whole tree moves to v0.8.0 rather than mixing versions. Taken verbatim from safl/upcie#65, which tags the layer safl/upcie#63 adds. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
safl
added a commit
to safl/xNVMe
that referenced
this pull request
Aug 26, 2026
The control plane the multi-process work is built on lives in nvme_cplane.h, and the runtime record that describes what a server holds lives in nvme_runtime_record.h; neither exists in the v0.7.0 drop currently vendored. Taken from safl/upcie#65, which is v0.8.0 and not yet released, so expect this to be refreshed once it is. The snapshot is the whole include tree as upstream has it, copied rather than edited, so a later drop is a replacement and never a merge. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
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
1 participant
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.
Consumers vendor these headers by version rather than by commit, so the number
has to move before xNVMe can pin the delegation layer. Nothing changes but the
version:
make bumprewritesmeson.build, theVERSIONin the Makefile, andthe
@versiontag in every header.Stacked on #63.
Worth a careful look
That the bump reaches everything. It touches 52 files where the v0.7.0 bump
touched 50. The two new ones are
nvme_delegate.handnvme_runtime_record.h,which were the only headers in the tree carrying no
@versiontag at all;#63 adds it, since
make bumponly rewrites files that already haveone and they would otherwise have drifted silently.
Note this is separate from
NVME_DELEGATE_VERSION, which stays at 1. Thatnumber versions the wire protocol between an owner and its consumers and moves
only when the message layout changes; this one versions the library.
Verification
Builds clean on Linux 7.0.0-28-generic at the tip. Not otherwise exercised, and
there is nothing to exercise: no code changes, and the header tag is a comment.
CI covers the build and the format checks.