qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [PULL] vfio-pci tree 20121008
Date: Mon, 08 Oct 2012 09:12:27 -0600	[thread overview]
Message-ID: <1349709147.2759.85.camel@ul30vt.home> (raw)

Anthony,

The following changes since commit 4bb26682f70a5f626cad3e0ac82bf4b6252ea7a4:

  Merge branch 'master' of git.qemu.org:/pub/git/qemu (2012-10-07 18:42:18 +0000)

are available in the git repository at:


  git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for-qemu-20121008.0

for you to fetch changes up to 3a4f2816fac1b0f9cc197bb2208ddf03dc7bc592:

  vfio-pci: Fix BAR->VFIODevice translation in (2012-10-08 08:45:31 -0600)

----------------------------------------------------------------
vfio-pci fixes 20121008.0


These patches have all been posted to the list for review.  From the
previous 00/11 series:

        I've been accumulating a backlog of vfio-pci changes while we've been
        getting the first implementation accepted.  This series includes a
        new algorithm for dealing with INTx that should avoid users needing
        to know about experimental parameters, a re-try mechanism for mappings
        that avoids common errors users might see trying to use vfio-pci, a
        rework of MSIX setup and teardown that fixes a corner case for MSIX
        being enabled but not used, a more robust device reset that re-inits
        interrupts much like pci-assign, a missing INTx setup failure cleanup,
        and addresses a few comments collected during initial review.

Additional Clang patch reported by Blue Swirl and posted last week, as
well as contribution from Jan included in this pull request.  Thanks,

Alex

----------------------------------------------------------------
Alex Williamson (12):
      vfio-pci: Update slow path INTx algorithm
      vfio-pci: Re-order map/unmap
      vfio-pci: Unmap and retry DMA mapping
      vfio-pci: Rework MSIX setup/teardown
      vfio-pci: No spurious MSIs
      vfio-pci: Roll the header into the .c file
      vfio-pci: Don't peak at msi_supported
      vfio-pci: Use uintptr_t for void* cast
      vfio-pci: Remove setting of MSI qsize
      vfio-pci: Extend reset
      vfio-pci: Cleanup on INTx setup failure
      vfio-pci: Clang cleanup

Jan Kiszka (1):
      vfio-pci: Fix BAR->VFIODevice translation in

 hw/vfio_pci.c     | 498 +++++++++++++++++++++++++++++++++---------------------
 hw/vfio_pci_int.h | 114 -------------
 2 files changed, 305 insertions(+), 307 deletions(-)
 delete mode 100644 hw/vfio_pci_int.h

             reply	other threads:[~2012-10-08 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 15:12 Alex Williamson [this message]
2012-10-12 16:18 ` [Qemu-devel] [PULL] vfio-pci tree 20121008 Anthony Liguori

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=1349709147.2759.85.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@siemens.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).