From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-kernel/master 0/2] fix two small issues with IOMMU in certain setups
Date: Wed, 27 Nov 2024 20:24:44 +0100 [thread overview]
Message-ID: <63acc1f8-bd29-4c07-8c92-cf659bba9701@proxmox.com> (raw)
In-Reply-To: <20241126163636.825951-1-s.ivanov@proxmox.com>
Am 26.11.24 um 17:36 schrieb Stoiko Ivanov:
> stubled across https://bugzilla.proxmox.com/show_bug.cgi?id=5926 which
> mentioned kernel-issues related to the 8.3.0 release - so took a quick look.
>
> While I think that the issues were not directly related to 8.3 (or the
> kernel version shipped with it (see bugzilla)) - one issue seemed to
> be easily addressable with a cherry-pick from kernel.org stable-6.11.7
> (patch 1/2)
>
> the second patch addresses an unrleated issue reported in our forums:
> https://forum.proxmox.com/threads/.157266
> see the commit-message of the patch for a bit more information - but it
> basically reverts a patch from Ubuntu-upstream, as this broke iGPU
> passthrough for old Intel-CPUs (without the patch users affected by the
> issue reported to Ubuntu had the options of disabling iommu via
> kernel-cmdline anyways).
>
> I'd suggest pulling patch 2/2 also for our kernel 6.8.
done
> Stoiko Ivanov (2):
> fix #5926: cherry-pick ACS-quirk fix from linux-stable/6.11.7
> revert Ubuntu patch disabling IOMMU functionality for Skylake iGPU
>
> ...nable_acs-support-for-the-ACS-quirks.patch | 68 +++++++++++++++++++
> ...UCE-iommu-intel-disable-DMAR-for-SKL.patch | 53 +++++++++++++++
> 2 files changed, 121 insertions(+)
> create mode 100644 patches/kernel/0016-PCI-Fix-pci_enable_acs-support-for-the-ACS-quirks.patch
> create mode 100644 patches/kernel/0017-Revert-UBUNTU-SAUCE-iommu-intel-disable-DMAR-for-SKL.patch
>
applied series, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-27 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 16:36 [pve-devel] " Stoiko Ivanov
2024-11-26 16:36 ` [pve-devel] [PATCH pve-kernel/master 1/2] fix #5926: cherry-pick ACS-quirk fix from linux-stable/6.11.7 Stoiko Ivanov
2024-11-26 16:36 ` [pve-devel] [PATCH pve-kernel/master 2/2] revert Ubuntu patch disabling IOMMU functionality for Skylake iGPU Stoiko Ivanov
2024-11-27 19:24 ` Thomas Lamprecht [this message]
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=63acc1f8-bd29-4c07-8c92-cf659bba9701@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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