qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qdev: switch reset to post-order, clean up PCI reset
Date: Thu, 3 Oct 2013 19:54:17 +0300	[thread overview]
Message-ID: <20131003165417.GA4616@redhat.com> (raw)
In-Reply-To: <524D9426.20707@redhat.com>

On Thu, Oct 03, 2013 at 05:58:30PM +0200, Paolo Bonzini wrote:
> Il 03/10/2013 15:54, Michael S. Tsirkin ha scritto:
> > On Thu, Oct 03, 2013 at 03:46:11PM +0200, Paolo Bonzini wrote:
> >> PCI is handling resetting of its devices before the bus is reset,
> >> but this is only necessary because qdev is broken and usually does
> >> pre-order reset.  Post-order is a much better definition.  Drop
> >> the unnecessary flexibility that lets bus decide the reset order,
> >> convert to post-order, and make PCI use common code for reset.
> > 
> > Need to go carefully here. I remember a bunch of targets
> > were relying on reset in this order, though don't
> > have the detail right now.
> 
> The main change is that sub-devices, which basically exist only for USB,
> virtio, and SCSI, are reset _before_ the corresponding parent device
> (the USB host controller, virtio proxy device, or SCSI HBA).
> 
> For SCSI, this patch fixes bugs that I'm currently working around in
> virtio-scsi (see the manual reset in virtio_scsi_reset, that manually
> resets the subdevices).
> 
> USB and virtio are not using qdev reset at all, so they are unaffected
> by the patches.  They rely on the parent device's own reset method to
> propagate the reset.  virtio already uses post-order, so it could be
> changed to use qdev reset, but I don't plan to do it unless it fixes
> bugs.  USB is more complicated and I don't really understand it.
> 
> For PCI, the change is that all devices are reset first, and then the
> interrupts state and config space are reset for all devices.
> 
> > What kind of testing did this patchset go through?
> 
> For each PCI device I tried creating a VM with an instance of it (a few
> devices at a time), and did VM resets.  Earlier versions were tested by
> the guy who reported the SCSI problems.
> 
> Paolo

x86 kvm only?

> >> Paolo Bonzini (4):
> >>   pci: do not export pci_bus_reset
> >>   pci: clean up resetting of IRQs
> >>   qdev: allow both pre- and post-order vists in qdev walking functions
> >>   qdev: switch reset to post-order
> >>
> >>  hw/core/qdev.c         |   47 ++++++++++++++++++++++++++++++++++-------------
> >>  hw/pci/pci.c           |   42 ++++++++++++++++++++----------------------
> >>  hw/pci/pci_bridge.c    |    2 +-
> >>  include/hw/pci/pci.h   |    1 -
> >>  include/hw/qdev-core.h |   15 ++++++++++-----
> >>  5 files changed, 65 insertions(+), 42 deletions(-)
> > 
> > 

  reply	other threads:[~2013-10-03 16:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 13:46 [Qemu-devel] [PATCH 0/4] qdev: switch reset to post-order, clean up PCI reset Paolo Bonzini
2013-10-03 13:46 ` [Qemu-devel] [PATCH 1/4] pci: do not export pci_bus_reset Paolo Bonzini
2013-10-03 13:46 ` [Qemu-devel] [PATCH 2/4] pci: clean up resetting of IRQs Paolo Bonzini
2013-10-03 13:46 ` [Qemu-devel] [PATCH 3/4] qdev: allow both pre- and post-order vists in qdev walking functions Paolo Bonzini
2013-10-03 13:46 ` [Qemu-devel] [PATCH 4/4] qdev: switch reset to post-order Paolo Bonzini
2013-10-03 13:54 ` [Qemu-devel] [PATCH 0/4] qdev: switch reset to post-order, clean up PCI reset Michael S. Tsirkin
2013-10-03 15:58   ` Paolo Bonzini
2013-10-03 16:54     ` Michael S. Tsirkin [this message]
2013-10-03 16:53       ` Paolo Bonzini
2013-10-06 18:28         ` Michael S. Tsirkin
2013-10-06 20:34           ` Paolo Bonzini
2013-10-09 16:10             ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2013-12-06 16:54 Paolo Bonzini
2013-12-19 19:15 ` Michael S. Tsirkin
2013-12-19 23:45   ` Paolo Bonzini

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=20131003165417.GA4616@redhat.com \
    --to=mst@redhat.com \
    --cc=pbonzini@redhat.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).