From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/3] pci-passthrough: mention that `intel_iommu=on` is the default for 6.8+
Date: Tue, 22 Oct 2024 12:19:38 +0200 [thread overview]
Message-ID: <20241022101941.329529-3-c.heiss@proxmox.com> (raw)
In-Reply-To: <20241022101941.329529-1-c.heiss@proxmox.com>
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
qm-pci-passthrough.adoc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
index c3dd184..70e33f2 100644
--- a/qm-pci-passthrough.adoc
+++ b/qm-pci-passthrough.adoc
@@ -74,7 +74,8 @@ xref:sysboot_edit_kernel_cmdline[kernel command line] kernels by adding:
intel_iommu=on
----
-For AMD CPUs it should be enabled automatically.
+For AMD CPUs it should be enabled automatically. For Intel CPUs this is also
+the default since the 6.8 kernel series.
.IOMMU Passthrough Mode
--
2.46.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-10-22 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 10:19 [pve-devel] [PATCH docs 0/3] pci-passthrough: update section for newer kernels, add mdev driver note Christoph Heiss
2024-10-22 10:19 ` [pve-devel] [PATCH docs 1/3] pci-passthrough: drop obsolete `vfio_virqfd` kernel module requirement Christoph Heiss
2024-10-22 10:19 ` Christoph Heiss [this message]
2024-10-29 13:17 ` [pve-devel] [PATCH docs 2/3] pci-passthrough: mention that `intel_iommu=on` is the default for 6.8+ Aaron Lauterer
2024-10-22 10:19 ` [pve-devel] [PATCH docs 3/3] pci-passthrough: add note about mediated devices w.r.t kernel modules Christoph Heiss
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=20241022101941.329529-3-c.heiss@proxmox.com \
--to=c.heiss@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