Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Draft] Add interface for arch-specific vCPU #1132

Closed
wants to merge 6 commits into from

Conversation

chl337
Copy link
Collaborator

@chl337 chl337 commented Mar 4, 2024

The finished work should solve #1105 and allow smoother integration of other architectures in the future.

NOTE: #1109 causes the build to fail.

@chl337 chl337 force-pushed the WIP_KVMvcpu_arch_concept branch 2 times, most recently from ccb0881 to 9e3bff4 Compare March 9, 2024 23:32
@chl337 chl337 force-pushed the WIP_KVMvcpu_arch_concept branch from 9e3bff4 to 802b0cf Compare March 17, 2024 13:51
@chl337 chl337 force-pushed the WIP_KVMvcpu_arch_concept branch from 86ee5c3 to 18e09f0 Compare April 3, 2024 21:13

#[derive(Debug)]
pub struct x86_64vCPU {

This comment was marked as outdated.

This comment was marked as outdated.

@shrik3
Copy link
Collaborator

shrik3 commented Apr 10, 2024 via email

@shrik3
Copy link
Collaborator

shrik3 commented May 7, 2024

we really need this. (as soon as we merge with main). I mean not just the vcpu, but the arch/ code organization in general.

#[cfg(target_arch="xyz")] here and there (inline) is annoying and error prone. Luckily we have only two architectures here. Imagine having more.

@shrik3
Copy link
Collaborator

shrik3 commented May 27, 2024

is this on the same agenda of #1136 , as well as the ongoing plan to abstract VM/VCPU creation?

@chl337
Copy link
Collaborator Author

chl337 commented May 27, 2024 via email

@chl337 chl337 marked this pull request as draft May 27, 2024 10:20
@chl337 chl337 changed the title [WIP] Add interface for arch-specific vCPU [Draft] Add interface for arch-specific vCPU May 27, 2024
@chl337 chl337 closed this Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants