| /linux-4.4.14/drivers/infiniband/hw/usnic/ |
| D | usnic_uiom.c | 100 static int usnic_uiom_get_pages(unsigned long addr, size_t size, int writable, in usnic_uiom_get_pages() argument
142 flags |= (writable) ? IOMMU_WRITE : 0; in usnic_uiom_get_pages()
150 1, !writable, page_list, NULL); in usnic_uiom_get_pages()
223 int writable = 0; in __usnic_uiom_reg_release() local
237 writable = 1; in __usnic_uiom_reg_release()
242 usnic_uiom_put_pages(&uiomr->chunk_list, dirty & writable); in __usnic_uiom_reg_release()
261 flags |= (uiomr->writable) ? IOMMU_WRITE : 0; in usnic_uiom_map_sorted_intervals()
338 int writable, int dmasync) in usnic_uiom_reg_get() argument
353 writable = 1; in usnic_uiom_reg_get()
368 uiomr->writable = writable; in usnic_uiom_reg_get()
[all …]
|
| D | usnic_uiom.h | 69 int writable; member
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | locking.txt | 21 - SPTE_HOST_WRITEABLE means the gfn is writable on host.
22 - SPTE_MMU_WRITEABLE means the gfn is writable on mmu. The bit is set when
23 the gfn is writable on guest mmu and it is not write-protected by shadow
66 - The pfn is writable that means it can not be shared between different gfns
80 writable between reading spte and updating spte. Like below case:
118 If the spte is updated from writable to readonly, we should flush all TLBs,
120 writable spte might be cached on a CPU's TLB.
122 As mentioned before, the spte can be updated to writable out of mmu-lock on
|
| D | timekeeping.txt | 325 has been lifted and all 64-bits are writable. On AMD systems, the ability to
|
| /linux-4.4.14/drivers/mfd/ |
| D | wm8350-regmap.c | 23 u16 writable; /* Mask of writable bits */ member
302 return wm8350_reg_io_map[reg].writable; in wm8350_writeable()
|
| /linux-4.4.14/virt/kvm/ |
| D | kvm_main.c | 1254 gfn_t gfn, bool *writable) in gfn_to_hva_memslot_prot() argument
1258 if (!kvm_is_error_hva(hva) && writable) in gfn_to_hva_memslot_prot()
1259 *writable = !memslot_is_readonly(slot); in gfn_to_hva_memslot_prot()
1264 unsigned long gfn_to_hva_prot(struct kvm *kvm, gfn_t gfn, bool *writable) in gfn_to_hva_prot() argument
1268 return gfn_to_hva_memslot_prot(slot, gfn, writable); in gfn_to_hva_prot()
1271 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
1275 return gfn_to_hva_memslot_prot(slot, gfn, writable); in kvm_vcpu_gfn_to_hva_prot()
1303 bool write_fault, bool *writable, pfn_t *pfn) in hva_to_pfn_fast() argument
1316 if (!(write_fault || writable)) in hva_to_pfn_fast()
1323 if (writable) in hva_to_pfn_fast()
[all …]
|
| /linux-4.4.14/drivers/infiniband/core/ |
| D | umem.c | 61 if (umem->writable && dirty) in __ib_umem_release()
132 umem->writable = !!(access & in ib_umem_get()
194 1, !umem->writable, page_list, vma_list); in ib_umem_get()
|
| /linux-4.4.14/arch/arm/kvm/ |
| D | mmu.c | 965 phys_addr_t pa, unsigned long size, bool writable) in kvm_phys_addr_ioremap() argument
978 if (writable) in kvm_phys_addr_ioremap()
1220 bool write_fault, writable, hugetlb = false, force_pte = false; in user_mem_abort() local
1284 pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, &writable); in user_mem_abort()
1305 writable = false; in user_mem_abort()
1320 if (writable) { in user_mem_abort()
1329 if (writable) { in user_mem_abort()
1403 bool is_iabt, write_fault, writable; in kvm_handle_guest_abort() local
1428 hva = gfn_to_hva_memslot_prot(memslot, gfn, &writable); in kvm_handle_guest_abort()
1430 if (kvm_is_error_hva(hva) || (write_fault && !writable)) { in kvm_handle_guest_abort()
[all …]
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig-nommu | 48 vectors to be mapped to writable memory, say 'n' here.
52 the writable versions located at DRAM_BASE.
|
| /linux-4.4.14/Documentation/vm/ |
| D | soft-dirty.txt | 20 Internally, to do this tracking, the writable bit is cleared from PTEs
28 the kernel does is finds this fact out and puts both writable and soft-dirty
|
| D | overcommit-accounting | 61 Pages made writable copies by mmap
|
| D | ksm.txt | 51 readable by all but writable only by root:
|
| D | slub.txt | 79 Look at the writable files. Writing 1 to them will enable the
|
| /linux-4.4.14/drivers/misc/eeprom/ |
| D | at24.c | 478 bool writable; in at24_probe() local
588 writable = !(chip.flags & AT24_FLAG_READONLY); in at24_probe()
589 if (writable) { in at24_probe()
638 writable ? "writable" : "read-only", at24->write_max); in at24_probe()
|
| /linux-4.4.14/arch/powerpc/kvm/ |
| D | book3s_32_mmu_host.c | 157 bool writable; in kvmppc_mmu_map_page() local
160 hpaddr = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
210 if (orig_pte->may_write && writable) { in kvmppc_mmu_map_page()
|
| D | book3s_64_mmu_host.c | 96 bool writable; in kvmppc_mmu_map_page() local
108 pfn = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
136 if (!orig_pte->may_write || !writable) in kvmppc_mmu_map_page()
|
| D | book3s.c | 370 bool *writable) in kvmppc_gpa_to_pfn() argument
386 if (writable) in kvmppc_gpa_to_pfn()
387 *writable = true; in kvmppc_gpa_to_pfn()
391 return gfn_to_pfn_prot(vcpu->kvm, gfn, writing, writable); in kvmppc_gpa_to_pfn()
|
| /linux-4.4.14/Documentation/frv/ |
| D | clock.txt | 13 On all boards, the 'p0' file should also be writable, and either '1' or '0'
23 writable, allowing the CPU core speed (and other clock speeds) to be
|
| /linux-4.4.14/include/rdma/ |
| D | ib_umem.h | 48 int writable; member
|
| /linux-4.4.14/mm/ |
| D | rmap.c | 630 tlb_ubc->writable = false; in try_to_unmap_flush()
639 if (tlb_ubc->writable) in try_to_unmap_flush_dirty()
644 struct page *page, bool writable) in set_tlb_ubc_flush_pending() argument
656 if (writable) in set_tlb_ubc_flush_pending()
657 tlb_ubc->writable = true; in set_tlb_ubc_flush_pending()
680 struct page *page, bool writable) in set_tlb_ubc_flush_pending() argument
|
| D | huge_memory.c | 2203 bool referenced = false, writable = false; in __collapse_huge_page_isolate() local
2244 writable = true; in __collapse_huge_page_isolate()
2275 if (likely(referenced && writable)) in __collapse_huge_page_isolate()
2651 bool writable = false, referenced = false; in khugepaged_scan_pmd() local
2674 writable = true; in khugepaged_scan_pmd()
2704 if (referenced && writable) in khugepaged_scan_pmd()
|
| D | hugetlb.c | 3024 int writable) in make_huge_pte() argument
3028 if (writable) { in make_huge_pte()
3037 entry = arch_make_huge_pte(entry, vma, page, writable); in make_huge_pte()
|
| /linux-4.4.14/arch/tile/include/asm/ |
| D | hugetlb.h | 103 struct page *page, int writable) in arch_make_huge_pte() argument
|
| /linux-4.4.14/Documentation/w1/slaves/ |
| D | w1_ds2406 | 21 work with. output is writable; bits 0 and 1 control PIO A and B,
|
| /linux-4.4.14/fs/nilfs2/ |
| D | Kconfig | 18 its writable mount, and this feature is convenient for online backup.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-kernel-livepatch | 24 A writable attribute that indicates whether the patched
|
| D | sysfs-class-scsi_host | 29 controller. This file is readable and writable.
|
| D | sysfs-class-mtd | 63 0x0400: MTD_WRITEABLE - device is writable
114 Minimal writable flash unit size. This will always be
|
| D | sysfs-bus-pci | 137 underlying VPD has a writable section then the
138 corresponding section of this file will be writable.
|
| D | sysfs-kernel-slab | 345 allocated. It is writable and can be changed to increase the
|
| D | sysfs-bus-iio | 282 May be writable if a variable offset can be applied on the
|
| /linux-4.4.14/include/linux/ |
| D | kvm_host.h | 597 unsigned long gfn_to_hva_prot(struct kvm *kvm, gfn_t gfn, bool *writable);
600 bool *writable);
608 bool *writable);
612 bool *async, bool write_fault, bool *writable);
647 unsigned long kvm_vcpu_gfn_to_hva_prot(struct kvm_vcpu *vcpu, gfn_t gfn, bool *writable);
|
| D | hugetlb.h | 424 struct page *page, int writable) in arch_make_huge_pte() argument
|
| D | sched.h | 1377 bool writable; member
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm77 | 34 temp1_crit_hyst writable, while temp1_min_hyst and temp1_max_hyst are
|
| D | emc1403 | 55 only temp1_crit_hyst writable, while all other hysteresis attributes
|
| D | vt1211 | 176 the first set pwm1_auto_point[1-4]_temp is writable, the second set is
|
| /linux-4.4.14/drivers/hwtracing/intel_th/ |
| D | gth.c | 251 .writable = (_w) }
260 writable : 1; member
447 if (output_parms[j].writable) { in intel_th_output_attributes()
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | powersave.txt | 24 The power_save option is exported as writable. This means you can
|
| /linux-4.4.14/fs/jffs2/ |
| D | TODO | 6 do shared writable mmap, if we can have a fs hook for do_wp_page() to
|
| /linux-4.4.14/arch/arm/include/asm/ |
| D | kvm_mmu.h | 60 phys_addr_t pa, unsigned long size, bool writable);
|
| /linux-4.4.14/arch/arm64/include/asm/ |
| D | kvm_mmu.h | 92 phys_addr_t pa, unsigned long size, bool writable);
|
| /linux-4.4.14/drivers/block/drbd/ |
| D | Kconfig | 31 DRBD can also be used in dual-Primary mode (device writable on both
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | fs.txt | 188 time-of-check-time-of-use race, most commonly seen in world-writable
208 time-of-check-time-of-use race, most commonly seen in world-writable
218 a sticky world-writable directory, or when the uid of the symlink and
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | device.txt | 41 Raw value writing function. Used for writable device values such
|
| /linux-4.4.14/fs/btrfs/ |
| D | Kconfig | 15 writable snapshotting, support for multiple devices and many more
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | persistent-data.txt | 44 The only way you can get hold of a writable block through the
|
| D | snapshot.txt | 7 the block device which are also writable without interfering with the
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | fw-cfg.txt | 16 the selected entry is writable, the guest can rewrite it through the data
|
| /linux-4.4.14/arch/powerpc/include/asm/ |
| D | kvm_book3s.h | 158 bool *writable);
|
| /linux-4.4.14/arch/s390/kvm/ |
| D | priv.c | 967 bool writable; in handle_tprot() local
1001 hva = gfn_to_hva_prot(vcpu->kvm, gpa_to_gfn(gpa), &writable); in handle_tprot()
1005 if (!writable) in handle_tprot()
|
| D | kvm-s390.h | 235 long kvm_arch_fault_in_page(struct kvm_vcpu *vcpu, gpa_t gpa, int writable);
|
| D | kvm-s390.c | 1888 long kvm_arch_fault_in_page(struct kvm_vcpu *vcpu, gpa_t gpa, int writable) in kvm_arch_fault_in_page() argument
1891 writable ? FAULT_FLAG_WRITE : 0); in kvm_arch_fault_in_page()
|
| /linux-4.4.14/Documentation/security/ |
| D | Yama.txt | 47 The sysctl settings (writable only with CAP_SYS_PTRACE) are:
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | romfs.txt | 166 a writable file system, thus negating the size advantages. Possible
168 similarly small writable filesystem for RAM disks.
|
| D | overlayfs.txt | 46 not need to be writable. The lower filesystem can even be another
47 overlayfs. The upper filesystem will normally be writable and if it
|
| D | sysfs-pci.txt | 50 rw - file is readable and writable
|
| D | nilfs2.txt | 19 concurrently with its writable mount, and this feature is convenient
|
| D | vfat.txt | 33 writable, utime(2) is also allowed. I.e. ~dmask & 022)
|
| D | vfs.txt | 283 unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
|
| /linux-4.4.14/fs/nfsd/ |
| D | nfs4proc.c | 95 u32 *bmval, u32 *writable) in check_attr_support() argument
120 if (writable) { in check_attr_support()
121 if ((bmval[0] & ~writable[0]) || (bmval[1] & ~writable[1]) || in check_attr_support()
122 (bmval[2] & ~writable[2])) in check_attr_support()
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | packet-writing.txt | 68 DVD-RAM discs are random writable, so using the pktcdvd driver is not
|
| /linux-4.4.14/drivers/power/ |
| D | smb347-charger.c | 616 static int smb347_set_writable(struct smb347_charger *smb, bool writable) in smb347_set_writable() argument
619 writable ? CMD_A_ALLOW_WRITE : 0); in smb347_set_writable()
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | cdrom.txt | 66 CDROM_NEXT_WRITABLE get next writable block
932 CDROM_NEXT_WRITABLE get next writable block
942 The next writable block.
|
| /linux-4.4.14/net/unix/ |
| D | af_unix.c | 2671 unsigned int mask, writable; in unix_dgram_poll() local
2703 writable = unix_writable(sk); in unix_dgram_poll()
2704 if (writable) { in unix_dgram_poll()
2711 writable = 0; in unix_dgram_poll()
2716 if (writable) in unix_dgram_poll()
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | armada-370-netgear-rn102.dts | 176 /* Last MB is for the BBT, i.e. not writable */
|
| D | armada-385-linksys.dtsi | 181 * 38MB, last MB is for the BBT, not writable
|
| D | armada-370-netgear-rn104.dts | 189 /* Last MB is for the BBT, i.e. not writable */
|
| D | armada-xp-linksys-mamba.dts | 264 * 38MB, last MB is for the BBT, not writable
|
| D | armada-xp-netgear-rn2120.dts | 218 /* Last MB is for the BBT, i.e. not writable */
|
| /linux-4.4.14/Documentation/ |
| D | rfkill.txt | 25 - soft block: writable radio block (need not be readable) that is set by
|
| D | nommu-mmap.txt | 84 case, a shared-writable memory mapping will be possible. It will work
218 assumed to be readable and writable, not executable, and only shareable
|
| D | ntb.txt | 7 registers are read-and-writable registers that are accessible from either side
|
| D | debugging-via-ohci1394.txt | 107 controller implements a writable Physical Upper Bound register. This is
|
| D | cachetlb.txt | 283 user space shared/writable mappings of this page potentially
300 which have shared+writable mappings of this file, we must make
|
| D | md.txt | 505 This file is writable, and each of the strings that could be
604 number of entries in the stripe cache. This is writable, but
|
| D | DMA-API.txt | 513 dma_alloc_coherent() be directly writable.
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | mwave | 33 readable and writable before it can be edited. This can be done with
|
| /linux-4.4.14/drivers/thermal/ |
| D | Kconfig | 46 bool "Enable writable trip points"
50 writable trips need to be specified when setting up the
|
| /linux-4.4.14/Documentation/gpio/ |
| D | gpio.txt | 43 - Output values are writable (high=1, low=0). Some chips also have
|
| D | gpio-legacy.txt | 30 - Output values are writable (high=1, low=0). Some chips also have
|
| /linux-4.4.14/drivers/infiniband/hw/mlx5/ |
| D | odp.c | 235 if (mr->umem->writable) in pagefault_single_data_segment()
|
| /linux-4.4.14/arch/tile/include/hv/ |
| D | hypervisor.h | 2404 _HV_BIT(writable, WRITABLE) in _HV_BIT()
|
| /linux-4.4.14/Documentation/fb/ |
| D | viafb.txt | 218 These two files are readable and writable. iga1 and iga2 are the two
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | uvcvideo.txt | 207 must point to a valid writable buffer big enough to hold the indicated
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | Assabet | 128 convenient way to store a writable filesystem into flash. JFFS2 is used in
|
| /linux-4.4.14/Documentation/usb/ |
| D | mass-storage.txt | 42 read, but (if the logical unit is writable) due to buffering on
|
| D | proc_usb_info.txt | 75 Note that since by default these BBB/DDD files are writable only by
|
| D | power-management.txt | 666 This writable flag controls the state of an idle port.
|
| /linux-4.4.14/Documentation/networking/ |
| D | netlink_mmap.txt | 43 mapping still needs to be writable in order to update the frame status after
|
| D | cdc_mbim.txt | 32 The parameter is writable, and can be changed at any time. A manual
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 177 All writable architected system registers at the exception level where
|
| /linux-4.4.14/drivers/mtd/ |
| D | Kconfig | 105 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
|
| /linux-4.4.14/arch/x86/kvm/ |
| D | mmu.c | 2977 gva_t gva, pfn_t *pfn, bool write, bool *writable);
3446 gva_t gva, pfn_t *pfn, bool write, bool *writable) in try_async_pf() argument
3453 *pfn = __gfn_to_pfn_memslot(slot, gfn, false, &async, write, writable); in try_async_pf()
3467 *pfn = __gfn_to_pfn_memslot(slot, gfn, false, NULL, write, writable); in try_async_pf()
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | networking.xml.db | 60 API-skb-clone-writable
|
| /linux-4.4.14/drivers/md/ |
| D | Kconfig | 275 Allow volume managers to take writable snapshots of a device.
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 201 attribute is writable and provides a ->store method, that method will be
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 518 writable by root only, and some are writable by everyone. Unless you
520 writable by root only alone. Most of the names are self explanatory.
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 355 writable control files located in procfs (for system wide settings).
|
| /linux-4.4.14/Documentation/x86/ |
| D | boot.txt | 20 writable.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_mid_low_api.txt | 135 those that are writable after the driver is loaded) could also be
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1423 Also, the /dev/net/tun device must be writable by the user running
1433 Making it world-writable looks bad, but it seems not to be
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 896 markers - When set, the trace_marker is writable (only by root).
|