From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: [PATCH] switch hypercall restart indication from
 -EAGAIN to -ERESTART
Date: Thu, 15 May 2014 13:07:56 +0100
Message-ID: <5374CA3C02000078000129FF@mail.emea.novell.com>
References: <5370EDB40200007800011718@mail.emea.novell.com>
	<20140515112409.GD40104@deinos.phlegethon.org>
	<5374C77F02000078000129B2@mail.emea.novell.com>
	<20140515120116.GA39957@deinos.phlegethon.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <JBeulich@suse.com>) id 1WkuS7-0001hJ-HR
	for xen-devel@lists.xenproject.org; Thu, 15 May 2014 12:07:59 +0000
In-Reply-To: <20140515120116.GA39957@deinos.phlegethon.org>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Tim Deegan <tim@xen.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>, Jun Nakajima <jun.nakajima@intel.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Eddie Dong <eddie.dong@intel.com>, Ian Campbell <Ian.Campbell@eu.citrix.com>, Stefano Stabellini <stefano.stabellini@citrix.com>, suravee.suthikulpanit@amd.com, xen-devel <xen-devel@lists.xenproject.org>, Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
List-Id: xen-devel@lists.xenproject.org

>>> On 15.05.14 at 14:01, <tim@xen.org> wrote:
> At 12:56 +0100 on 15 May (1400154975), Jan Beulich wrote:
>> >>> On 15.05.14 at 13:24, <tim@xen.org> wrote:
>> > 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.
> 
> I didn't really understand that.  Do you mean that there's a reason to
> have both EINTR and ERESTART even though we don't return EINTR to
> guests, or that you want to keep them separate in case we ever do
> want to return EINTR?

The former.

Jan