From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Luis R. Rodriguez" Subject: Re: [RFC v4 1/2] x86/xen: add xen_is_preemptible_hypercall() Date: Tue, 27 Jan 2015 02:45:54 +0100 Message-ID: <20150127014554.GC17887@wotan.suse.de> References: <1421972951-3940-1-git-send-email-mcgrof@do-not-panic.com> <1421972951-3940-2-git-send-email-mcgrof@do-not-panic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Luis R. Rodriguez" , David Vrabel , Konrad Rzeszutek Wilk , Boris Ostrovsky , "xen-devel@lists.xenproject.org" , "linux-kernel@vger.kernel.org" , X86 ML , kvm list , Paul McKenney , Steven Rostedt , Borislav Petkov , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Masami Hiramatsu , Jan Beulich To: Andy Lutomirski Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Thu, Jan 22, 2015 at 05:40:45PM -0800, Andy Lutomirski wrote: > On Thu, Jan 22, 2015 at 4:29 PM, Luis R. Rodriguez > wrote: > > From: "Luis R. Rodriguez" > > > > On kernels with voluntary or no preemption we can run > > into situations where a hypercall issued through userspace > > will linger around as it addresses sub-operatiosn in kernel > > context (multicalls). Such operations can trigger soft lockup > > detection. > > Looks reasonable. I'll add a reviewed-by... LUis