public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server v2 1/3] close #5291: support disabling KSM for specific VMs
Date: Mon, 17 Nov 2025 12:59:52 +0100	[thread overview]
Message-ID: <176338078415.3512763.15001247617317199659.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251113155127.591195-2-f.ebner@proxmox.com>

On Thu, 13 Nov 2025 16:51:07 +0100, Fiona Ebner wrote:
> KSM exposes a guest's virtual memory to side-channel attacks. Add a VM
> configuration option to disable KSM for specific VMs that need to be
> protected against such attacks. This makes it possible to still
> benefit from KSM for other processes on the host rather than needing
> to turn of KSM completely.
> 
> 
> [...]

Applied a bit ago already, thanks!

[1/3] close #5291: support disabling KSM for specific VMs
      commit: ae91d137c1e993031385da594c37c61e4295dc97


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-11-17 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 15:51 [pve-devel] [PATCH-SERIES qemu-server/manager/docs v2 0/3] " Fiona Ebner
2025-11-13 15:51 ` [pve-devel] [PATCH qemu-server v2 1/3] " Fiona Ebner
2025-11-17 11:59   ` Thomas Lamprecht [this message]
2025-11-13 15:51 ` [pve-devel] [PATCH manager v2 2/3] close #5291: ui: qemu: memory edit: " Fiona Ebner
2025-11-14 21:02   ` [pve-devel] applied: " Thomas Lamprecht
2025-11-13 15:51 ` [pve-devel] [PATCH docs v2 3/3] kernel samepage merging: describe how to disable for a specific VM Fiona Ebner
2025-11-14 21:08   ` [pve-devel] applied: " Thomas Lamprecht

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=176338078415.3512763.15001247617317199659.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal