All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/4] Add Error **errp for xen_host_pci_device_get()
Date: Tue, 5 Jan 2016 15:23:23 +0800	[thread overview]
Message-ID: <568B6F6B.3020800@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601041510130.19710@kaball.uk.xensource.com>



On 01/04/2016 11:15 PM, Stefano Stabellini wrote:
> On Sun, 27 Dec 2015, Cao jin wrote:
>> To catch the error msg. Also modify the caller
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>
> This looks much better, thanks.
>
>
[...]
>>
>> -int xen_host_pci_device_get(XenHostPCIDevice *d, uint16_t domain,
>> -                            uint8_t bus, uint8_t dev, uint8_t func)
>> +void xen_host_pci_device_get(XenHostPCIDevice *d, uint16_t domain,
>> +                            uint8_t bus, uint8_t dev, uint8_t func,
>> +                            Error **errp)
>>   {
>>       unsigned int v;
>> -    int rc = 0;
>>
>>       d->config_fd = -1;
>>       d->domain = domain;
>> @@ -353,43 +360,48 @@ int xen_host_pci_device_get(XenHostPCIDevice *d, uint16_t domain,
>>       d->dev = dev;
>>       d->func = func;
>>
>> -    rc = xen_host_pci_config_open(d);
>> -    if (rc) {
>> +    xen_host_pci_config_open(d, errp);
>> +    if (*errp) {
>
> I think that errp could be NULL, therefore the right way to do this is:
>
>      Error *err = NULL;
>      foo(arg, &err);
>      if (err) {
>          handle the error...
>          error_propagate(errp, err);
>      }
>
> see the comment at the beginning of include/qapi/error.h.
>

Hi stefano,

     I read that comment, and find something maybe new:

"errp could be NULL", I think it is saying, if we are in a .realize() 
function, yes, *errp* maybe NULL, but reality is, here is the callee of 
.realize(), and we defined a local variable: Error *local_err = NULL in 
.realize() and passed it to all the callee, so, theoretically *errp* 
won`t be NULL. so the way you said above is suitable in .realize() IMHO, 
and I also did it in that way.

comment also says:

  * Receive an error and pass it on to the caller:
  *     Error *err = NULL;
  *     foo(arg, &err);
  *     if (err) {
  *         handle the error...
  *         error_propagate(errp, err);
  *     }
  * where Error **errp is a parameter, by convention the last one.

If I understand the last sentence well, the Error **errp in .realize() 
prototype is *the last one*, so we could call error_propagate(errp, err) 
only in .realize()

The comment also says:

  * But when all you do with the error is pass it on, please use
  *     foo(arg, errp);
  * for readability."

We just pass error on in all the callees, so I guess I also did as 
comment suggest?

How do you think?

[...]
-- 
Yours Sincerely,

Cao Jin

  parent reply	other threads:[~2016-01-05  7:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27 13:40 [Qemu-devel] [PATCH v2 0/4] Convert to realize() Cao jin
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 1/4] Add Error **errp for xen_host_pci_device_get() Cao jin
2016-01-04 15:15   ` Stefano Stabellini
2016-01-05  5:31     ` Cao jin
2016-01-05  7:23     ` Cao jin [this message]
2016-01-05 10:40       ` Stefano Stabellini
2016-01-05 12:41         ` Cao jin
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 2/4] Add Error **errp for xen_pt_setup_vga() Cao jin
2016-01-04 15:18   ` Stefano Stabellini
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 3/4] Add Error **errp for xen_pt_config_init() Cao jin
2016-01-04 15:23   ` Stefano Stabellini
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 4/4] Xen PCI passthru: convert to realize() Cao jin
2016-01-04 15:29   ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=568B6F6B.3020800@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.