16 Mar, 2013

1 commit


28 Feb, 2013

1 commit

  • Use the infrastructure for delivering VMBUS interrupts using a
    special vector. With this patch, we can now properly handle
    the VMBUS interrupts that can be delivered on any CPU. Also,
    turn on interrupt load balancing as well.

    This patch requires the infrastructure that was implemented in the patch:
    X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts

    Signed-off-by: K. Y. Srinivasan
    Signed-off-by: Greg Kroah-Hartman

    K. Y. Srinivasan
     

18 Jan, 2013

7 commits


18 Aug, 2012

1 commit

  • We wait for about 5 seconds for the success of the hyperv registration even if
    we were not in hyperv platform. This is suboptimal, so the patch check the cpuid
    in the beginning of hv_acpi_init() instead of in vmbus_bus_init() to fail the
    probing immediately.

    Signed-off-by: Jason Wang
    Cc: Haiyang Zhang
    Acked-by: K. Y. Srinivasan
    Signed-off-by: Greg Kroah-Hartman

    Jason Wang
     

14 Aug, 2012

1 commit

  • The current guest ID string in use in vmbus driver does not conform
    to the MSFT guidelines on guest ID. MSFT currently does not specify
    Linux specific guidelines. MSFT however has plans to publish Linux
    specific guidelines. This implementation conforms to the yet unpublished
    Linux specific guidelines for guest ID. This implementation also broadly
    conforms to the current guidelines as well.

    Signed-off-by: K. Y. Srinivasan
    Reviewed-by: Haiyang Zhang
    Cc: Bjørn Mork
    Cc: Paolo Bonzini
    Signed-off-by: Greg Kroah-Hartman

    K. Y. Srinivasan
     

10 Apr, 2012

1 commit

  • This function returns negative error codes, but because the type is u16
    they get truncated into positive numbers. It doesn't look like the
    callers care, but we should fix it anyway as a cleanup.

    Signed-off-by: Dan Carpenter
    Signed-off-by: K. Y. Srinivasan
    Signed-off-by: Greg Kroah-Hartman

    Dan Carpenter
     

10 Feb, 2012

1 commit

  • The current code arbirarily limited the number of CPUs the guest could have.
    Change that so that we can support the maximum number of CPUs the guest can
    support. While we use NR_CPUS to size the per-cpu state all we are allocating
    based on NR_CPUS are the pointers to per-cpu state that will be allocatted in
    the context of the initializing CPU. This patch triggers a checkpatch warning
    for the usage of NR_CPU and since all we are allocating a couple of pointers
    per CPU, it should be ok.

    Signed-off-by: K. Y. Srinivasan
    Signed-off-by: Haiyang Zhang
    Signed-off-by: Greg Kroah-Hartman

    K. Y. Srinivasan
     

13 Dec, 2011

2 commits


11 Oct, 2011

2 commits