From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bernhard Beschow <shentey@gmail.com>, qemu-devel@nongnu.org
Cc: "Alberto Garcia" <berto@igalia.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Laurent Vivier" <lvivier@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v2 2/2] hw/ipack: Remove legacy qemu_allocate_irqs() use
Date: Tue, 21 Jan 2025 11:04:43 +0100 [thread overview]
Message-ID: <a301444f-623e-4ba3-9868-b301f6e86a87@linaro.org> (raw)
In-Reply-To: <27522A5D-63E7-45B7-8A54-A19E453AB401@gmail.com>
On 21/1/25 10:24, Bernhard Beschow wrote:
>
>
> Am 21. Januar 2025 08:44:52 UTC schrieb "Philippe Mathieu-Daudé" <philmd@linaro.org>:
>> No need to dynamically allocate IRQ when we know before hands
>> how many we'll use. Declare the 2 of them in IPackDevice state
>> and initialize them in the DeviceRealize handler.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> include/hw/ipack/ipack.h | 7 ++-----
>> hw/char/ipoctal232.c | 4 ++--
>> hw/ipack/ipack.c | 7 +++----
>> hw/ipack/tpci200.c | 6 +++---
>> 4 files changed, 10 insertions(+), 14 deletions(-)
>>
>> diff --git a/include/hw/ipack/ipack.h b/include/hw/ipack/ipack.h
>> index cbcdda509d3..00f397fd020 100644
>> --- a/include/hw/ipack/ipack.h
>> +++ b/include/hw/ipack/ipack.h
>> @@ -12,6 +12,7 @@
>> #define QEMU_IPACK_H
>>
>> #include "hw/qdev-core.h"
>> +#include "hw/irq.h"
>> #include "qom/object.h"
>>
>>
>> @@ -19,10 +20,8 @@
>> OBJECT_DECLARE_SIMPLE_TYPE(IPackBus, IPACK_BUS)
>>
>> struct IPackBus {
>> - /*< private >*/
>> BusState parent_obj;
>>
>> - /* All fields are private */
>> uint8_t n_slots;
>> uint8_t free_slot;
>> qemu_irq_handler set_irq;
>> @@ -58,13 +57,11 @@ struct IPackDeviceClass {
>> };
>>
>> struct IPackDevice {
>> - /*< private >*/
>> DeviceState parent_obj;
>> - /*< public >*/
>>
>> int32_t slot;
>> /* IRQ objects for the IndustryPack INT0# and INT1# */
>> - qemu_irq *irq;
>> + IRQState irq[2];
>> };
>>
>> extern const VMStateDescription vmstate_ipack_device;
>> diff --git a/hw/char/ipoctal232.c b/hw/char/ipoctal232.c
>> index d1e5f6dad2e..a2879977fb3 100644
>> --- a/hw/char/ipoctal232.c
>> +++ b/hw/char/ipoctal232.c
>> @@ -184,9 +184,9 @@ static void update_irq(IPOctalState *dev, unsigned block)
>> unsigned intno = block / 2;
>>
>> if ((blk0->isr & blk0->imr) || (blk1->isr & blk1->imr)) {
>> - qemu_irq_raise(idev->irq[intno]);
>> + qemu_irq_raise(&idev->irq[intno]);
>> } else {
>> - qemu_irq_lower(idev->irq[intno]);
>> + qemu_irq_lower(&idev->irq[intno]);
>> }
>> }
>>
>> diff --git a/hw/ipack/ipack.c b/hw/ipack/ipack.c
>> index ed75f791832..eeb48dd331c 100644
>> --- a/hw/ipack/ipack.c
>> +++ b/hw/ipack/ipack.c
>> @@ -55,22 +55,21 @@ static void ipack_device_realize(DeviceState *dev, Error **errp)
>> }
>> bus->free_slot = idev->slot + 1;
>>
>> - idev->irq = qemu_allocate_irqs(bus->set_irq, idev, 2);
>> + for (int i = 0; i < ARRAY_SIZE(idev->irq); i++) {
>> + qemu_init_irq(&idev->irq[i], bus->set_irq, idev, i);
>
> I wonder if we eventually need a qemu_init_irqs() (note the plural) as we remove further uses of qemu_allocate_irqs().
Yeah I thought about it, but looking at other "Initialize pre-allocated
QOM object in place", we don't have helpers for arrays. Usually because
we can set properties, and array initializer doesn't scale then.
For now IRQ doesn't have properties, so can do.
> With the above addressed:
> Reviewed-by: Bernhard Beschow <shentey@gmail.com>
Thanks!
next prev parent reply other threads:[~2025-01-21 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 8:44 [PATCH v2 0/2] hw/ipack: Minor dust removal Philippe Mathieu-Daudé
2025-01-21 8:44 ` [PATCH v2 1/2] hw/ipack: Clarify KConfig symbols Philippe Mathieu-Daudé
2025-01-21 8:44 ` [PATCH v2 2/2] hw/ipack: Remove legacy qemu_allocate_irqs() use Philippe Mathieu-Daudé
2025-01-21 9:24 ` Bernhard Beschow
2025-01-21 10:04 ` Philippe Mathieu-Daudé [this message]
2025-01-21 15:32 ` Bernhard Beschow
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=a301444f-623e-4ba3-9868-b301f6e86a87@linaro.org \
--to=philmd@linaro.org \
--cc=berto@igalia.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.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).