Skip to content

handle KVM indirect calls #74

Description

@rikvanriel

__vmx_handle_exit() has a table of function calls that semcode currently fails to handle:

    exit_handler_index = array_index_nospec((u16)exit_reason.basic,
                                            kvm_vmx_max_exit_handlers);
    if (!kvm_vmx_exit_handlers[exit_handler_index])
            goto unexpected_vmexit;

    return kvm_vmx_exit_handlers[exit_handler_index](vcpu);

Both kvm_handle_invalid_op and handle_vmx_construction are called through the table above, but semcode doesn't know:

semcode> callers kvm_handle_invalid_op
Finding all functions that call: kvm_handle_invalid_op

=== Direct Callers ===
1 functions directly call 'kvm_handle_invalid_op':

  1. kvm_emulate_monitor_mwait
    semcode> callers handle_vmx_instruction
    Finding all functions that call: handle_vmx_instruction
    Info: No functions call 'handle_vmx_instruction'

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions