All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [PATCH v3 11/20] nubus-device: add romfile property for loading declaration ROMs
Date: Thu, 16 Sep 2021 15:06:50 +0200	[thread overview]
Message-ID: <878rzw655h.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <a6857eaa-a0d3-c098-3cda-057ee9fa15a4@amsat.org> ("Philippe =?utf-8?Q?Mathieu-Daud=C3=A9=22's?= message of "Thu, 16 Sep 2021 13:05:41 +0200")

Philippe Mathieu-Daudé <f4bug@amsat.org> writes:

> On 9/16/21 12:05 PM, Mark Cave-Ayland wrote:
>> The declaration ROM is located at the top-most address of the standard slot
>> space.
>> 
>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> ---
>>  hw/nubus/nubus-device.c  | 43 +++++++++++++++++++++++++++++++++++++++-
>>  include/hw/nubus/nubus.h |  6 ++++++
>>  2 files changed, 48 insertions(+), 1 deletion(-)
>
>> @@ -38,10 +43,46 @@ static void nubus_device_realize(DeviceState *dev, Error **errp)
>>      memory_region_add_subregion(&nubus->slot_io, slot_offset,
>>                                  &nd->slot_mem);
>>      g_free(name);
>> +
>> +    /* Declaration ROM */
>> +    if (nd->romfile != NULL) {
>> +        path = qemu_find_file(QEMU_FILE_TYPE_BIOS, nd->romfile);
>> +        if (path == NULL) {
>> +            path = g_strdup(nd->romfile);
>> +        }
>> +
>> +        size = get_image_size(path);
>> +        if (size < 0) {
>> +            error_setg(errp, "failed to find romfile \"%s\"", nd->romfile);
>> +            g_free(path);
>> +            return;
>> +        } else if (size == 0) {
>> +            error_setg(errp, "romfile \"%s\" is empty", nd->romfile);
>> +            g_free(path);
>> +            return;
>> +        } else if (size > NUBUS_DECL_ROM_MAX_SIZE) {
>> +            error_setg(errp, "romfile \"%s\" too large (maximum size 128K)",
>> +                       nd->romfile);
>> +            g_free(path);
>> +            return;
>> +        }
>> +
>> +        name = g_strdup_printf("nubus-slot-%x-declaration-rom", nd->slot);
>> +        memory_region_init_rom(&nd->decl_rom, OBJECT(dev), name, size,
>> +                               &error_fatal);

Is this error expected to happen?

If yes, you should quite probably propagate it.

If no, &error_abort.

>> +        ret = load_image_mr(path, &nd->decl_rom);
>
> load_image_mr() already calls get_image_size(), rom_add_file() and
> qemu_find_file(). *But* it doesn't takes and Error handle, and report
> error using fprintf()...

... except when they don't:

    int load_image_mr(const char *filename, MemoryRegion *mr)
    {
        int size;

        if (!memory_access_is_direct(mr, false)) {
            /* Can only load an image into RAM or ROM */
--->        return -1;
        }

        size = get_image_size(filename);

        if (size < 0 || size > memory_region_size(mr)) {
            return -1;
        }
        if (size > 0) {
            if (rom_add_file_mr(filename, mr, -1) < 0) {
                return -1;
            }
        }
        return size;
    }

Hot mess!

>                          So unfortunately rom_add*() functions are
> kinda outdated and you are doing the right thing to propagate detailled
> errors.

I can't see errors being propagated, only a warn_report()...

>         Therefore:
>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>
>> +        g_free(path);
>> +        if (ret < 0) {
>> +            warn_report("nubus-device: could not load prom '%s'", nd->romfile);

... here.

>> +        }
>> +        memory_region_add_subregion(&nd->slot_mem, NUBUS_SLOT_SIZE - size,
>> +                                    &nd->decl_rom);
>> +    }
>>  }



  reply	other threads:[~2021-09-16 13:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 10:05 [PATCH v3 00/20] nubus: bus, device, bridge, IRQ and address space improvements Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 01/20] nubus-device: rename slot_nb variable to slot Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 02/20] nubus-device: expose separate super slot memory region Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 03/20] nubus-device: add device slot parameter Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 04/20] nubus: use bitmap to manage available slots Mark Cave-Ayland
2021-09-16 10:36   ` Philippe Mathieu-Daudé
2021-09-16 10:05 ` [PATCH v3 05/20] nubus: move slot bitmap checks from NubusDevice realize() to BusClass check_address() Mark Cave-Ayland
2021-09-16 10:37   ` Philippe Mathieu-Daudé
2021-09-16 10:05 ` [PATCH v3 06/20] nubus: implement BusClass get_dev_path() Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 07/20] nubus: add trace-events for empty slot accesses Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 08/20] nubus: generate bus error when attempting to access empty slots Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 09/20] macfb: don't register declaration ROM Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 10/20] nubus-device: remove nubus_register_rom() and nubus_register_format_block() Mark Cave-Ayland
2021-09-19 21:10   ` Philippe Mathieu-Daudé
2021-09-21  7:24     ` Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 11/20] nubus-device: add romfile property for loading declaration ROMs Mark Cave-Ayland
2021-09-16 11:05   ` Philippe Mathieu-Daudé
2021-09-16 13:06     ` Markus Armbruster [this message]
2021-09-16 14:19       ` Mark Cave-Ayland
2021-09-17  9:53         ` Markus Armbruster
2021-09-16 10:05 ` [PATCH v3 12/20] nubus: move nubus to its own 32-bit address space Mark Cave-Ayland
2021-09-16 12:48   ` BALATON Zoltan
2021-09-16 14:00     ` Mark Cave-Ayland
2021-09-16 16:50       ` BALATON Zoltan
2021-09-16 10:05 ` [PATCH v3 13/20] nubus-bridge: introduce separate NubusBridge structure Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 14/20] mac-nubus-bridge: rename MacNubusState to MacNubusBridge Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 15/20] nubus: move NubusBus from mac-nubus-bridge to nubus-bridge Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 16/20] nubus-bridge: embed the NubusBus object directly within nubus-bridge Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 17/20] nubus-bridge: make slot_available_mask a qdev property Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 18/20] nubus: add support for slot IRQs Mark Cave-Ayland
2021-09-16 10:05 ` [PATCH v3 19/20] q800: wire up nubus IRQs Mark Cave-Ayland
2021-09-19 21:13   ` Philippe Mathieu-Daudé
2021-09-16 10:05 ` [PATCH v3 20/20] q800: configure nubus available slots for Quadra 800 Mark Cave-Ayland
2021-09-19 21:14   ` Philippe Mathieu-Daudé

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=878rzw655h.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    /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.