linux-kernel - Re: [PATCH 0/5 V5] 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Dec 2011 11:48:36 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Eric B Munson <emunson@...bm.net>
CC:	mingo@...hat.com, hpa@...or.com, arnd@...db.de,
	ryanh@...ux.vnet.ibm.com, aliguori@...ibm.com, mtosatti@...hat.com,
	jeremy.fitzhardinge@...rix.com, levinsasha928@...il.com,
	Jan Kiszka <jan.kiszka@...mens.com>, kvm@...r.kernel.org,
	linux-arch@...r.kernel.org, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5 V5] Avoid soft lockup message when KVM is stopped
 by host

On 12/14/2011 07:58 PM, Eric B Munson wrote:
> > I don't think you should see a guest softlockup if the host is
> > overloaded.  Nor should you see it due to a long live migration pause,
> > or STOP/CONT.  You should see a guest softlockup if it is spinning due
> > to a guest bug, and not for any other reason.
> > 
> > I think we need a mix of the ioctl (for STOP/CONT and voluntary pauses,
> > like live migration or qemu stop/cont) and preempt notifiers (together
> > with a check for TASK_RUNNING/TASK_UNINTERRUPTIBLE, for scheduling or
> > swap delays)
> > 
>
> Do you want the preemption notifier work in before you will consider merging
> this set, or can that be a follow on?

Yes please.

-- 
error compiling committee.c: too many arguments to function

--
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/