WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH V2 10/11] libxl_qmp, Introduce libxl__qmp_pci_add

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH V2 10/11] libxl_qmp, Introduce libxl__qmp_pci_add.
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Mon, 24 Oct 2011 16:27:21 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 24 Oct 2011 08:28:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=slPr99Yllz05L/ydI7X8brMccC5NG/h+mrPEbPy4e48=; b=JUpJAVm8sDddsDw1Ux2719FuRueCTdX19Br0H8h00GT+iF6BDiVhs12+0/yRSvbPC8 RvDDh2nETuIxL9BnWK6PlOZZBNWw+4MxpSdYdsTdlPL49zFQApOrY8pnaKqyxnipe2G1 WyPNkD90z/uDT+Mie2y3kUIo8uE/xt0fej57Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1319450467.3385.178.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1319133573-25891-1-git-send-email-anthony.perard@xxxxxxxxxx> <1319133573-25891-11-git-send-email-anthony.perard@xxxxxxxxxx> <1319450467.3385.178.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Oct 24, 2011 at 11:01, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>
>> +    rc = qmp_synchronous_send(qmp, "device_add", &args, NULL, qmp->timeout);
>> +    if (rc == 0) {
>> +        rc = qmp_synchronous_send(qmp, "query-pci", NULL,
>> +                                  &request, qmp->timeout);
>> +        if (rc == 0) {
>> +            rc = request.rc;
>> +        }
>
> Is every caller going to want this behaviour? Perhaps it belongs in
> qmp_sync..._send?

Yes, I think we want to know if the command and the callback have been
a success or not. And, in case we want to know if it's a protocol
error or an error in the callback, then we will just need different
value return.

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>