From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
aliguori@us.ibm.com, lersek@redhat.com, qemu-devel@nongnu.org,
dwmw2@infradead.org, afaerber@suse.de
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 [thread overview]
Message-ID: <513708BE.2000407@redhat.com> (raw)
In-Reply-To: <CAEgOgz7vAdFBix0wBxTzcH=hV3L5mnO2CjzEWY=hhF8yCicFCw@mail.gmail.com>
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
next prev parent reply other threads:[~2013-03-06 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 19:00 [Qemu-devel] [PATCH v2 0/3] Implement x86 soft reset Paolo Bonzini
2013-03-05 19:00 ` [Qemu-devel] [PATCH v2 1/3] cpu: make CPU_INTERRUPT_RESET available on all targets Paolo Bonzini
2013-03-05 23:23 ` Peter Maydell
2013-03-06 8:49 ` Paolo Bonzini
2013-03-06 2:02 ` Peter Crosthwaite
2013-03-06 9:13 ` Paolo Bonzini [this message]
2013-03-06 11:54 ` Andreas Färber
2013-03-06 12:12 ` Peter Maydell
2013-03-06 12:19 ` Paolo Bonzini
2013-03-05 19:00 ` [Qemu-devel] [PATCH v2 2/3] pc: port 92 reset requires a low->high transition Paolo Bonzini
2013-03-05 19:00 ` [Qemu-devel] [PATCH v2 3/3] hw: correctly implement soft reset Paolo Bonzini
2013-03-06 2:02 ` li guang
2013-03-06 8:36 ` Paolo Bonzini
2013-03-06 9:06 ` li guang
2013-03-06 9:23 ` Paolo Bonzini
2013-03-05 19:35 ` [Qemu-devel] [PATCH v2 0/3] Implement x86 " Laszlo Ersek
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=513708BE.2000407@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=dwmw2@infradead.org \
--cc=lersek@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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 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).