Linux IOMMU Development
 help / color / mirror / Atom feed
From: bugtracker@fischbytes.de
To: iommu@lists.linux.dev
Subject: Relaxable RMRR kernel parameter for broken platforms
Date: Fri, 12 May 2023 20:52:53 +0200	[thread overview]
Message-ID: <2282218.ElGaqSPkdT@helios-lx> (raw)

Hi there,

I came here today to ask if there are any plans regarding the implementation 
of a "relaxed RMRR" kernel parameter to aid using IOMMU on broken platforms 
such as the ProLiant Series by Hewlett Packard Enterprise. To everyone not 
aware of the issue;

Certain vendors that are under the assumption that standards are for jerks and 
Intel's specifications are a loose optional guideline have implemented RMRR in 
such a way that every PCI device is marked as reserved and therefore cannot be 
passed through to a virtual machine. This issue has been very well documented 
by some people that have a lot more experience than I do at the below linked 
resource. I was hoping that the kernel devs could implement the Relaxed RMRR 
option as an optional kernel parameter to use on these bugged platforms as 
that would re-enable or rather enable a lot of broken servers for the first 
time ever to use PCIe Passthrough. I can verify the issue exists on a HPE 
DL360e Gen8 with trying to passthrough a GPU to a KVM/QEMU machine.

Link to fix: https://github.com/Aterfax/relax-intel-rmrr

Furthermore, since I am not a developer and wouldn't claim that I am competent 
enough to decide whether or not implementing this patch would present an issue 
in terms of stability or security, I was hoping that you could evaluate the 
situation. I can verify the pre-built packages for the Proxmox Linux 
environment fix the issue and behave identical in function to other systems 
that ignore RMRR completely, such as VMWare ESXi.

Thanks alot in advance, you implementing this patch would really mean a lot, 
since the hardware manufacturers just don't seem to care for fixing up this, 
erm, mess.

Skali S.



             reply	other threads:[~2023-05-12 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 18:52 bugtracker [this message]
2023-05-13  6:20 ` Relaxable RMRR kernel parameter for broken platforms Baolu Lu
2023-05-13 18:58   ` bugtracker
     [not found]   ` <1877598.tdWV9SEqCh@helios-lx>
2023-05-16  1:13     ` Baolu Lu
2023-05-22 11:42       ` Robin Murphy
2023-05-22 16:44         ` Alex Williamson
2023-05-22 18:17           ` Robin Murphy

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=2282218.ElGaqSPkdT@helios-lx \
    --to=bugtracker@fischbytes.de \
    --cc=iommu@lists.linux.dev \
    /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