From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container v3 0/4] implement device hotplug
Date: Mon, 2 Jun 2025 15:32:09 +0200 [thread overview]
Message-ID: <20250602133213.81979-1-f.schauer@proxmox.com> (raw)
For now this only includes adding devices to a running container.
(not removing or editing existing devices)
Changes since v1:
* Reduce code repetition between lxc-pve-prestart-hook and
device_passthrough_hotplug by extracting passthrough device node
creation to a helper.
Changes since v2:
* Remove superfluous comments stating the obvious
* Ensure that the path in the container where the device node is placed
exists
* Split long lines
Filip Schauer (4):
extract apparmor profile & namespace switch to a helper
extract passthrough device node creation to a helper
config: support printing a device
implement device hotplug
src/PVE/LXC.pm | 182 +++++++++++++++++++++++++++++++-------
src/PVE/LXC/Config.pm | 25 ++++++
src/lxc-pve-prestart-hook | 21 +----
3 files changed, 177 insertions(+), 51 deletions(-)
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-06-02 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:32 Filip Schauer [this message]
2025-06-02 13:32 ` [pve-devel] [PATCH container v3 1/4] extract apparmor profile & namespace switch to a helper Filip Schauer
2025-06-02 13:32 ` [pve-devel] [PATCH container v3 2/4] extract passthrough device node creation " Filip Schauer
2025-06-02 13:32 ` [pve-devel] [PATCH container v3 3/4] config: support printing a device Filip Schauer
2025-06-02 13:32 ` [pve-devel] [PATCH container v3 4/4] implement device hotplug Filip Schauer
2025-07-17 9:28 ` Wolfgang Bumiller
2025-07-28 12:53 ` [pve-devel] superseded: [PATCH container v3 0/4] " Filip Schauer
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=20250602133213.81979-1-f.schauer@proxmox.com \
--to=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.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.