From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/3] vfio: free data and unmap BARs in instance_finalize
Date: Wed, 4 Feb 2015 13:11:07 +0100 [thread overview]
Message-ID: <1423051870-26473-1-git-send-email-pbonzini@redhat.com> (raw)
This is v2 of the patch sent yesterday. In addition to including
the missing vfio bits, I split it in two parts: one introducing
instance_finalize (patch 2), and the second making the freeing of BARs
RCU-friendly (patch 3).
With these two changes I found the error path logic a bit hard
to follow. So I preceded it with patch 1, which tries to make things
a little bit clearer, at least to me.
VFIO is probably the device that requires the largest changes, due to
the complex, highly data-driven initialization sequence. No other device
can use so many dynamic data structures, because their configuration is
obviously not as variable as for PCI pass-through.
Paolo
Paolo Bonzini (3):
vfio: cleanup vfio_get_device error path, remove vfio_populate_device callback
vfio: free dynamically-allocated data in instance_finalize
vfio: unmap and free BAR data in instance_finalize
hw/vfio/common.c | 36 ++++++++--------
hw/vfio/pci.c | 96 ++++++++++++++++++++++++++++++++++---------
include/hw/vfio/vfio-common.h | 1 -
3 files changed, 92 insertions(+), 41 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-02-04 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 12:11 Paolo Bonzini [this message]
2015-02-04 12:11 ` [Qemu-devel] [PATCH 1/3] vfio: cleanup vfio_get_device error path, remove vfio_populate_device callback Paolo Bonzini
2015-02-04 18:22 ` Alex Williamson
2015-02-04 20:14 ` Paolo Bonzini
2015-02-04 12:11 ` [Qemu-devel] [PATCH 2/3] vfio: free dynamically-allocated data in instance_finalize Paolo Bonzini
2015-02-04 12:11 ` [Qemu-devel] [PATCH 3/3] vfio: unmap and free BAR " 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=1423051870-26473-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.