This repository has been archived by the owner on Nov 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 74
Enable Clone for CpuId, Msrs and MsrList #13
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Field
entries
is type of __IncompleteArrayField, is it safe to clone it?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is like phantomdata safe to clone. The cloning of actual data is done by the
Clone
implementation ofFamStructWrapper
.The clone implementation added by this PR is not even actually used. But it is needed to satisfy the
requirement.
Another option would be to remove
Clone
from theFamStructWrapper
requirements as it's not actually needed AFAICT.CC @serban300 as the FamStructWrapper op.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you need
Clone
functionality for an instance ofFamStructWrapper
,T
needs to implementClone
, otherwise the code won't build, becausemem_allocator
is aVec<T>
.I think it's ok to implement
Clone
forkvm_cpuid2
,kvm_msrs
andkvm_msr_list
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's right.
Let's stick to the strategy implemented in this PR then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
__IncompleteArrayField are not safe to clone as @jiangliu also said in the previous commit. More details on this issue: rust-lang/rust-bindgen#1431. I am not sure what is the best way to move forward here honestly, but adding clone doesn't seem right to me.