mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-11-20 00:26:39 +08:00
f4142cba4e
In the OF 'translations' property, the template TTEs in the mappings never specify the executable bit. This is the case even though some of these mappings are for OF's code segment. Therefore, we need to force the execute bit on in every mapping. This problem can only really trigger on Niagara/sun4v machines and the history behind this is a little complicated. Previous to sun4v, the sun4u TTE entries lacked a hardware execute permission bit. So OF didn't have to ever worry about setting anything to handle executable pages. Any valid TTE loaded into the I-TLB would be respected by the chip. But sun4v Niagara chips have a real hardware enforced executable bit in their TTEs. So it has to be set or else the I-TLB throws an instruction access exception with type code 6 (protection violation). We've been extremely fortunate to not get bitten by this in the past. The best I can tell is that the OF's mappings for it's executable code were mapped using permanent locked mappings on sun4v in the past. Therefore, the fact that we didn't have the exec bit set in the OF translations we would use did not matter in practice. Thanks to Greg Onufer for helping me track this down. Signed-off-by: David S. Miller <davem@davemloft.net> |
||
|---|---|---|
| .. | ||
| btfixup.c | ||
| extable.c | ||
| fault_32.c | ||
| fault_64.c | ||
| generic_32.c | ||
| generic_64.c | ||
| gup.c | ||
| highmem.c | ||
| hugetlbpage.c | ||
| hypersparc.S | ||
| init_32.c | ||
| init_64.c | ||
| init_64.h | ||
| io-unit.c | ||
| iommu.c | ||
| leon_mm.c | ||
| loadmmu.c | ||
| Makefile | ||
| nosun4c.c | ||
| srmmu.c | ||
| sun4c.c | ||
| swift.S | ||
| tlb.c | ||
| tsb.c | ||
| tsunami.S | ||
| ultra.S | ||
| viking.S | ||