Home
last modified time | relevance | path

Searched refs:writable (Results 1 – 25 of 131) sorted by relevance

123456

/Linux-v5.4/include/trace/events/
Dhuge_memory.h50 TP_PROTO(struct mm_struct *mm, struct page *page, bool writable,
53 TP_ARGS(mm, page, writable, referenced, none_or_zero, status, unmapped),
58 __field(bool, writable)
68 __entry->writable = writable;
78 __entry->writable,
112 int referenced, bool writable, int status),
114 TP_ARGS(page, none_or_zero, referenced, writable, status),
120 __field(bool, writable)
128 __entry->writable = writable;
136 __entry->writable,
/Linux-v5.4/drivers/infiniband/hw/usnic/
Dusnic_uiom.c85 static int usnic_uiom_get_pages(unsigned long addr, size_t size, int writable, in usnic_uiom_get_pages() argument
137 flags |= (writable) ? IOMMU_WRITE : 0; in usnic_uiom_get_pages()
139 gup_flags |= (writable) ? 0 : FOLL_FORCE; in usnic_uiom_get_pages()
221 int writable = 0; in __usnic_uiom_reg_release() local
235 writable = 1; in __usnic_uiom_reg_release()
240 usnic_uiom_put_pages(&uiomr->chunk_list, dirty & writable); in __usnic_uiom_reg_release()
259 flags |= (uiomr->writable) ? IOMMU_WRITE : 0; in usnic_uiom_map_sorted_intervals()
336 int writable, int dmasync) in usnic_uiom_reg_get() argument
351 writable = 1; in usnic_uiom_reg_get()
366 uiomr->writable = writable; in usnic_uiom_reg_get()
[all …]
Dusnic_uiom.h71 int writable; member
/Linux-v5.4/drivers/mfd/
Dwm8350-regmap.c19 u16 writable; /* Mask of writable bits */ member
298 return wm8350_reg_io_map[reg].writable; in wm8350_writeable()
/Linux-v5.4/drivers/infiniband/hw/hfi1/
Duser_pages.c104 bool writable, struct page **pages) in hfi1_acquire_user_pages() argument
107 unsigned int gup_flags = FOLL_LONGTERM | (writable ? FOLL_WRITE : 0); in hfi1_acquire_user_pages()
/Linux-v5.4/tools/testing/selftests/kvm/lib/x86_64/
Dprocessor.c21 uint64_t writable:1; member
36 uint64_t writable:1; member
51 uint64_t writable:1; member
66 uint64_t writable:1; member
295 pml4e[index[3]].writable = true; in virt_pg_map()
306 pdpe[index[2]].writable = true; in virt_pg_map()
317 pde[index[1]].writable = true; in virt_pg_map()
325 pte[index[0]].writable = true; in virt_pg_map()
369 pml4e->writable, pml4e->execute_disable); in virt_dump()
382 (uint64_t) pdpe->address, pdpe->writable, in virt_dump()
[all …]
Dvmx.c22 uint64_t writable:1; member
426 pml4e[index[3]].writable = true; in nested_pg_map()
438 pdpe[index[2]].writable = true; in nested_pg_map()
450 pde[index[1]].writable = true; in nested_pg_map()
459 pte[index[0]].writable = true; in nested_pg_map()
/Linux-v5.4/Documentation/virt/kvm/
Dlocking.txt40 - SPTE_HOST_WRITEABLE means the gfn is writable on host.
41 - SPTE_MMU_WRITEABLE means the gfn is writable on mmu. The bit is set when
42 the gfn is writable on guest mmu and it is not write-protected by shadow
86 - The pfn is writable that means it can not be shared between different gfns
100 writable between reading spte and updating spte. Like below case:
138 If the spte is updated from writable to readonly, we should flush all TLBs,
140 writable spte might be cached on a CPU's TLB.
142 As mentioned before, the spte can be updated to writable out of mmu-lock on
/Linux-v5.4/drivers/infiniband/sw/siw/
Dsiw_mem.c78 umem->writable && dirty); in siw_umem_release()
368 struct siw_umem *siw_umem_get(u64 start, u64 len, bool writable) in siw_umem_get() argument
393 umem->writable = writable; in siw_umem_get()
397 if (!writable) in siw_umem_get()
/Linux-v5.4/virt/kvm/
Dkvm_main.c1475 gfn_t gfn, bool *writable) in gfn_to_hva_memslot_prot() argument
1479 if (!kvm_is_error_hva(hva) && writable) in gfn_to_hva_memslot_prot()
1480 *writable = !memslot_is_readonly(slot); in gfn_to_hva_memslot_prot()
1485 unsigned long gfn_to_hva_prot(struct kvm *kvm, gfn_t gfn, bool *writable) in gfn_to_hva_prot() argument
1489 return gfn_to_hva_memslot_prot(slot, gfn, writable); in gfn_to_hva_prot()
1492 unsigned long kvm_vcpu_gfn_to_hva_prot(struct kvm_vcpu *vcpu, gfn_t gfn, bool *writable) in kvm_vcpu_gfn_to_hva_prot() argument
1496 return gfn_to_hva_memslot_prot(slot, gfn, writable); in kvm_vcpu_gfn_to_hva_prot()
1513 bool *writable, kvm_pfn_t *pfn) in hva_to_pfn_fast() argument
1523 if (!(write_fault || writable)) in hva_to_pfn_fast()
1530 if (writable) in hva_to_pfn_fast()
[all …]
/Linux-v5.4/drivers/infiniband/core/
Dumem.c57 put_user_pages_dirty_lock(&page, 1, umem->writable && dirty); in __ib_umem_release()
237 umem->writable = ib_access_writable(access); in ib_umem_get()
268 if (!umem->writable) in ib_umem_get()
Dumem_odp.c316 umem->writable = ib_access_writable(access); in ib_umem_odp_alloc_implicit()
360 umem->writable = root->umem.writable; in ib_umem_odp_alloc_child()
412 umem_odp->umem.writable = ib_access_writable(access); in ib_umem_odp_get()
/Linux-v5.4/virt/kvm/arm/
Dmmu.c1335 phys_addr_t pa, unsigned long size, bool writable) in kvm_phys_addr_ioremap() argument
1348 if (writable) in kvm_phys_addr_ioremap()
1669 bool write_fault, writable, force_pte = false; in user_mem_abort() local
1736 pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, &writable); in user_mem_abort()
1760 writable = false; in user_mem_abort()
1781 if (writable) in user_mem_abort()
1805 if (writable) in user_mem_abort()
1817 if (writable) in user_mem_abort()
1827 if (writable) { in user_mem_abort()
1905 bool is_iabt, write_fault, writable; in kvm_handle_guest_abort() local
[all …]
/Linux-v5.4/drivers/misc/eeprom/
Dat24.c568 bool writable; in at24_probe() local
669 writable = !(flags & AT24_FLAG_READONLY); in at24_probe()
670 if (writable) { in at24_probe()
686 nvmem_config.read_only = !writable; in at24_probe()
721 writable ? "writable" : "read-only", at24->write_max); in at24_probe()
/Linux-v5.4/arch/arm/
DKconfig-nommu50 vectors to be mapped to writable memory, say 'n' here.
54 the writable versions located at DRAM_BASE.
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-kernel-livepatch24 A writable attribute that indicates whether the patched
41 A writable attribute that allows administrator to affect the
/Linux-v5.4/Documentation/admin-guide/mm/
Dsoft-dirty.rst24 Internally, to do this tracking, the writable bit is cleared from PTEs
32 the kernel does is finds this fact out and puts both writable and soft-dirty
/Linux-v5.4/include/linux/
Dmm_types_task.h95 bool writable; member
/Linux-v5.4/Documentation/security/
Dself-protection.rst37 APIs hard to use incorrectly, minimizing the areas of writable kernel
43 When all of kernel memory is writable, it becomes trivial for attacks
47 Executable code and read-only data must not be writable
50 Any areas of the kernel with executable memory must not be writable.
56 made writable during the update, and then returned to the original
61 writable, data is not executable, and read-only data is neither writable
70 Function pointers and sensitive variables must not be writable
/Linux-v5.4/arch/powerpc/kvm/
Dbook3s_32_mmu_host.c145 bool writable; in kvmppc_mmu_map_page() local
148 hpaddr = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
198 if (orig_pte->may_write && writable) { in kvmppc_mmu_map_page()
Dbook3s_64_mmu_host.c84 bool writable; in kvmppc_mmu_map_page() local
96 pfn = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
124 if (!orig_pte->may_write || !writable) in kvmppc_mmu_map_page()
/Linux-v5.4/Documentation/admin-guide/sysctl/
Dfs.rst211 in world writable sticky directories, unless they are owned by the
214 When set to "2" it also applies to group writable sticky directories.
223 time-of-check-time-of-use race, most commonly seen in world-writable
249 don't own in world writable sticky directories, unless they are
252 When set to "2" it also applies to group writable sticky directories.
259 time-of-check-time-of-use race, most commonly seen in world-writable
269 a sticky world-writable directory, or when the uid of the symlink and
/Linux-v5.4/arch/arm64/include/asm/
Dhugetlb.h38 struct page *page, int writable);
/Linux-v5.4/include/rdma/
Dib_umem.h49 u32 writable : 1; member
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-g-audioout.rst52 Audio outputs have no writable properties. Nevertheless, to select the
54 ``reserved`` array (which in the future may contain writable properties)

123456