[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 7/9] util/vfio-helpers: Have qemu_vfio_dma_map() propagate Er
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH 7/9] util/vfio-helpers: Have qemu_vfio_dma_map() propagate Error |
Date: |
Wed, 25 Aug 2021 15:08:17 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 8/25/21 1:34 PM, Klaus Jensen wrote:
> On Aug 24 16:11, Philippe Mathieu-Daudé wrote:
>> Now that all qemu_vfio_dma_map() callers provide an Error* argument,
>> fill it with relevant / more descriptive message. Reduce 'ret'
>> (returned value) scope by returning errno directly to simplify
>> (removing the goto / 'out' label).
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> block/nvme.c | 1 +
>> util/vfio-helpers.c | 31 ++++++++++++++-----------------
>> 2 files changed, 15 insertions(+), 17 deletions(-)
>>
>> diff --git a/block/nvme.c b/block/nvme.c
>> index 663e5d918fa..80546b0babd 100644
>> --- a/block/nvme.c
>> +++ b/block/nvme.c
>> @@ -240,6 +240,7 @@ static NVMeQueuePair
>> *nvme_create_queue_pair(BDRVNVMeState *s,
>> r = qemu_vfio_dma_map(s->vfio, q->prp_list_pages, bytes,
>> false, &prp_list_iova, errp);
>> if (r) {
>> + error_prepend(errp, "Cannot map buffer for DMA: ");
>
> Ah. Here is the missing error message that I noticed in patch 2 ;)
So I should use error_setg() in patch 2 and replace it with
error_prepend() here? I'm trying to address Eric's comments
from:
https://lore.kernel.org/qemu-devel/2cbd5471-4611-ae6b-d79f-db6ff19db5bf@redhat.com/
https://lore.kernel.org/qemu-devel/bd1cc1c9-3553-d252-3ca9-a23bc1035170@redhat.com/
>
>> goto fail;
>> }
>> q->free_req_head = -1;
>> diff --git a/util/vfio-helpers.c b/util/vfio-helpers.c
>> index 3e1a49bea15..f4c16e1dae5 100644
>> --- a/util/vfio-helpers.c
>> +++ b/util/vfio-helpers.c
>> @@ -729,7 +729,6 @@ qemu_vfio_find_temp_iova(QEMUVFIOState *s, size_t size,
>> uint64_t *iova)
>> int qemu_vfio_dma_map(QEMUVFIOState *s, void *host, size_t size,
>> bool temporary, uint64_t *iova, Error **errp)
>> {
>> - int ret = 0;
>> int index;
>> IOVAMapping *mapping;
>> uint64_t iova0;
>> @@ -742,32 +741,34 @@ int qemu_vfio_dma_map(QEMUVFIOState *s, void *host,
>> size_t size,
>> if (mapping) {
>> iova0 = mapping->iova + ((uint8_t *)host - (uint8_t
>> *)mapping->host);
>> } else {
>> + int ret;
>> +
>> if (s->high_water_mark - s->low_water_mark + 1 < size) {
>> - ret = -ENOMEM;
>> - goto out;
>> + error_setg(errp, "iova exhausted (water mark reached)");
>> + return -ENOMEM;
>> }
>> if (!temporary) {
>> - if (qemu_vfio_find_fixed_iova(s, size, &iova0)) {
>> - ret = -ENOMEM;
>> - goto out;
>> + if (qemu_vfio_find_fixed_iova(s, size, &iova0) < 0) {
>> + error_setg(errp, "iova range not found");
>> + return -ENOMEM;
>
> Just curious.
>
> Previously this did error_setg_errno in out. Why don't we want to do that
> here?
I didn't thought about it but indeed you are right.
Thanks for the review!
Phil.
- [PATCH 1/9] block/nvme: Use safer trace format string, (continued)
- [PATCH 1/9] block/nvme: Use safer trace format string, Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 2/9] block/nvme: Have nvme_create_queue_pair() report errors consistently, Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 3/9] util/vfio-helpers: Let qemu_vfio_verify_mappings() use error_report(), Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 4/9] util/vfio-helpers: Replace qemu_mutex_lock() calls with QEMU_LOCK_GUARD, Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 6/9] util/vfio-helpers: Pass Error handle to qemu_vfio_dma_map(), Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 7/9] util/vfio-helpers: Have qemu_vfio_dma_map() propagate Error, Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 5/9] util/vfio-helpers: Remove unreachable code in qemu_vfio_dma_map(), Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 8/9] util/vfio-helpers: Let qemu_vfio_do_mapping() propagate Error, Philippe Mathieu-Daudé, 2021/08/24
- [PATCH 9/9] block/nvme: Only report VFIO error on failed retry, Philippe Mathieu-Daudé, 2021/08/24