From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH] switch hypercall restart indication from -EAGAIN to -ERESTART Date: Thu, 15 May 2014 12:56:15 +0100 Message-ID: <5374C77F02000078000129B2@mail.emea.novell.com> References: <5370EDB40200007800011718@mail.emea.novell.com> <20140515112409.GD40104@deinos.phlegethon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WkuHC-0000Vm-2a for xen-devel@lists.xenproject.org; Thu, 15 May 2014 11:56:42 +0000 In-Reply-To: <20140515112409.GD40104@deinos.phlegethon.org> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan Cc: Kevin Tian , Keir Fraser , Jun Nakajima , Ian Jackson , Eddie Dong , Ian Campbell , Stefano Stabellini , suravee.suthikulpanit@amd.com, xen-devel , Aravind Gopalakrishnan , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org >>> On 15.05.14 at 13:24, wrote: > Some of the paths are a bit complex now, e.g. a preemption > point being reported as EINTR by __put_page_type(), translated to > ERESTART by relinquish_memory(), then to EAGAIN by domain_kill(). That second conversion I expect to go away anyway - we shouldn't really rely on the tools to do the hypercall re-invocations. I've got this as part of another domctl/XSA-77 follow-up patch already. > Are there cases where we want to return EINTR to the guest, or could > we maybe use it everywhere and drop ERESTART? No, we need two distinct error codes on these paths. For now we never need to return -EINTR to the guest (and for now I also can't see when/why we would), but we'd have to convert these too should the need arise. Jan