a3da4fc60b
Altough in the comment above the pmap_change_attr() it was mentioned that VA could be in KV or DMAP memory space. However, pmap_change_attr_locked() was accepting only the values inside the DMAP memory range. To fix that, the condition check was changed so also the va inside the KV memory range would be accepted. The sample use case that wasn't supported is the PCI Device that has the BAR which should me mapped with the Write Combine attribute - for example BAR2 of the ENA network controller on the A1 instances on AWS. Tested on A1 AWS instance and changed ENA BAR2 mapped resource to be write-combined memory region. Differential Revision: https://reviews.freebsd.org/D22055 MFC after: 2 weeks Submitted by: Michal Krawczyk <mk@semihalf.com> Obtained from: Semihalf Sponsored by: Amazon, Inc. |
||
|---|---|---|
| .. | ||
| acpica | ||
| arm64 | ||
| cavium | ||
| cloudabi32 | ||
| cloudabi64 | ||
| conf | ||
| coresight | ||
| include | ||
| intel | ||
| linux | ||
| qualcomm | ||
| rockchip | ||