From: "Luis R. Rodriguez" Subject: Re: [Xen-devel] [PATCH v5 0/2] x86/xen: add xen hypercall preemption Date: Thu, 5 Feb 2015 19:15:52 +0100 Message-ID: <20150205181551.GW19988@wotan.suse.de> References: <1422323467-16713-1-git-send-email-mcgrof@do-not-panic.com> <54D36653.7010207@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: <54D36653.7010207@citrix.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Thu, Feb 05, 2015 at 12:47:15PM +0000, David Vrabel wrote: > On 27/01/15 01:51, Luis R. Rodriguez wrote: > > From: "Luis R. Rodriguez" > > > > This v5 nukes tracing as David said it was useless, it also > > only adds support for 64-bit as its the only thing I can test, > > and slightly modifies the documentation in code as to why we > > want this. The no krobe thing is left in place as I haven't > > heard confirmation its kosher to remove it. > > FYI, I went back an reviewed my last v4 patch and folded the > xen_end_upcall() change into it instead. > > http://lists.xen.org/archives/html/xen-devel/2015-02/msg00682.html > > This will be easier for arm/arm64 to make use of in the future since > there are fewer arch-specific changes. I had taken similar approach first and determined using pt_regs was safer after advice from Andy. I'll provide feedback on your new patchset. Luis