From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 0/5] Support VM migration with mdev vGPUs
Date: Fri, 23 Oct 2026 19:53:38 +0300 [thread overview]
Message-ID: <20261023165343.503945-1-andrey.drobyshev@virtuozzo.com> (raw)
Reverts are taken from the Oracle's UEK kernel.
Plus one real bug fix.
https://virtuozzo.atlassian.net/browse/VSTOR-150595
Andrey Drobyshev (1):
mm: allow MADV_DOEXEC on a VFIO mapping not faulted in yet
Anthony Yznaga (4):
Revert "vfio: revert "iommu driver notify callback""
Revert "vfio/type1: revert "implement notify callback""
Revert "vfio/type1: revert "block on invalid vaddr""
Revert "vfio/type1: exclude mdevs from VFIO_UPDATE_VADDR"
drivers/vfio/container.c | 5 ++
drivers/vfio/vfio.h | 7 ++
drivers/vfio/vfio_iommu_type1.c | 149 ++++++++++++++++++++++----------
include/linux/mm.h | 4 +-
include/uapi/linux/vfio.h | 15 ++--
5 files changed, 124 insertions(+), 56 deletions(-)
--
2.47.1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-10-23 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 16:53 Andrey Drobyshev [this message]
2026-10-23 16:53 ` [Devel] [PATCH hci-8.1 1/5] Revert "vfio: revert "iommu driver notify callback"" Andrey Drobyshev
2026-10-23 16:53 ` [Devel] [PATCH hci-8.1 2/5] Revert "vfio/type1: revert "implement " Andrey Drobyshev
2026-10-23 16:53 ` [Devel] [PATCH hci-8.1 3/5] Revert "vfio/type1: revert "block on invalid vaddr"" Andrey Drobyshev
2026-10-23 16:53 ` [Devel] [PATCH hci-8.1 4/5] Revert "vfio/type1: exclude mdevs from VFIO_UPDATE_VADDR" Andrey Drobyshev
2026-10-23 16:53 ` [Devel] [PATCH hci-8.1 5/5] mm: allow MADV_DOEXEC on a VFIO mapping not faulted in yet Andrey Drobyshev
2026-10-27 15:48 ` [Devel] [PATCH hci-8.1 0/5] Support VM migration with mdev vGPUs Andrey Drobyshev
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=20261023165343.503945-1-andrey.drobyshev@virtuozzo.com \
--to=andrey.drobyshev@virtuozzo.com \
--cc=devel@openvz.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