KVM_GET_SUPPORTED_CPUID should reflect these host CPUID bits. The bits
are already cached in word 12. Give the bits X86_FEATURE names, so
that they can be easily referenced. Hide these bits from
/proc/cpuinfo, since the host kernel makes no use of them at present.
Signed-off-by: Jim Mattson <email address hidden>
Reviewed-by: Sean Christopherson <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Sean Christopherson <email address hidden>
(cherry picked from commit f8df91e73a6827a4569bb56cd53e55b4ea2f5b1f)
Signed-off-by: Michael Reed <email address hidden>
f1bde9d...
by
Linus Torvalds <email address hidden>
x86: don't use REP_GOOD or ERMS for small memory clearing
The modern target to use is FSRS (Fast Short REP STOS), and the other
cases should only be used for bigger areas (ie mainly things like page
clearing).
Signed-off-by: Linus Torvalds <email address hidden>
(cherry picked from commit 20f3337d350c4e1b4ac66d731fd4e98565bf6cc0)
Signed-off-by: Michael Reed <email address hidden>
Device that support DASH may be reseted or powered off during suspend.
So driver needs to handle DASH during system suspend and resume. Or
DASH firmware will influence device behavior and causes network lost.
For devices that support DASH, even DASH is disabled, there may still
exist a default firmware that will influence device behavior.
So driver needs to handle DASH for devices that support DASH, no
matter the DASH status is.
This patch also prepares for "fix network lost after resume on DASH
systems".
Fixes: ee7a1beb9759 ("r8169:call "rtl8168_driver_start" "rtl8168_driver_stop" only when hardware dash function is enabled")
Cc: <email address hidden>
Signed-off-by: ChunHao Lin <email address hidden>
Reviewed-by: Heiner Kallweit <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Jakub Kicinski <email address hidden>
(cherry picked from commit 0ab0c45d8aaea5192328bfa6989673aceafc767c)
Signed-off-by: Aaron Ma <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Thibault Ferrante <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>
Intel Alder Lake-P AHCI controller needs to be added to the mobile
chipsets list in order to have link power management enabled. Without
this the CPU cannot enter lower power C-states making idle power
consumption high.
Cc: Koba Ko <email address hidden>
Signed-off-by: Mika Westerberg <email address hidden>
Signed-off-by: Damien Le Moal <email address hidden>
(cherry picked from commit b8b8b4e0c052b2c06e1c4820a8001f4e0f77900f)
Signed-off-by: Koba Ko <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Acked-by: Roxana Nicolescu <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>
Enable VFIO zPCI pass-through for s390x (CONFIG_VFIO_PCI_ZDEV_KVM=y),
to allow pass-through of any kind of s390x-specific vfio-pci devices,
like RoCE devices, ISM devices, NVMe drives.
Signed-off-by: Frank Heimes <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>
Some devices are reporting controller ready mode support, but return 0
for CRTO. These devices require a much higher time to ready than that,
so they are failing to initialize after the driver starter preferring
that value over CAP.TO.
The spec requires that CAP.TO match the appropritate CRTO value, or be
set to 0xff if CRTO is larger than that. This means that CAP.TO can be
used to validate if CRTO is reliable, and provides an appropriate
fallback for setting the timeout value if not. Use whichever is larger.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217863
Reported-by: Cláudio Sampaio <email address hidden>
Reported-by: Felix Yan <email address hidden>
Tested-by: Felix Yan <email address hidden>
Based-on-a-patch-by: Felix Yan <email address hidden>
Cc: <email address hidden>
Signed-off-by: Keith Busch <email address hidden>
(cherry picked from commit 6cc834ba62998c65c42d0c63499bdd35067151ec)
Signed-off-by: You-Sheng Yang <email address hidden>
Acked-by: Emil Renner Berthing <email address hidden>
Acked-by: Andrea Righi <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>
As a result, the host thinks that the VM is not an open-source OS, and it's not Linux. Consequently, the "VM Availability" fron Azure portal is 0 (unhealthy): some users rely on the info to manage their VMs, e.g. if the VM is erroneously reported "unhealthy", the VM may be killed and re-created, and the new VM is still "unhealthy", and the VM may be killed and re-created again...
Fixes commit 5dd24f2df328 ('UBUNTU: SAUCE: (no-up) hv: Supply vendor ID and package ABI')
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>