[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 1/3] cpu: make CPU_INTERRUPT_RESET available
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH v2 1/3] cpu: make CPU_INTERRUPT_RESET available on all targets |
Date: |
Wed, 06 Mar 2013 10:13:34 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130219 Thunderbird/17.0.3 |
Il 06/03/2013 03:02, Peter Crosthwaite ha scritto:
> If you truly have connectivity from device land to the CPU cluster
> should that be reflected by some sort of QOM linkage?
I think in real hardware what happens is that a single "wire" is
distributed to all CPUs. Devices do not have direct links to all the
CPUs, they are agnostic of how many CPUs they control (at least on x86).
In this sense, using first_cpu is the right modelling in my opinion.
Having qemu_irqs for all the reset requests would definitely be a good
thing to do. In the meanwhile, however, having half of the reset
signals as qemu_irqs, and the other half as function calls would be
confusing.
Alternatively we could add some kind of "meta-device" that distributes
stuff to all CPUs, and hide the usage of first_cpu there. Andreas, what
do you think?
Paolo
[Qemu-devel] [PATCH v2 3/3] hw: correctly implement soft reset, Paolo Bonzini, 2013/03/05
Re: [Qemu-devel] [PATCH v2 0/3] Implement x86 soft reset, Laszlo Ersek, 2013/03/05