Re: QOM

Re: QOM

[Philippe Mathieu-Daudé]

Hi Abhijeet,

On 12/21/21 12:27, abhijeet inamdar wrote:
> Hi,
> 
> 1)What does QOM stand for?

QOM: "QEMU Object Model"

See https://qemu-project.gitlab.io/qemu/devel/qom.html

> 2)Can anyone tell what this error means? 
> 
> (qemu) Unexpected error in object_property_find() at
> /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177:
> qemu-system-arm: Property '.sysbus-irq[0]' not found
> Aborted (core dumped).

I suppose you are trying to connect a device gpio/irq output line
to another device input, likely using sysbus_connect_irq().

The API is "connect the N-th output line from the SysBus device
to this qemu_irq handler", where qemu_irq is the input line.

Apparently your SysBus device doesn't have any output line
registered. These are registered using sysbus_init_irq().
The first call register the first output IRQ, and so on.

Some objects have their QOM interface documented, for
example to use the ARM GIC see:
https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/intc/arm_gic.h#L22

Hope that helps.

Regards,

Phil.

Re: QOM

[abhijeet inamdar]

[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]

Oh,

In that case I have to define my irq set for a machine to handle the
exception and interrupts.

BR.
Abhijeet.

On Tue, 21 Dec, 2021, 12:59 Philippe Mathieu-Daudé, <philmd@redhat.com>
wrote:

> Hi Abhijeet,
>
> On 12/21/21 12:27, abhijeet inamdar wrote:
> > Hi,
> >
> > 1)What does QOM stand for?
>
> QOM: "QEMU Object Model"
>
> See https://qemu-project.gitlab.io/qemu/devel/qom.html
>
> > 2)Can anyone tell what this error means?
> >
> > (qemu) Unexpected error in object_property_find() at
> > /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177:
> > qemu-system-arm: Property '.sysbus-irq[0]' not found
> > Aborted (core dumped).
>
> I suppose you are trying to connect a device gpio/irq output line
> to another device input, likely using sysbus_connect_irq().
>
> The API is "connect the N-th output line from the SysBus device
> to this qemu_irq handler", where qemu_irq is the input line.
>
> Apparently your SysBus device doesn't have any output line
> registered. These are registered using sysbus_init_irq().
> The first call register the first output IRQ, and so on.
>
> Some objects have their QOM interface documented, for
> example to use the ARM GIC see:
>
> https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/intc/arm_gic.h#L22
>
> Hope that helps.
>
> Regards,
>
> Phil.
>
>

[-- Attachment #2: Type: text/html, Size: 2135 bytes --]

Re: QOM

[abhijeet inamdar]

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

As we have almost 80 irq lines and 40-45 NVIC_irq's.

Where can I define them?

BR.
Abhijeet.

On Tue, 21 Dec, 2021, 13:18 abhijeet inamdar, <abhijeetinamdar3005@gmail.com>
wrote:

> Oh,
>
> In that case I have to define my irq set for a machine to handle the
> exception and interrupts.
>
> BR.
> Abhijeet.
>
> On Tue, 21 Dec, 2021, 12:59 Philippe Mathieu-Daudé, <philmd@redhat.com>
> wrote:
>
>> Hi Abhijeet,
>>
>> On 12/21/21 12:27, abhijeet inamdar wrote:
>> > Hi,
>> >
>> > 1)What does QOM stand for?
>>
>> QOM: "QEMU Object Model"
>>
>> See https://qemu-project.gitlab.io/qemu/devel/qom.html
>>
>> > 2)Can anyone tell what this error means?
>> >
>> > (qemu) Unexpected error in object_property_find() at
>> > /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177:
>> > qemu-system-arm: Property '.sysbus-irq[0]' not found
>> > Aborted (core dumped).
>>
>> I suppose you are trying to connect a device gpio/irq output line
>> to another device input, likely using sysbus_connect_irq().
>>
>> The API is "connect the N-th output line from the SysBus device
>> to this qemu_irq handler", where qemu_irq is the input line.
>>
>> Apparently your SysBus device doesn't have any output line
>> registered. These are registered using sysbus_init_irq().
>> The first call register the first output IRQ, and so on.
>>
>> Some objects have their QOM interface documented, for
>> example to use the ARM GIC see:
>>
>> https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/intc/arm_gic.h#L22
>>
>> Hope that helps.
>>
>> Regards,
>>
>> Phil.
>>
>>

[-- Attachment #2: Type: text/html, Size: 2761 bytes --]

Re: QOM

[abhijeet inamdar]

[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]

Hi,

How did we decide the NUM_IRQ_LINES 64 for stellaris?


BR.
Abhijeet.




On Tue, 21 Dec, 2021, 13:22 abhijeet inamdar, <abhijeetinamdar3005@gmail.com>
wrote:

> As we have almost 80 irq lines and 40-45 NVIC_irq's.
>
> Where can I define them?
>
> BR.
> Abhijeet.
>
> On Tue, 21 Dec, 2021, 13:18 abhijeet inamdar, <
> abhijeetinamdar3005@gmail.com> wrote:
>
>> Oh,
>>
>> In that case I have to define my irq set for a machine to handle the
>> exception and interrupts.
>>
>> BR.
>> Abhijeet.
>>
>> On Tue, 21 Dec, 2021, 12:59 Philippe Mathieu-Daudé, <philmd@redhat.com>
>> wrote:
>>
>>> Hi Abhijeet,
>>>
>>> On 12/21/21 12:27, abhijeet inamdar wrote:
>>> > Hi,
>>> >
>>> > 1)What does QOM stand for?
>>>
>>> QOM: "QEMU Object Model"
>>>
>>> See https://qemu-project.gitlab.io/qemu/devel/qom.html
>>>
>>> > 2)Can anyone tell what this error means?
>>> >
>>> > (qemu) Unexpected error in object_property_find() at
>>> > /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177:
>>> > qemu-system-arm: Property '.sysbus-irq[0]' not found
>>> > Aborted (core dumped).
>>>
>>> I suppose you are trying to connect a device gpio/irq output line
>>> to another device input, likely using sysbus_connect_irq().
>>>
>>> The API is "connect the N-th output line from the SysBus device
>>> to this qemu_irq handler", where qemu_irq is the input line.
>>>
>>> Apparently your SysBus device doesn't have any output line
>>> registered. These are registered using sysbus_init_irq().
>>> The first call register the first output IRQ, and so on.
>>>
>>> Some objects have their QOM interface documented, for
>>> example to use the ARM GIC see:
>>>
>>> https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/intc/arm_gic.h#L22
>>>
>>> Hope that helps.
>>>
>>> Regards,
>>>
>>> Phil.
>>>
>>>

[-- Attachment #2: Type: text/html, Size: 3478 bytes --]

Re: QOM

[Peter Maydell]

On Tue, 21 Dec 2021 at 16:23, abhijeet inamdar
<abhijeetinamdar3005@gmail.com> wrote:
> How did we decide the NUM_IRQ_LINES 64 for stellaris?

Either:
(a) we looked at the documentation for the hardware, which told us
that this SoC is built with its Cortex-M core configured with
that many interrupt lines

Or:
(b) this is for legacy reasons a bogus setting which happens to
work because it's too big rather than too small

For a new SoC, you need to follow course (a), ie look at what
the hardware is and model that.

-- PMM