From: Eric Auger <eric.auger@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>, qemu-devel@nongnu.org
Cc: "Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 01/17] vfio: Make vfio_devices_dma_logging_start() return bool
Date: Mon, 17 Jun 2024 15:55:27 +0200 [thread overview]
Message-ID: <d830b55b-b45c-43cc-aee7-cd996985c4f3@redhat.com> (raw)
In-Reply-To: <c998c442-f873-4409-804a-fcba1f53efc2@redhat.com>
Hi Cédric,
On 6/17/24 14:34, Cédric Le Goater wrote:
> Hello Eric,
>
> On 6/17/24 1:31 PM, Eric Auger wrote:
>> Hi Cédric,
>>
>> On 6/17/24 08:33, Cédric Le Goater wrote:
>>> Since vfio_devices_dma_logging_start() takes an 'Error **' argument,
>>> best practices suggest to return a bool. See the api/error.h Rules
>>> section. It will simplify potential changes coming after.
>>
>>
>> As I already mentionned the Rules section does not say that, as far as I
>> understand:
>> It is allowed to either return a bool, a pointer-value, an integer,
>> along with an error handle:
>>
>> "
>> * • bool-valued functions return true on success / false on failure,
>> * • pointer-valued functions return non-null / null pointer, and
>> * • integer-valued functions return non-negative / negative.
>> "
>>
>> Personally I don't like much returning a bool as I think it rather
>> complexifies the code and to me that kind of change is error prone.
>
> Returning an int could be misleading too, since there are multiple ways
> it could be interpreted. You can find in QEMU routines returning -1 for
> error which is later used as an errno :/
yes no good!
>
> The error framework in QEMU provides a way to to save and return any
> kind of errors, using the error_seg_*() routines. I tend to prefer
> the basic approach: return fail or pass and use the Error parameter
> for details.
>
> Now, the problem, as always, is doing the conversion in all the
> code. This is probably why people, with a kernel background, find
> it confusing.
>
>
>>
>>
>>>
>>> vfio_container_set_dirty_page_tracking() could be modified in the same
>>> way but the errno value can be saved in the migration stream when
>>> called from vfio_listener_log_global_stop().
>>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>>> Reviewed-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> ---
>>> hw/vfio/common.c | 14 +++++++-------
>>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
>>> index
>>> 9e4c0cc95ff90209d3e8184035af0806a2bf890b..d48cd9b9361a92d184e423ffc60aabaff40fb487
>>> 100644
>>> --- a/hw/vfio/common.c
>>> +++ b/hw/vfio/common.c
>>> @@ -1020,7 +1020,7 @@ static void
>>> vfio_device_feature_dma_logging_start_destroy(
>>> g_free(feature);
>>> }
>>> -static int vfio_devices_dma_logging_start(VFIOContainerBase
>>> *bcontainer,
>>> +static bool vfio_devices_dma_logging_start(VFIOContainerBase
>>> *bcontainer,
>>> Error **errp)
>>> {
>>> struct vfio_device_feature *feature;
>>> @@ -1033,7 +1033,7 @@ static int
>>> vfio_devices_dma_logging_start(VFIOContainerBase *bcontainer,
>>> &ranges);
>>> if (!feature) {
>>> error_setg_errno(errp, errno, "Failed to prepare DMA
>>> logging");
>>> - return -errno;
>>> + return false;
>>> }
>>> QLIST_FOREACH(vbasedev, &bcontainer->device_list,
>>> container_next) {
>>> @@ -1058,7 +1058,7 @@ out:
>>> vfio_device_feature_dma_logging_start_destroy(feature);
>>> - return ret;
>>> + return ret == 0;
>>> }
>>> static bool vfio_listener_log_global_start(MemoryListener
>>> *listener,
>>> @@ -1067,18 +1067,18 @@ static bool
>>> vfio_listener_log_global_start(MemoryListener *listener,
>>> ERRP_GUARD();
>>> VFIOContainerBase *bcontainer = container_of(listener,
>>> VFIOContainerBase,
>>> listener);
>>> - int ret;
>>> + bool ret;
>>> if (vfio_devices_all_device_dirty_tracking(bcontainer)) {
>>> ret = vfio_devices_dma_logging_start(bcontainer, errp);
>>> } else {
>>> - ret = vfio_container_set_dirty_page_tracking(bcontainer,
>>> true, errp);
>>> + ret = vfio_container_set_dirty_page_tracking(bcontainer,
>>> true, errp) == 0;
>>
>> why vfio_container_set_dirty_page_tracking(bcontainer, true, errp)
>> doesn't return a bool then?
>
> The errno value can be saved in the migration stream when called from
> vfio_listener_log_global_stop(). So this would require changes in the
> migration subsystem, like we did for vfio_listener_log_global_start().
OK
so although I am not a big fan of that kind of change and once
highlighted this is not mandated by the error.h doc, please feel free to
add my
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
>
> Thanks,
>
> C.
>
>
>
>
>
>>
>> Eric
>>
>>> }
>>> - if (ret) {
>>> + if (!ret) {
>>> error_prepend(errp, "vfio: Could not start dirty page
>>> tracking - ");
>>> }
>>> - return !ret;
>>> + return ret;
>>> }
>>> static void vfio_listener_log_global_stop(MemoryListener *listener)
>>
>
next prev parent reply other threads:[~2024-06-17 13:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 6:33 [PATCH v2 00/17] vfio: QOMify VFIOContainer Cédric Le Goater
2024-06-17 6:33 ` [PATCH v2 01/17] vfio: Make vfio_devices_dma_logging_start() return bool Cédric Le Goater
2024-06-17 11:31 ` Eric Auger
2024-06-17 12:34 ` Cédric Le Goater
2024-06-17 13:55 ` Eric Auger [this message]
2024-06-17 6:33 ` [PATCH v2 02/17] vfio: Remove unused declarations from vfio-common.h Cédric Le Goater
2024-06-17 11:32 ` Eric Auger
2024-06-17 6:33 ` [PATCH v2 03/17] vfio/common: Move dirty tracking ranges update to helper Cédric Le Goater
2024-06-17 11:39 ` Eric Auger
2024-06-18 11:22 ` Cédric Le Goater
2024-06-17 6:33 ` [PATCH v2 04/17] vfio/common: Extract vIOMMU code from vfio_sync_dirty_bitmap() Cédric Le Goater
2024-06-17 14:00 ` Eric Auger
2024-06-18 11:22 ` Cédric Le Goater
2024-06-17 6:33 ` [PATCH v2 05/17] vfio/container: Introduce vfio_address_space_insert() Cédric Le Goater
2024-06-17 14:04 ` Eric Auger
2024-06-18 11:27 ` Cédric Le Goater
2024-06-17 6:33 ` [PATCH v2 06/17] vfio/container: Simplify vfio_container_init() Cédric Le Goater
2024-06-17 14:25 ` Eric Auger
2024-06-18 11:29 ` Cédric Le Goater
2024-06-17 6:33 ` [PATCH v2 07/17] vfio/container: Modify vfio_get_iommu_type() to use a container fd Cédric Le Goater
2024-06-17 14:26 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 08/17] vfio/container: Introduce vfio_get_iommu_class_name() Cédric Le Goater
2024-06-17 14:29 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 09/17] vfio/container: Introduce vfio_create_container() Cédric Le Goater
2024-06-17 14:29 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 10/17] vfio/container: Discover IOMMU type before creating the container Cédric Le Goater
2024-06-17 14:39 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 11/17] vfio/container: Change VFIOContainerBase to use QOM Cédric Le Goater
2024-06-17 15:26 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 12/17] vfio/container: Switch to QOM Cédric Le Goater
2024-06-17 15:26 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 13/17] vfio/container: Introduce an instance_init() handler Cédric Le Goater
2024-06-17 15:27 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 14/17] vfio/container: Remove VFIOContainerBase::ops Cédric Le Goater
2024-06-17 15:27 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 15/17] vfio/container: Remove vfio_container_init() Cédric Le Goater
2024-06-17 15:28 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 16/17] vfio/container: Introduce vfio_iommu_legacy_instance_init() Cédric Le Goater
2024-06-17 15:29 ` Eric Auger
2024-06-17 6:34 ` [PATCH v2 17/17] vfio/container: Move vfio_container_destroy() to an instance_finalize() handler Cédric Le Goater
2024-06-17 10:24 ` Duan, Zhenzhong
2024-06-17 15:30 ` Eric Auger
2024-06-17 16:22 ` [PATCH v2 00/17] vfio: QOMify VFIOContainer Eric Auger
2024-06-18 11:45 ` Cédric Le Goater
2024-06-24 21:17 ` Cédric Le Goater
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=d830b55b-b45c-43cc-aee7-cd996985c4f3@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=clg@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).