kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	virtualization@lists.linux-foundation.org,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org, avi@redhat.com, Carsten Otte <
Subject: [PATCHv3 0/2] virtio: find_vqs/del_vqs fixes
Date: Sun, 26 Jul 2009 15:47:52 +0300	[thread overview]
Message-ID: <20090726124752.GA20740@redhat.com> (raw)

Here's a patch series to fix known regressions in virtio_pci,
by refactoring code along the lines suggested by Rusty.

This is on top of patch
	virtio: fix memory leak on device removal
that has been applied by Rusty.

This supercedes patches:
	[PATCHv3] virtio: recover from vector assignment failure
	[PATCHv2] virtio: fix double free_irq on device removal

Michael S. Tsirkin (2):
  virtio: delete vq from list
  virtio: refactor find_vqs

 drivers/virtio/virtio_pci.c |  218 ++++++++++++++++++++++++-------------------
 1 files changed, 124 insertions(+), 94 deletions(-)

                 reply	other threads:[~2009-07-26 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090726124752.GA20740@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).