public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm <kvm@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"eric.auger" <eric.auger@linaro.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	james.morse@arm.com
Subject: [GIT PULL] VFIO updates for v4.4-rc1
Date: Fri, 13 Nov 2015 09:36:47 -0700	[thread overview]
Message-ID: <1447432607.3946.103.camel@redhat.com> (raw)

Hi Linus,

The following changes since commit 32b88194f71d6ae7768a29f87fbba454728273ee:

  Linux 4.3-rc7 (2015-10-25 10:39:47 +0900)

are available in the git repository at:

  git://github.com/awilliam/linux-vfio.git tags/vfio-v4.4-rc1

for you to fetch changes up to 222e684ca762e9288108fcf852eb5d08cbe10ae3:

  vfio/pci: make an array larger (2015-11-09 08:59:11 -0700)

----------------------------------------------------------------
VFIO updates for v4.4-rc1
 - Use kernel interfaces for VPD emulation (Alex Williamson)
 - Platform fix for releasing IRQs (Eric Auger)
 - Type1 IOMMU always advertises PAGE_SIZE support when smaller
   mapping sizes are available (Eric Auger)
 - Platform fixes for incorrectly using copies of structures rather
   than pointers to structures (James Morse)
 - Rework platform reset modules, fix leak, and add AMD xgbe reset
   module (Eric Auger)
 - Fix vfio_device_get_from_name() return value (Joerg Roedel)
 - No-IOMMU interface (Alex Williamson)
 - Fix potential out of bounds array access in PCI config handling
   (Dan Carpenter)

----------------------------------------------------------------
Alex Williamson (3):
      vfio: Whitelist PCI bridges
      vfio/pci: Use kernel VPD access functions
      vfio: Include No-IOMMU mode

Dan Carpenter (1):
      vfio/pci: make an array larger

Eric Auger (11):
      VFIO: platform: clear IRQ_NOAUTOEN when de-assigning the IRQ
      vfio/type1: handle case where IOMMU does not support PAGE_SIZE size
      vfio: platform: introduce vfio-platform-base module
      vfio: platform: add capability to register a reset function
      vfio: platform: introduce module_vfio_reset_handler macro
      vfio: platform: reset: calxedaxgmac: add reset function registration
      vfio: platform: add compat in vfio_platform_device
      vfio: platform: use list of registered reset function
      vfio: platform: add dev_info on device reset
      vfio: platform: reset: calxedaxgmac: fix ioaddr leak
      VFIO: platform: reset: AMD xgbe reset module

James Morse (1):
      vfio/platform: store mapped memory in region, instead of an on-stack copy

Joerg Roedel (1):
      vfio: Fix bug in vfio_device_get_from_name()

 drivers/vfio/Kconfig                               |  15 ++
 drivers/vfio/pci/vfio_pci.c                        |   8 +-
 drivers/vfio/pci/vfio_pci_config.c                 |  74 ++++++-
 drivers/vfio/platform/Makefile                     |   6 +-
 drivers/vfio/platform/reset/Kconfig                |   8 +
 drivers/vfio/platform/reset/Makefile               |   2 +
 .../vfio/platform/reset/vfio_platform_amdxgbe.c    | 127 ++++++++++++
 .../platform/reset/vfio_platform_calxedaxgmac.c    |  19 +-
 drivers/vfio/platform/vfio_amba.c                  |   1 +
 drivers/vfio/platform/vfio_platform.c              |   1 +
 drivers/vfio/platform/vfio_platform_common.c       | 155 +++++++++-----
 drivers/vfio/platform/vfio_platform_irq.c          |   1 +
 drivers/vfio/platform/vfio_platform_private.h      |  40 +++-
 drivers/vfio/vfio.c                                | 224 +++++++++++++++++++--
 drivers/vfio/vfio_iommu_type1.c                    |  15 +-
 include/linux/vfio.h                               |   3 +
 include/uapi/linux/vfio.h                          |   7 +
 17 files changed, 616 insertions(+), 90 deletions(-)
 create mode 100644 drivers/vfio/platform/reset/vfio_platform_amdxgbe.c


                 reply	other threads:[~2015-11-13 16:36 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=1447432607.3946.103.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=eric.auger@linaro.org \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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