From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v6.11-rc1
Date: Thu, 18 Jul 2024 12:35:35 -0600 [thread overview]
Message-ID: <20240718123535.270f63f2.alex.williamson@redhat.com> (raw)
Hi Linus,
Just a few commits this cycle. Thanks
The following changes since commit 6ba59ff4227927d3a8530fc2973b80e94b54d58f:
Linux 6.10-rc4 (2024-06-16 13:40:16 -0700)
are available in the Git repository at:
https://github.com/awilliam/linux-vfio.git tags/vfio-v6.11-rc1
for you to fetch changes up to 0756bec2e45b206ccb5fc3e8791c08d696dd06f7:
vfio-mdev: add missing MODULE_DESCRIPTION() macros (2024-07-17 12:24:13 -0600)
----------------------------------------------------------------
VFIO updates for v6.11
- Add support for 8-byte accesses when using read/write through the
device regions. This fills a gap for userspace drivers that might
not be able to use access through mmap to perform native register
width accesses. (Gerd Bayer)
- Add missing MODULE_DESCRIPTION to vfio-mdev sample drivers and
replace a non-standard MODULE_INFO usage. (Jeff Johnson)
----------------------------------------------------------------
Ben Segal (1):
vfio/pci: Support 8-byte PCI loads and stores
Gerd Bayer (2):
vfio/pci: Extract duplicated code into macro
vfio/pci: Fix typo in macro to declare accessors
Jeff Johnson (1):
vfio-mdev: add missing MODULE_DESCRIPTION() macros
drivers/vfio/pci/vfio_pci_rdwr.c | 122 ++++++++++++++++++++-------------------
include/linux/vfio_pci_core.h | 21 ++++---
samples/vfio-mdev/mbochs.c | 1 +
samples/vfio-mdev/mdpy-fb.c | 1 +
samples/vfio-mdev/mdpy.c | 1 +
samples/vfio-mdev/mtty.c | 2 +-
6 files changed, 78 insertions(+), 70 deletions(-)
next reply other threads:[~2024-07-18 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 18:35 Alex Williamson [this message]
2024-07-19 19:38 ` pr-tracker-bot
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=20240718123535.270f63f2.alex.williamson@redhat.com \
--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
all inboxes | Powered by JetHome®