Regression with xhci console (was: [PATCH 1/4] amd-vi: fix IVMD memory type checks)

2024-03-10 Thread Marek Marczykowski-Górecki
On Thu, Feb 01, 2024 at 06:01:56PM +0100, Roger Pau Monne wrote: > The current code that parses the IVMD blocks is relaxed with regard to the > restriction that such unity regions should always fall into memory ranges > marked as reserved in the memory map. > > However the type checks for the

Re: [PATCH 1/4] amd-vi: fix IVMD memory type checks

2024-02-06 Thread Jan Beulich
On 01.02.2024 18:01, Roger Pau Monne wrote: > The current code that parses the IVMD blocks is relaxed with regard to the > restriction that such unity regions should always fall into memory ranges > marked as reserved in the memory map. > > However the type checks for the IVMD addresses are

Re: [PATCH 1/4] amd-vi: fix IVMD memory type checks

2024-02-02 Thread oxjo
On Thursday, February 1st, 2024 at 18:01, Roger Pau Monne wrote: > The current code that parses the IVMD blocks is relaxed with regard to the > restriction that such unity regions should always fall into memory ranges > marked as reserved in the memory map. > > However the type checks for the

[PATCH 1/4] amd-vi: fix IVMD memory type checks

2024-02-01 Thread Roger Pau Monne
The current code that parses the IVMD blocks is relaxed with regard to the restriction that such unity regions should always fall into memory ranges marked as reserved in the memory map. However the type checks for the IVMD addresses are inverted, and as a result IVMD ranges falling into RAM