From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: VFIO updates for v5.1-rc1
Date: Fri, 22 Feb 2019 15:22:52 -0700 [thread overview]
Message-ID: <20190222152252.0e08eab2@x1.home> (raw)
Hi Linus,
An early pull request for the v5.1 merge window.
The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:
Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.1-rc1
for you to fetch changes up to 0cfd027be1d6def4a462cdc180c055143af24069:
vfio_pci: Enable memory accesses before calling pci_map_rom (2019-02-18 14:57:50 -0700)
----------------------------------------------------------------
VFIO updates for v5.1-rc1
- Switch mdev to generic UUID API (Andy Shevchenko)
- Fixup platform reset include paths (Masahiro Yamada)
- Fix usage of MINORMASK (Chengguang Xu)
- Remove noise from duplicate spapr table unsets (Alexey Kardashevskiy)
- Restore device state after PM reset (Alex Williamson)
- Ensure memory translation enabled for PCI ROM access (Eric Auger)
----------------------------------------------------------------
Alex Williamson (1):
vfio/pci: Restore device state on PM transition
Alexey Kardashevskiy (1):
vfio/spapr_tce: Skip unsetting already unset table
Andy Shevchenko (1):
vfio-mdev: Switch to use new generic UUID API
Chengguang Xu (4):
vfio: expand minor range when registering chrdev region
samples/vfio-mdev/mbochs: expand minor range when registering chrdev region
samples/vfio-mdev/mdpy: expand minor range when registering chrdev region
samples/vfio-mdev/mtty: expand minor range when registering chrdev region
Eric Auger (1):
vfio_pci: Enable memory accesses before calling pci_map_rom
Masahiro Yamada (1):
vfio: platform: reset: fix up include directives to remove ccflags-y
drivers/vfio/mdev/mdev_core.c | 16 ++--
drivers/vfio/mdev/mdev_private.h | 5 +-
drivers/vfio/mdev/mdev_sysfs.c | 6 +-
drivers/vfio/pci/vfio_pci.c | 90 ++++++++++++++++++----
drivers/vfio/pci/vfio_pci_config.c | 2 +-
drivers/vfio/pci/vfio_pci_private.h | 6 ++
drivers/vfio/platform/reset/Makefile | 2 -
.../vfio/platform/reset/vfio_platform_amdxgbe.c | 2 +-
.../vfio/platform/reset/vfio_platform_bcmflexrm.c | 2 +-
.../platform/reset/vfio_platform_calxedaxgmac.c | 2 +-
drivers/vfio/vfio.c | 8 +-
drivers/vfio/vfio_iommu_spapr_tce.c | 3 +-
include/linux/mdev.h | 2 +-
samples/vfio-mdev/mbochs.c | 8 +-
samples/vfio-mdev/mdpy.c | 8 +-
samples/vfio-mdev/mtty.c | 17 ++--
16 files changed, 125 insertions(+), 54 deletions(-)
reply other threads:[~2019-02-22 22:22 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=20190222152252.0e08eab2@x1.home \
--to=alex.williamson@redhat.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