From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Alistair Francis" <alistair.francis@xilinx.com>,
"Peter Crosthwaite" <crosthwaitepeter@gmail.com>,
"Christopher Covington" <cov@codeaurora.org>,
"Andreas Färber" <afaerber@suse.de>,
"Li Guang" <lig.fnst@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] qdev-monitor.c: Register reset function if the device has one
Date: Fri, 19 Feb 2016 18:17:37 +0100 [thread overview]
Message-ID: <56C74E31.6030806@redhat.com> (raw)
In-Reply-To: <CAFEAcA_vwC5KR1KVYcRJ1FULCzvNvguAvvM0DyKmm+uNMkfq+w@mail.gmail.com>
On 19/02/2016 11:55, Peter Maydell wrote:
>> Any abstraction we have in QEMU should have at least a parallel (though
>> > it need not be the same) in real hardware. Reset signals _do_ propagate
>> > along buses, or at least along some buses, so "debusifying" reset seems
>> > like a counterproductive goal to me.
> Reset for some buses propagates along buses, but not in all
> cases.
Agreed. But still this doesn't change the fact that "debusifying" reset
is a non-goal.
> In any case our current "reset" semantics are "power on
> reset", not any kind of driven-by-hardware-reset-lines reset.
It depends. There are several cases (PCI, SCSI) where qdev_reset_all is
used from within the code in order to provide hardware reset semantics.
Paolo
next prev parent reply other threads:[~2016-02-19 17:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 21:04 [Qemu-devel] [PATCH v1 0/2] Add a generic loader Alistair Francis
2016-02-17 21:04 ` [Qemu-devel] [PATCH v1 1/2] qdev-monitor.c: Register reset function if the device has one Alistair Francis
2016-02-18 9:56 ` Markus Armbruster
2016-02-18 18:47 ` Alistair Francis
2016-02-18 21:47 ` Paolo Bonzini
2016-02-18 23:07 ` Peter Crosthwaite
2016-02-19 0:02 ` Alistair Francis
2016-02-19 9:33 ` Paolo Bonzini
2016-02-19 10:55 ` Peter Maydell
2016-02-19 17:17 ` Paolo Bonzini [this message]
2016-02-19 9:58 ` Markus Armbruster
2016-02-19 17:15 ` Andreas Färber
2016-02-19 18:53 ` Alistair Francis
2016-02-17 21:04 ` [Qemu-devel] [PATCH v1 2/2] generic-loader: Add a generic loader Alistair Francis
2016-02-17 21:41 ` Eric Blake
2016-02-18 0:03 ` Alistair Francis
2016-02-18 0:11 ` Eric Blake
2016-02-18 0:17 ` Alistair Francis
2016-02-18 18:23 ` Hollis Blanchard
2016-02-18 18:49 ` Alistair Francis
2016-02-18 18:58 ` Hollis Blanchard
2016-02-18 19:34 ` Alistair Francis
2016-02-18 18:27 ` [Qemu-devel] [PATCH v1 0/2] " Hollis Blanchard
2016-02-18 19:02 ` Alistair Francis
2016-02-18 20:01 ` Peter Maydell
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=56C74E31.6030806@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=alistair.francis@xilinx.com \
--cc=armbru@redhat.com \
--cc=cov@codeaurora.org \
--cc=crosthwaitepeter@gmail.com \
--cc=lig.fnst@cn.fujitsu.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).