From: Alex Williamson <alex.williamson@redhat.com>
To: aliguori@amazon.com, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PULL v2 0/8] vfio pull request
Date: Tue, 28 Jan 2014 08:58:01 -0700 [thread overview]
Message-ID: <1390924681.2315.62.camel@bling.home> (raw)
In-Reply-To: <20140128153451.30053.92976.stgit@bling.home>
I guess I should be addressing these to both Anthony and Peter now.
Thanks for stepping in, Peter. Thanks,
Alex
On Tue, 2014-01-28 at 08:44 -0700, Alex Williamson wrote:
> Anthony,
>
> My last vfio pull request didn't seem to make the most recent round of
> merges. The only difference in this request is trivial patch 8/8, the
> rest is a resend. I've not rebased in order to maintain the commit
> IDs from my previous tag, the merge to current HEAD is still clean.
> Please pull. Thanks,
>
> Alex
>
> The following changes since commit 1cf892ca2689c84960b4ce4d2723b6bee453711c:
>
> SPARC: Fix LEON3 power down instruction (2014-01-15 15:37:33 +1000)
>
> are available in the git repository at:
>
> git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for-qemu-20140128.0
>
> for you to fetch changes up to 8b6d14087d487203f4d1a67aeaddc3be6c73f49f:
>
> vfio: correct debug macro typo (2014-01-28 08:23:19 -0700)
>
> ----------------------------------------------------------------
> vfio-pci updates include:
> - Destroy MemoryRegions on device teardown
> - Print warnings around PCI option ROM failures
> - Skip bogus mappings from 64bit BAR sizing
> - Act on DMA mapping failures
> - Fix alignment to avoid MSI-X table mapping
> - Fix debug macro typo
>
> ----------------------------------------------------------------
> Alex Williamson (3):
> vfio: Destroy memory regions
> vfio: Filter out bogus mappings
> vfio-pci: Fail initfn on DMA mapping errors
>
> Alexey Kardashevskiy (2):
> kvm: initialize qemu_host_page_size
> vfio: fix mapping of MSIX bar
>
> Bandan Das (3):
> vfio: warn if host device rom can't be read
> vfio: Do not reattempt a failed rom read
> vfio: correct debug macro typo
>
> hw/misc/vfio.c | 78 ++++++++++++++++++++++++++++++++++++++++++-------
> include/exec/exec-all.h | 1 +
> kvm-all.c | 1 +
> translate-all.c | 14 +++++----
> 4 files changed, 77 insertions(+), 17 deletions(-)
next prev parent reply other threads:[~2014-01-28 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 15:44 [Qemu-devel] [PULL v2 0/8] vfio pull request Alex Williamson
2014-01-28 15:45 ` [Qemu-devel] [PULL v2 1/8] vfio: Destroy memory regions Alex Williamson
2014-01-28 15:45 ` [Qemu-devel] [PULL v2 2/8] vfio: warn if host device rom can't be read Alex Williamson
2014-01-28 15:45 ` [Qemu-devel] [PULL v2 3/8] vfio: Do not reattempt a failed rom read Alex Williamson
2014-01-28 15:45 ` [Qemu-devel] [PULL v2 4/8] vfio: Filter out bogus mappings Alex Williamson
2014-01-28 15:58 ` Alex Williamson [this message]
2014-02-01 22:15 ` [Qemu-devel] [PULL v2 0/8] vfio pull request Peter Maydell
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=1390924681.2315.62.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=aliguori@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.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).