All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>,
	Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
	Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
	Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/2] mm: allow MADV_DOEXEC on VFIO BAR mappings
Date: Wed, 04 Nov 2026 20:21:52 +0100	[thread overview]
Message-ID: <179382011290.2760255.357492986463241507.b4-ty@b4> (raw)
In-Reply-To: <20261016-b4-prep-khorenko-vstor-103860-4-doexec-vfio-bars-v2-0-2237f8fbb38e@virtuozzo.com>

On Fri, 16 Oct 2026 23:35:38 +0200, Konstantin Khorenko wrote:
> mm: allow MADV_DOEXEC on VFIO BAR mappings
> 
> VSTOR-103860: keep the VFIO BAR mappings of a QEMU process across a
> live-update exec, so the device keeps its MMIO mappings without a
> re-mmap. Applies on top of "mm, exec: fix the MADV_DOEXEC code we carry
> from Oracle" and needs patch 1 of "mm, binfmt_elf: two fixes also posted
> to mainline" (the copy_huge_pmd() recheck), because every live-update
> exec now copies the BAR's huge PMDs. The latter is posted as
> http://lore.virtuozzo.com/20261014-b4-prep-khorenko-vstor-149847-1-upstream-fixes-v1-0-7fde9ffbebe9@virtuozzo.com
> 
> [...]

Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.18.vz10, thanks!

[1/2] mm: allow MADV_DOEXEC on shared PFN mappings of device memory
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/ba11691580f3
[2/2] selftests/mm: check MADV_DOEXEC on VFIO BARs and other PFN mappings
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/31ad25004a57

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team


_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-04 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 21:35 Konstantin Khorenko
2026-10-16 21:35 ` [Devel] [PATCH hci-8.1 v2 1/2] mm: allow MADV_DOEXEC on shared PFN mappings of device memory Konstantin Khorenko
2026-10-16 21:35 ` [Devel] [PATCH hci-8.1 v2 2/2] selftests/mm: check MADV_DOEXEC on VFIO BARs and other PFN mappings Konstantin Khorenko
2026-11-04 19:21 ` Konstantin Khorenko [this message]

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=179382011290.2760255.357492986463241507.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=andrey.drobyshev@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=ptikhomirov@virtuozzo.com \
    --cc=vasileios.almpanis@virtuozzo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.