linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: pratyush@kernel.org, pasha.tatashin@soleen.com, rppt@kernel.org,
	dmatlack@google.com, skhawaja@google.com, rientjes@google.com,
	corbet@lwn.net, akpm@linux-foundation.org, kees@kernel.org,
	davidgow@google.com, pmladek@suse.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v8 0/2] Live Update: File-Lifecycle-Bound (FLB) State
Date: Tue, 25 Nov 2025 17:50:04 -0500	[thread overview]
Message-ID: <20251125225006.3722394-1-pasha.tatashin@soleen.com> (raw)

This series adds support for FLB state to the Live Update Orchestrator.

This functionality was originally part of the main LUO series [1] but
has been split out to serve as a stable dependency for upcoming device
preservation series.

What is FLB?
============
FLB allows global kernel state (like IOMMU domains or HugeTLB state) to
be preserved once, shared across multiple file descriptors, and restored
when needed. It uses reference counting tied to the lifecycle of
preserved files (e.g., VFIO fds) to ensure the global state is valid
as long as any file depends on it.

Why separate?
=============
This patch does not have current user user, but multiple streams depend
on it:

1. VFIO LU preservation (ETA: Tomorrow)
2. IOMMU LU preservation (ETA: One week)
3. HugeTLB LUO preservation (ETA: A couple weeks)

Merging this into linux-next allows these dependent series to be
developed against the same API.

Github repo for this series: [2].

Dependencies
============
This series applies on top of [PATCH v8] Live Update Orchestrator [1].

[1] https://lore.kernel.org/all/20251125165850.3389713-1-pasha.tatashin@soleen.com
[2] https://github.com/soleen/linux/tree/luo/flb_v8

Pasha Tatashin (2):
  liveupdate: luo_flb: Introduce File-Lifecycle-Bound global state
  tests/liveupdate: Add in-kernel liveupdate test

 Documentation/core-api/liveupdate.rst |  11 +
 MAINTAINERS                           |   1 +
 include/linux/kho/abi/luo.h           |  81 ++++
 include/linux/liveupdate.h            | 143 ++++++
 kernel/liveupdate/Makefile            |   1 +
 kernel/liveupdate/luo_core.c          |   7 +-
 kernel/liveupdate/luo_file.c          |  32 +-
 kernel/liveupdate/luo_flb.c           | 656 ++++++++++++++++++++++++++
 kernel/liveupdate/luo_internal.h      |  15 +
 lib/Kconfig.debug                     |  23 +
 lib/tests/Makefile                    |   1 +
 lib/tests/liveupdate.c                | 158 +++++++
 12 files changed, 1125 insertions(+), 4 deletions(-)
 create mode 100644 kernel/liveupdate/luo_flb.c
 create mode 100644 lib/tests/liveupdate.c


base-commit: c26edadff67601d5bbd748ea404ca354d9d47997
-- 
2.52.0.487.g5c8c507ade-goog



             reply	other threads:[~2025-11-25 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 22:50 Pasha Tatashin [this message]
2025-11-25 22:50 ` [PATCH v8 1/2] liveupdate: luo_flb: Introduce File-Lifecycle-Bound global state Pasha Tatashin
2025-11-25 22:50 ` [PATCH v8 2/2] tests/liveupdate: Add in-kernel liveupdate test Pasha Tatashin

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=20251125225006.3722394-1-pasha.tatashin@soleen.com \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=dmatlack@google.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pmladek@suse.com \
    --cc=pratyush@kernel.org \
    --cc=rientjes@google.com \
    --cc=rppt@kernel.org \
    --cc=skhawaja@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox