From: "Andreas Färber" <afaerber@suse.de>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: peter.crosthwaite@xilinx.com, qemu-devel@nongnu.org,
agraf@suse.de, Christian Borntraeger <borntraeger@de.ibm.com>,
jfrei@linux.vnet.ibm.com, gesaint@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH for-2.4 1/2] core: reset handler for bus-less devices
Date: Mon, 13 Jul 2015 18:06:45 +0200 [thread overview]
Message-ID: <55A3E215.20305@suse.de> (raw)
In-Reply-To: <20150713163727.4b18f409.cornelia.huck@de.ibm.com>
Am 13.07.2015 um 16:37 schrieb Cornelia Huck:
> On Mon, 13 Jul 2015 16:20:09 +0200
> Andreas Färber <afaerber@suse.de> wrote:
>
>> Am 13.07.2015 um 16:11 schrieb Cornelia Huck:
>>> On Mon, 13 Jul 2015 14:22:05 +0200
>>> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>>>
>>> Any objections against taking this through s390-next? I'd like to fix
>>> diag288 reset (+ that annoying migration regession) for 2.4-rc1 and
>>> send a pull request soon.
>>
>> Which device does this fix (only this diag88?), and is it really not
>> possible to register a reset handler where it's being created?
>
> The original patch did this
> (<1436259202-20509-2-git-send-email-cornelia.huck@de.ibm.com>). Peter
> C. suspected NAND may also be affected
> (<CAEgOgz6Fa5TSApDrj9iHA+2joDt1yBg6amCAp-634Bbe5bgNvA@mail.gmail.com>).
Found it. So the problem *is* different from what I understood! It's not
directly attached to /machine by s390x code, but rather instantiated via
-device by the user.
Peter C. suggested you to do it in realize, which affects all devices.
The solution would be to instead either do the reset registration in
qdev-monitor.c, where it's specific to devices that do not have a bus
and on /machine/peripheral or /machine/periph-anon are not managed by a
parent, or to add a further check here in realized. Right now I can only
think of a hot-plug flag...? Not sure about unrealizing in the
qdev-monitor case, but I think we can ignore that in this case?
>> Peter C.'s theory does not match practice for x86, and this patch will
>> lead to bus-less devices that are properly being reset by their parent
>> getting reset twice, potentially causing issues due to qemu_irqs. I'd
>> rather avoid that.
>
> Introducing new bugs is not something I want to do. Are double resets a
> problem in practice, though?
Not the double part, the relative ordering.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-07-13 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 16:51 [Qemu-devel] [PATCH for-2.4 0/2] reset for bus-less devices Cornelia Huck
2015-07-09 16:51 ` [Qemu-devel] [PATCH for-2.4 1/2] core: reset handler " Cornelia Huck
2015-07-09 16:59 ` Andreas Färber
2015-07-09 18:53 ` Peter Crosthwaite
2015-07-13 14:28 ` Paolo Bonzini
2015-07-13 12:22 ` Christian Borntraeger
2015-07-13 14:11 ` Cornelia Huck
2015-07-13 14:20 ` Andreas Färber
2015-07-13 14:30 ` Christian Borntraeger
2015-07-13 15:05 ` Andreas Färber
2015-07-13 15:38 ` Cornelia Huck
2015-07-13 15:49 ` Andreas Färber
2015-07-13 15:56 ` Peter Maydell
2015-07-13 14:37 ` Cornelia Huck
2015-07-13 16:06 ` Andreas Färber [this message]
2015-07-14 7:41 ` Cornelia Huck
2015-07-09 16:51 ` [Qemu-devel] [PATCH for-2.4 2/2] watchdog/diag288: handle subsystem resets correctly Cornelia Huck
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=55A3E215.20305@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gesaint@linux.vnet.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=peter.crosthwaite@xilinx.com \
--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).