Re: Relaxable RMRR kernel parameter for broken platforms

[bugtracker@fischbytes.de]

On Saturday, May 13, 2023 8:20:40 AM CEST you wrote:
> On 5/13/23 2:52 AM, bugtracker@fischbytes.de wrote:
> > 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.
> 
> The relaxed RMRRs are used for legacy purpose, but it requires the full
> range of memory addresses are available after the OS device driver takes
> over the control of the device.
> 
> Not all RMRRs are of this type and typically the VT-d driver only allows
> those RMRRs for USB and graphic devices as relaxed ones.
> 
> Are you proposing to add a kernel parameter to allow any RMRR for an
> arbitrary device to be relaxed, or I didn't get the idea here?
> 
> Best regards,
> baolu

Correct, the idea here is that, while this observation can only be made on 
specific hardware, it more often than not occurs that devices that definitely 
shouldn't be (like e.g. GPUs attached to the physical PCIe Interface) are 
marked as reserved by offending firmware. A perfect solution would of course be 
to force the hardware vendors to push a firmware update that resolves the 
violation of Intel's specifications, but such a thing doesn't appear to have 
happened in the past and it's very unlikely that, let's say Hewlett Packard 
Enterprise, will ever release a firmware update for those thousands of broken 
servers. 

(Quoted from here: https://github.com/Aterfax/relax-intel-rmrr/blob/master/
deep-dive.md#rmrr---the-monster-in-a-closet ;

Intel anticipated the some will be tempted to misuse the feature as they 
warned in the VT-d specification: "RMRR regions are expected to be used for 
legacy usages (...). Platform designers should avoid or limit use of reserved 
memory regions".

HP (and probably others) decided to mark every freaking PCI device memory 
space as RMRR! Like that, just in case... just that their tools could 
potentially maybe monitor these devices while OS agent is not installed. But 
wait, there's more! They marked ALL devices as such, even third party ones 
physically installed in motherboard's PCI/PCIe slots!)

Hope this could clarify my inquiry a bit more.