lkml.org 
[lkml]   [2009]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 2/5] KVM: SVM: don't copy exit_int_info on nested vmrun
    Date
    The exit_int_info field is only written by the hardware and
    never read. So it does not need to be copied on a vmrun
    emulation.

    Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
    ---
    arch/x86/kvm/svm.c | 2 --
    1 files changed, 0 insertions(+), 2 deletions(-)

    diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
    index 668460c..80f5309 100644
    --- a/arch/x86/kvm/svm.c
    +++ b/arch/x86/kvm/svm.c
    @@ -1790,8 +1790,6 @@ static bool nested_svm_vmrun(struct vcpu_svm *svm)
    svm->nested.intercept = nested_vmcb->control.intercept;

    force_new_asid(&svm->vcpu);
    - svm->vmcb->control.exit_int_info = nested_vmcb->control.exit_int_info;
    - svm->vmcb->control.exit_int_info_err = nested_vmcb->control.exit_int_info_err;
    svm->vmcb->control.int_ctl = nested_vmcb->control.int_ctl | V_INTR_MASKING_MASK;
    if (nested_vmcb->control.int_ctl & V_IRQ_MASK) {
    nsvm_printk("nSVM Injecting Interrupt: 0x%x\n",
    --
    1.6.3.3



    \
     
     \ /
      Last update: 2009-09-16 15:33    [W:0.024 / U:90.232 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site