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

Test vmlaunch failure #165

Merged
merged 1 commit into from
Sep 2, 2016
Merged

Test vmlaunch failure #165

merged 1 commit into from
Sep 2, 2016

Conversation

connojd
Copy link
Member

@connojd connojd commented Aug 31, 2016

This patch tests a vmlaunch failure and ensures all checks pass in the vmcs launch function. Also, tests were added to reach full coverage of vmcs_intel_x64.cpp

{
vmcs_vm_instruction_error_read_count++;

if (vmcs_vm_instruction_error_read_count == 2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really over-specified.... would love to see an alternative to this. Specifically, if the implementation changes, this unit test will fail even if the code is still valid.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d781848 on connojd:master into aacc91e on Bareflank:master.

- The case where vmlaunch fails and the checks inside the "if"
  branch of vmcs_intel_x64::launch all succeed is tested with
  this commit.

- Remove unused static vmwrite, write_msr functions and add
  tests in order to get full coverage in vmcs_intel_x64.
@connojd connojd changed the title Add completed vmcs launch test suite Test vmlaunch failure Sep 1, 2016
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 998848f on connojd:master into aacc91e on Bareflank:master.

@rianquinn rianquinn merged commit 9b58419 into Bareflank:master Sep 2, 2016
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.

None yet

3 participants