From: Christoph Heiss <c.heiss@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 2/3] pci-passthrough: mention that `intel_iommu=on` is the default for 6.8+
Date: Thu, 31 Oct 2024 10:53:08 +0100 [thread overview]
Message-ID: <rwmkzv62wslyvqlergtdxvur4gismexihrreyjvcuzm7h2dxkx@xvjgllzoefzs> (raw)
In-Reply-To: <9ddd8807-5623-484f-aa5d-b751d732ae53@proxmox.com>
Thanks for taking a look!
On Tue, Oct 29, 2024 at 02:17:59PM GMT, Aaron Lauterer wrote:
> Looking at the surrounding context, I would rework this section even more.
> Before I just apply my approach, what do you think about the following
> change?
> ---
> diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
> index 4f19f2a..ca07692 100644
> --- a/qm-pci-passthrough.adoc
> +++ b/qm-pci-passthrough.adoc
> @@ -63,19 +63,18 @@ some configuration to enable PCI(e) passthrough.
>
> .IOMMU
>
> -First, you will have to enable IOMMU support in your BIOS/UEFI. Usually the
> +You will have to enable IOMMU support in your BIOS/UEFI. Usually the
> corresponding setting is called `IOMMU` or `VT-d`, but you should find the
> exact
> option name in the manual of your motherboard.
>
> -For Intel CPUs, you also need to enable the IOMMU on the
> -xref:sysboot_edit_kernel_cmdline[kernel command line] kernels by adding:
> +With recent kernels (6.8 or newer), `IOMMU` should be enabled
I'd drop the code tags for IOMMU here (and add a "the") -- like in the
first sentence -- since this is referring to the IOMMU in a more general
sense rather than a specific setting as above such, IMO.
> automatically.
Since you drop the note about AMD CPUs below, I'd either keep that one
below or explicitly mention here that this automatic enablement is for
both Intel and AMD CPUs.
Otherwise users/admin might be left wondering what needs to be done for
AMD CPUs, if only Intel are mentioned here. Just to be thorough.
> +On older kernels, it was necessary to enable it on Intel CPUs via the
> +xref:sysboot_edit_kernel_cmdline[kernel command line] by adding:
>
> ----
> intel_iommu=on
> ----
>
> -For AMD CPUs it should be enabled automatically.
> -
> .IOMMU Passthrough Mode
>
> If your hardware supports IOMMU passthrough mode, enabling this mode might
> [..]
_______________________________________________
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-31 9:53 UTC|newest]
Thread overview: 7+ 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 ` [pve-devel] [PATCH docs 2/3] pci-passthrough: mention that `intel_iommu=on` is the default for 6.8+ Christoph Heiss
2024-10-29 13:17 ` Aaron Lauterer
2024-10-31 9:53 ` Christoph Heiss [this message]
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
2024-10-31 10:29 ` [pve-devel] applied: [PATCH docs 0/3] pci-passthrough: update section for newer kernels, add mdev driver note Aaron Lauterer
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=rwmkzv62wslyvqlergtdxvur4gismexihrreyjvcuzm7h2dxkx@xvjgllzoefzs \
--to=c.heiss@proxmox.com \
--cc=a.lauterer@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