qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 00/35] hw/ reorganization, part 2


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH 00/35] hw/ reorganization, part 2
Date: Tue, 19 Mar 2013 10:26:46 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130219 Thunderbird/17.0.3

Il 18/03/2013 21:21, Peter Maydell ha scritto:
> On 18 March 2013 20:05, Paolo Bonzini <address@hidden> wrote:
>> Il 18/03/2013 19:17, Peter Maydell ha scritto:
>>>>> Shouldn't these containers also host the CPU device(s), rather than the
>>>>> boards?  And create them according to the num-cpu property?  If so, they
>>>>> would have to go in hw/arm.
>>> Yes, ideally they should have the CPU devices in them too.
>>> Remind me why devices which instantiate the CPU device go
>>> in hw/arm ?
>>
>> Because they refer to ARMCPU/CPUARMState.
> 
> Well, a container object that instantiated the CPUs wouldn't
> be referring to the internal CPU state struct, it would just
> be treating them as QOM objects like any other, so that doesn't
> apply.

Wouldn't it also bridge the CPU's internal interrupt pins to the GIC?
Like this code in highbank.c:


        /* This will become a QOM property eventually */
        irqp = arm_pic_init_cpu(cpu);
        cpu_irq[n] = irqp[ARM_PIC_CPU_IRQ];
...
    for (n = 0; n < smp_cpus; n++) {
        sysbus_connect_irq(busdev, n, cpu_irq[n]);
    }

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]