From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fam Zheng <fam@euphon.net>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4] virtio-scsi: restart DMA after iothread
Date: Mon, 17 Jun 2019 19:58:40 +0200 [thread overview]
Message-ID: <20190617175840.GO7397@linux.fritz.box> (raw)
In-Reply-To: <25ad60d8-8860-b535-a42b-03d4d63d0802@redhat.com>
Am 17.06.2019 um 19:23 hat Paolo Bonzini geschrieben:
> On 17/06/19 14:29, Kevin Wolf wrote:
> > But in the end, if Paolo feels strongly that for whatever reason
> > propagating events through the real device tree isn't good, let's get
> > the bug fixed with whatever hack it takes.
>
> It is actually good, but the implementation in hw/scsi is ugly because
> it singles out virtio-scsi - whereas the rule should simply be that the
> HBA is stopped after the disks and started before. Having the HBA do
> something special if it cares about the order is the part that I didn't
> like.
The alternative would be to add a VM state change handler to all other
HBAs, too, so that scsi-bus never has to register its own handler. I
don't think we have that many HBAs, so maybe it's actually workable.
Of course, this makes me think that maybe for the actual proper
solution, VM state change handlers should really be a feature that qdev
provides for devices. Then if a HBA doesn't have anything else to do,
the qdev core would just recurse into the children right away; if it has
something to do, it would disable the device after its children, and
re-enable it before the children.
However, I'm afraid we're talking about a major feature then and not
about a simple fix any more. :-(
Kevin
next prev parent reply other threads:[~2019-06-17 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 12:04 [Qemu-devel] [PATCH v4] virtio-scsi: restart DMA after iothread Stefan Hajnoczi
2019-06-12 12:32 ` Paolo Bonzini
2019-06-12 14:06 ` no-reply
2019-06-17 12:29 ` Kevin Wolf
2019-06-17 17:23 ` Paolo Bonzini
2019-06-17 17:58 ` Kevin Wolf [this message]
2019-06-17 18:27 ` Paolo Bonzini
2019-06-20 16:18 ` Stefan Hajnoczi
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=20190617175840.GO7397@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=fam@euphon.net \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).