From: "Luis R. Rodriguez" Subject: Re: [Xen-devel] [RFC v4 0/2] x86/xen: add xen hypercall preemption Date: Fri, 23 Jan 2015 19:58:45 +0100 Message-ID: <20150123185845.GY17887@wotan.suse.de> References: <1421972951-3940-1-git-send-email-mcgrof@do-not-panic.com> <54C235AD.5010202@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Luis R. Rodriguez" , konrad.wilk@oracle.com, boris.ostrovsky@oracle.com, xen-devel@lists.xenproject.org, kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, rostedt@goodmis.org, paulmck@linux.vnet.ibm.com To: David Vrabel Return-path: Content-Disposition: inline In-Reply-To: <54C235AD.5010202@citrix.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, Jan 23, 2015 at 11:51:09AM +0000, David Vrabel wrote: > On 23/01/15 00:29, Luis R. Rodriguez wrote: > > From: "Luis R. Rodriguez" > > > > This v4 addresses some of the cleanups recommended and adds > > tracing option for when we do actually preempt a hypercall. > > I kept the NOKPROBE_SYMBOL() for now but did remove the 'notrace' > > stuff. > > > > This goes out as RFC still as I have not been able to test 32-bit. > > Can anyone test that or at least confirm that the 32-bit point > > we do the upcall is definitely not on the IRQ stack? > > You can omit fixing this for 32-bit guests (provided you note as such in > the commit message). I'll be happy to do that. Luis