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

kvmi: increase the message size #25

Merged
merged 2 commits into from
Feb 22, 2020
Merged

kvmi: increase the message size #25

merged 2 commits into from
Feb 22, 2020

Conversation

adlazar
Copy link
Collaborator

@adlazar adlazar commented Dec 2, 2019

This will allow us to read a whole page with KVMI_READ_PHYSICAL.

Signed-off-by: Adalbert Lazăr [email protected]

This will allow us to read a whole page with KVMI_READ_PHYSICAL.

Signed-off-by: Adalbert Lazăr <[email protected]>
@mtarral
Copy link
Collaborator

mtarral commented Dec 2, 2019

@adlazar could you explain this modification, because it's not obvious to me why we are introducing a magic number * 2 to increase the message size ?

@adlazar
Copy link
Collaborator Author

adlazar commented Dec 2, 2019

For convenience, we've tried to keep the message limit small and page size multiple (including the message header). The variable size commands and command replies are affected by this limit. The old value (one page size minus the message header) won't allow us to read (or write) a whole page, which is a common use case, I guess.

@mtarral
Copy link
Collaborator

mtarral commented Dec 2, 2019

@adlazar can i merge this, or do you need more eyes/testing on it ?

@adlazar
Copy link
Collaborator Author

adlazar commented Dec 2, 2019

You can merge it, but you need it in userspace (libvmi) too.

@Wenzel
Copy link
Member

Wenzel commented Feb 22, 2020

I forgot about this one, merging now.

@Wenzel Wenzel merged commit bb3ca20 into KVM-VMI:kvmi-v6 Feb 22, 2020
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.

3 participants