linux-kernel - [RFC PATCH 0/3] Avoid soft lockup message when KVM is stopped by host

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1312381501-27746-1-git-send-email-emunson@mgebm.net>
Date:	Wed,  3 Aug 2011 10:24:58 -0400
From:	Eric B Munson <emunson@...bm.net>
To:	kvm@...r.kernel.org
Cc:	kvm-ia64@...r.kernel.org, kvm-ppc@...r.kernel.org, avi@...hat.com,
	riel@...hat.com, glommer@...hat.com, linux-kernel@...r.kernel.org,
	aliguori@...ibm.com, raharper@...ibm.com,
	Eric B Munson <emunson@...bm.net>
Subject: [RFC PATCH 0/3] Avoid soft lockup message when KVM is stopped by host

This set is just a rough first pass at avoiding soft lockup warnings when a host
pauses the execution of a guest.  A flag is set by the host in the shared page
used for the pvclock when the host goes to stop the guest.  When the guest
resumes and detects a soft lockup, this flag is checked and cleared and the soft
lockup message is skipped.

This currently breaks the build for non-x86 architectures but part of what I am
looking for here is how to go about adding the function stubs for everything
else.

Eric B Munson (3):
  Add flag to indicate that a vm was stopped by the host
  Add functions to check if the host has stopped the vm
  Add check for suspended vm in softlockup detector

 arch/x86/include/asm/pvclock-abi.h |    1 +
 arch/x86/include/asm/pvclock.h     |    3 +++
 arch/x86/kernel/kvmclock.c         |   12 ++++++++++++
 kernel/watchdog.c                  |   11 +++++++++++
 4 files changed, 27 insertions(+), 0 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/