search for: pte_rdon

Displaying 3 results from an estimated 3 matches for "pte_rdon".

Did you mean: perdon
2024 Jan 24
1
[PATCH] mm: Remove double faults once write a device pfn
...>> >>>> What? How do you got to this conclusion? >> >>> Sorry. I did not mention that this problem only exists on arm64 platform. >> >> Ok, that makes at least a little bit more sense. >> >> >> >>> Because on arm64 platform the PTE_RDONLY is automatically attached >> >>> to the userspace pte entries even through VM_WRITE + VM_SHARE. >> >>> The PTE_RDONLY needs to be cleared in vmf_insert_pfn_prot. However >> >>> vmf_insert_pfn_prot do not make the pte writable passing false >> &g...
2024 Jan 23
2
[PATCH] mm: Remove double faults once write a device pfn
...pfn writable so the pte entry is normally read-only or dirty >>> catching. >> What? How do you got to this conclusion? > Sorry. I did not mention that this problem only exists on arm64 platform. Ok, that makes at least a little bit more sense. > Because on arm64 platform the PTE_RDONLY is automatically attached to > the userspace pte entries even through VM_WRITE + VM_SHARE. > The PTE_RDONLY needs to be cleared in vmf_insert_pfn_prot. However > vmf_insert_pfn_prot do not make the pte writable passing false @mkwrite > to insert_pfn. Question is why is arm64 doing t...
2024 Jan 24
2
[PATCH] mm: Remove double faults once write a device pfn
...only or dirty >>>>> catching. >>>> What? How do you got to this conclusion? >>> Sorry. I did not mention that this problem only exists on arm64 platform. >> Ok, that makes at least a little bit more sense. >> >>> Because on arm64 platform the PTE_RDONLY is automatically attached to >>> the userspace pte entries even through VM_WRITE + VM_SHARE. >>> The PTE_RDONLY needs to be cleared in vmf_insert_pfn_prot. However >>> vmf_insert_pfn_prot do not make the pte writable passing false >>> @mkwrite to insert_pfn. &...