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

kvm: let clock scale setting apply immediately #8

Merged
merged 1 commit into from
Nov 22, 2017

Conversation

vitalych
Copy link
Member

@vitalych vitalych commented Nov 5, 2017

Signed-off-by: Vitaly Chipounov [email protected]

@adrianherrera
Copy link
Member

adrianherrera commented Nov 6, 2017

Can you mention in one of the commit messages why this change was made? I think it's good to note these things for future reference.

@vitalych
Copy link
Member Author

@adrianherrera I mentioned it in the code. People don't really read commit messages.

@adrianherrera
Copy link
Member

Hey, I read commit messages! :( Especially to see why a change was made.

I was more after an explanation of why it was changed from an integer to a pointer. But sure, have at it.

@vitalych
Copy link
Member Author

Ok, good point, I will update the explanations

Changed it to a pointer because we cannot wait for kvm_run to return.
Interrupts may happen while kvm_run is running and we want these
interrupts to take into account the new clock speed.

Signed-off-by: Vitaly Chipounov <[email protected]>
@vitalych vitalych merged commit 772451c into v1.0.50-se Nov 22, 2017
@vitalych vitalych deleted the clock-scale-fix branch November 22, 2017 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants