1. 19 12月, 2013 1 次提交
  2. 07 12月, 2013 1 次提交
    • L
      ACPI: Clean up inclusions of ACPI header files · 8b48463f
      Lv Zheng 提交于
      Replace direct inclusions of <acpi/acpi.h>, <acpi/acpi_bus.h> and
      <acpi/acpi_drivers.h>, which are incorrect, with <linux/acpi.h>
      inclusions and remove some inclusions of those files that aren't
      necessary.
      
      First of all, <acpi/acpi.h>, <acpi/acpi_bus.h> and <acpi/acpi_drivers.h>
      should not be included directly from any files that are built for
      CONFIG_ACPI unset, because that generally leads to build warnings about
      undefined symbols in !CONFIG_ACPI builds.  For CONFIG_ACPI set,
      <linux/acpi.h> includes those files and for CONFIG_ACPI unset it
      provides stub ACPI symbols to be used in that case.
      
      Second, there are ordering dependencies between those files that always
      have to be met.  Namely, it is required that <acpi/acpi_bus.h> be included
      prior to <acpi/acpi_drivers.h> so that the acpi_pci_root declarations the
      latter depends on are always there.  And <acpi/acpi.h> which provides
      basic ACPICA type declarations should always be included prior to any other
      ACPI headers in CONFIG_ACPI builds.  That also is taken care of including
      <linux/acpi.h> as appropriate.
      Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Matthew Garrett <mjg59@srcf.ucam.org>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Acked-by: Bjorn Helgaas <bhelgaas@google.com> (drivers/pci stuff)
      Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> (Xen stuff)
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      8b48463f
  3. 20 10月, 2013 1 次提交
  4. 18 10月, 2013 1 次提交
  5. 17 10月, 2013 2 次提交
  6. 27 9月, 2013 16 次提交
  7. 26 9月, 2013 1 次提交
  8. 31 8月, 2013 1 次提交
  9. 28 8月, 2013 1 次提交
  10. 02 8月, 2013 1 次提交
  11. 27 7月, 2013 2 次提交
  12. 17 7月, 2013 3 次提交
  13. 25 6月, 2013 2 次提交
  14. 19 6月, 2013 1 次提交
  15. 04 6月, 2013 1 次提交
    • K
      Drivers: hv: vmbus: Implement multi-channel support · e68d2971
      K. Y. Srinivasan 提交于
      Starting with Win8, the host supports multiple sub-channels for a given
      device. As in the past, the initial channel offer specifies the device and
      is associated with both the type and the instance GUIDs. For performance
      critical devices, the host may support multiple sub-channels. The sub-channels
      share the same type and instance GUID as the primary channel. The number of
      sub-channels offerrred to the guest depends on the number of virtual CPUs
      assigned to the guest. The guest can request the creation of these sub-channels
      and once created and opened, the guest can distribute the traffic across all
      the channels (the primary and the sub-channels). A request sent on a sub-channel
      will have the response delivered on the same sub-channel.
      
      At channel (sub-channel) creation we bind the channel interrupt to a CPU and
      with this sub-channel support we will be able to spread the interrupt load
      of a given device across all available CPUs.
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Reviewed-by: NHaiyang Zhang <haiyangz@microsoft.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      e68d2971
  16. 22 5月, 2013 1 次提交
  17. 02 4月, 2013 1 次提交
  18. 30 3月, 2013 2 次提交
    • K
      Drivers: hv: Notify the host of permanent hot-add failures · 7f4f2302
      K. Y. Srinivasan 提交于
      If memory hot-add fails with the error -EEXIST, then this is a permanent
      failure. Notify the host of this information, so the host will not attempt
      hot-add again. If the failure were a transient failure, host will attempt
      a hot-add after some delay.
      
      In this version of the patch, I have added some additional comments
      to clarify how the host treats different failure conditions.
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7f4f2302
    • K
      Drivers: hv: balloon: Support 2M page allocations for ballooning · f766dc1e
      K. Y. Srinivasan 提交于
      On Hyper-V it will be very efficient to use 2M allocations in the guest as this
      makes the ballooning protocol with the host that much more efficient. Hyper-V
      uses page ranges (start pfn : number of pages) to specify memory being moved
      around and with 2M pages this encoding can be very efficient. However, when
      memory is returned to the guest, the host does not guarantee any granularity.
      To deal with this issue, split the page soon after a successful 2M allocation
      so that this memory can potentially be freed as 4K pages.
      
      If 2M allocations fail, we revert to 4K allocations.
      
      In this version of the patch, based on the feedback from Michal Hocko
      <mhocko@suse.cz>, I have added some additional commentary to the patch
      description.
      
      Cc: Michal Hocko <mhocko@suse.cz>
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f766dc1e
  19. 29 3月, 2013 1 次提交