kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PULL 0/6] VFIO updates for QEMU
Date: Wed, 09 Oct 2013 07:54:00 -0700	[thread overview]
Message-ID: <87hacqxzp3.fsf@codemonkey.ws> (raw)
In-Reply-To: <20131003153601.26487.70022.stgit@bling.home>

Alex Williamson <alex.williamson@redhat.com> writes:

> The following changes since commit a684f3cf9b9b9c3cb82be87aafc463de8974610c:
>
>   Merge remote-tracking branch 'kraxel/seabios-1.7.3.2' into staging (2013-09-30 17:15:27 -0500)
>
> are available in the git repository at:
>
>
>   git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for-qemu-20131003.0
>
> for you to fetch changes up to 1d5bf692e55ae22b59083741d521e27db704846d:
>
>   vfio: Fix debug output for int128 values (2013-10-03 09:10:09 -0600)
>
> ----------------------------------------------------------------

Judging from the review comments, I think this needs a v2.

Regards,

Anthony Liguori

> vfio-pci updates include:
>  - Forgotten MSI affinity patch posted several months ago
>  - Lazy option ROM loading to delay load until after device/bus resets
>  - Error reporting cleanups
>  - PCI hot reset support introduced with Linux v3.12 development kernels
>  - Debug build fix for int128
>
> The lazy ROM loading and hot reset should help VGA assignment as we can
> now do a bus reset when there are multiple devices on the bus, ex.
> multi-function graphics and audio cards.  The known remaining part for
> VGA is the KVM-VFIO device and matching QEMU support to properly handle
> devices that make use of No-Snoop transactions, particularly on Intel
> host systems.
>
> ----------------------------------------------------------------
> Alex Williamson (5):
>       vfio-pci: Add support for MSI affinity
>       vfio-pci: Test device reset capabilities
>       vfio-pci: Lazy PCI option ROM loading
>       vfio-pci: Cleanup error_reports
>       vfio-pci: Implement PCI hot reset
>
> Alexey Kardashevskiy (1):
>       vfio: Fix debug output for int128 values
>
>  hw/misc/vfio.c | 621 +++++++++++++++++++++++++++++++++++++++++++++++----------
>  1 file changed, 512 insertions(+), 109 deletions(-)

  parent reply	other threads:[~2013-10-09 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 15:38 [PULL 0/6] VFIO updates for QEMU Alex Williamson
2013-10-03 15:38 ` [PULL 1/6] vfio-pci: Add support for MSI affinity Alex Williamson
2013-10-03 15:38 ` [PULL 2/6] vfio-pci: Test device reset capabilities Alex Williamson
2013-10-03 15:39 ` [PULL 3/6] vfio-pci: Lazy PCI option ROM loading Alex Williamson
2013-10-03 18:46   ` Paolo Bonzini
2013-10-03 19:11     ` Alex Williamson
2013-10-04 12:13   ` Alexey Kardashevskiy
2013-10-04 14:30     ` Alex Williamson
2013-10-03 15:39 ` [PULL 4/6] vfio-pci: Cleanup error_reports Alex Williamson
2013-10-03 15:39 ` [PULL 5/6] vfio-pci: Implement PCI hot reset Alex Williamson
2013-10-03 15:39 ` [PULL 6/6] vfio: Fix debug output for int128 values Alex Williamson
2013-10-09 14:54 ` Anthony Liguori [this message]
2013-10-09 15:14   ` [PULL 0/6] VFIO updates for QEMU Alex Williamson

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=87hacqxzp3.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).