Home
last modified time | relevance | path

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

/linux-4.1.27/drivers/infiniband/hw/usnic/
Dusnic_uiom.c100 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 …]
Dusnic_uiom.h54 int writable; member
/linux-4.1.27/Documentation/virtual/kvm/
Dlocking.txt21 - 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
Dtimekeeping.txt325 has been lifted and all 64-bits are writable. On AMD systems, the ability to
/linux-4.1.27/drivers/mfd/
Dwm8350-regmap.c23 u16 writable; /* Mask of writable bits */ member
302 return wm8350_reg_io_map[reg].writable; in wm8350_writeable()
/linux-4.1.27/virt/kvm/
Dkvm_main.c1175 gfn_t gfn, bool *writable) in gfn_to_hva_memslot_prot() argument
1179 if (!kvm_is_error_hva(hva) && writable) in gfn_to_hva_memslot_prot()
1180 *writable = !memslot_is_readonly(slot); in gfn_to_hva_memslot_prot()
1185 unsigned long gfn_to_hva_prot(struct kvm *kvm, gfn_t gfn, bool *writable) in gfn_to_hva_prot() argument
1189 return gfn_to_hva_memslot_prot(slot, gfn, writable); in gfn_to_hva_prot()
1217 bool write_fault, bool *writable, pfn_t *pfn) in hva_to_pfn_fast() argument
1230 if (!(write_fault || writable)) in hva_to_pfn_fast()
1237 if (writable) in hva_to_pfn_fast()
1238 *writable = true; in hva_to_pfn_fast()
1250 bool *writable, pfn_t *pfn) in hva_to_pfn_slow() argument
[all …]
/linux-4.1.27/drivers/infiniband/core/
Dumem.c61 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.1.27/arch/arm/kvm/
Dmmu.c965 phys_addr_t pa, unsigned long size, bool writable) in kvm_phys_addr_ioremap() argument
978 if (writable) in kvm_phys_addr_ioremap()
1219 bool write_fault, writable, hugetlb = false, force_pte = false; in user_mem_abort() local
1283 pfn = gfn_to_pfn_prot(kvm, gfn, write_fault, &writable); in user_mem_abort()
1304 writable = false; in user_mem_abort()
1319 if (writable) { in user_mem_abort()
1328 if (writable) { in user_mem_abort()
1402 bool is_iabt, write_fault, writable; in kvm_handle_guest_abort() local
1427 hva = gfn_to_hva_memslot_prot(memslot, gfn, &writable); in kvm_handle_guest_abort()
1429 if (kvm_is_error_hva(hva) || (write_fault && !writable)) { in kvm_handle_guest_abort()
[all …]
/linux-4.1.27/arch/arm/
DKconfig-nommu48 vectors to be mapped to writable memory, say 'n' here.
52 the writable versions located at DRAM_BASE.
/linux-4.1.27/Documentation/vm/
Dsoft-dirty.txt20 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
Dovercommit-accounting61 Pages made writable copies by mmap
Dksm.txt51 readable by all but writable only by root:
Dslub.txt79 Look at the writable files. Writing 1 to them will enable the
/linux-4.1.27/arch/powerpc/kvm/
Dbook3s_32_mmu_host.c156 bool writable; in kvmppc_mmu_map_page() local
159 hpaddr = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
209 if (orig_pte->may_write && writable) { in kvmppc_mmu_map_page()
Dbook3s_64_mmu_host.c95 bool writable; in kvmppc_mmu_map_page() local
107 pfn = kvmppc_gpa_to_pfn(vcpu, orig_pte->raddr, iswrite, &writable); in kvmppc_mmu_map_page()
135 if (!orig_pte->may_write || !writable) in kvmppc_mmu_map_page()
Dbook3s.c368 bool *writable) in kvmppc_gpa_to_pfn() argument
384 if (writable) in kvmppc_gpa_to_pfn()
385 *writable = true; in kvmppc_gpa_to_pfn()
389 return gfn_to_pfn_prot(vcpu->kvm, gfn, writing, writable); in kvmppc_gpa_to_pfn()
/linux-4.1.27/drivers/misc/eeprom/
Dat24.c498 bool writable; in at24_probe() local
601 writable = !(chip.flags & AT24_FLAG_READONLY); in at24_probe()
602 if (writable) { in at24_probe()
651 writable ? "writable" : "read-only", at24->write_max); in at24_probe()
/linux-4.1.27/Documentation/frv/
Dclock.txt13 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.1.27/include/rdma/
Dib_umem.h48 int writable; member
/linux-4.1.27/arch/tile/include/asm/
Dhugetlb.h116 struct page *page, int writable) in arch_make_huge_pte() argument
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-kernel-livepatch24 A writable attribute that indicates whether the patched
Dsysfs-class-scsi_host29 controller. This file is readable and writable.
Dsysfs-class-mtd63 0x0400: MTD_WRITEABLE - device is writable
114 Minimal writable flash unit size. This will always be
Dsysfs-bus-pci137 underlying VPD has a writable section then the
138 corresponding section of this file will be writable.
Dsysfs-kernel-slab345 allocated. It is writable and can be changed to increase the
Dsysfs-bus-iio267 May be writable if a variable offset can be applied on the
/linux-4.1.27/fs/nilfs2/
DKconfig18 its writable mount, and this feature is convenient for online backup.
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds240621 work with. output is writable; bits 0 and 1 control PIO A and B,
/linux-4.1.27/Documentation/hwmon/
Dlm7734 temp1_crit_hyst writable, while temp1_min_hyst and temp1_max_hyst are
Demc140355 only temp1_crit_hyst writable, while all other hysteresis attributes
Dvt1211176 the first set pwm1_auto_point[1-4]_temp is writable, the second set is
/linux-4.1.27/include/linux/
Dkvm_host.h543 unsigned long gfn_to_hva_prot(struct kvm *kvm, gfn_t gfn, bool *writable);
546 bool *writable);
553 bool write_fault, bool *writable);
556 bool *writable);
Dhugetlb.h410 struct page *page, int writable) in arch_make_huge_pte() argument
/linux-4.1.27/net/netfilter/ipvs/
Dip_vs_core.c959 unsigned int writable; in ip_vs_out_icmp_v6() local
1009 writable = ciph.len; in ip_vs_out_icmp_v6()
1011 pp, writable, sizeof(struct ipv6hdr), in ip_vs_out_icmp_v6()
1520 unsigned int offs_ciph, writable, verdict; in ip_vs_in_icmp_v6() local
1594 writable = ciph.len; in ip_vs_in_icmp_v6()
1597 writable += 2 * sizeof(__u16); /* Also mangle ports */ in ip_vs_in_icmp_v6()
1599 verdict = ip_vs_icmp_xmit_v6(skb, cp, pp, writable, hooknum, &ciph); in ip_vs_in_icmp_v6()
/linux-4.1.27/fs/jffs2/
DTODO6 do shared writable mmap, if we can have a fs hook for do_wp_page() to
/linux-4.1.27/Documentation/sound/alsa/
Dpowersave.txt24 The power_save option is exported as writable. This means you can
/linux-4.1.27/arch/arm/include/asm/
Dkvm_mmu.h60 phys_addr_t pa, unsigned long size, bool writable);
/linux-4.1.27/drivers/block/drbd/
DKconfig31 DRBD can also be used in dual-Primary mode (device writable on both
/linux-4.1.27/arch/arm64/include/asm/
Dkvm_mmu.h92 phys_addr_t pa, unsigned long size, bool writable);
/linux-4.1.27/Documentation/sysctl/
Dfs.txt165 time-of-check-time-of-use race, most commonly seen in world-writable
185 time-of-check-time-of-use race, most commonly seen in world-writable
195 a sticky world-writable directory, or when the uid of the symlink and
/linux-4.1.27/drivers/staging/iio/Documentation/
Ddevice.txt41 Raw value writing function. Used for writable device values such
/linux-4.1.27/fs/btrfs/
DKconfig15 writable snapshotting, support for multiple devices and many more
/linux-4.1.27/Documentation/device-mapper/
Dpersistent-data.txt44 The only way you can get hold of a writable block through the
Dsnapshot.txt7 the block device which are also writable without interfering with the
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt16 the selected entry is writable, the guest can rewrite it through the data
/linux-4.1.27/arch/powerpc/include/asm/
Dkvm_book3s.h158 bool *writable);
/linux-4.1.27/arch/s390/kvm/
Dpriv.c974 bool writable; in handle_tprot() local
1008 hva = gfn_to_hva_prot(vcpu->kvm, gpa_to_gfn(gpa), &writable); in handle_tprot()
1012 if (!writable) in handle_tprot()
Dkvm-s390.h206 long kvm_arch_fault_in_page(struct kvm_vcpu *vcpu, gpa_t gpa, int writable);
Dkvm-s390.c1787 long kvm_arch_fault_in_page(struct kvm_vcpu *vcpu, gpa_t gpa, int writable) in kvm_arch_fault_in_page() argument
1790 writable ? FAULT_FLAG_WRITE : 0); in kvm_arch_fault_in_page()
/linux-4.1.27/mm/
Dhuge_memory.c2130 bool referenced = false, writable = false; in __collapse_huge_page_isolate() local
2170 writable = true; in __collapse_huge_page_isolate()
2200 if (likely(referenced && writable)) in __collapse_huge_page_isolate()
2574 bool writable = false, referenced = false; in khugepaged_scan_pmd() local
2596 writable = true; in khugepaged_scan_pmd()
2625 if (referenced && writable) in khugepaged_scan_pmd()
Dhugetlb.c2604 int writable) in make_huge_pte() argument
2608 if (writable) { in make_huge_pte()
2617 entry = arch_make_huge_pte(entry, vma, page, writable); in make_huge_pte()
/linux-4.1.27/Documentation/security/
DYama.txt49 The sysctl settings (writable only with CAP_SYS_PTRACE) are:
/linux-4.1.27/Documentation/filesystems/
Dromfs.txt166 a writable file system, thus negating the size advantages. Possible
168 similarly small writable filesystem for RAM disks.
Doverlayfs.txt45 not need to be writable. The lower filesystem can even be another
46 overlayfs. The upper filesystem will normally be writable and if it
Dsysfs-pci.txt50 rw - file is readable and writable
Dnilfs2.txt19 concurrently with its writable mount, and this feature is convenient
Dvfat.txt33 writable, utime(2) is also allowed. I.e. ~dmask & 022)
Dvfs.txt283 unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
/linux-4.1.27/fs/nfsd/
Dnfs4proc.c95 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.1.27/Documentation/cdrom/
Dpacket-writing.txt68 DVD-RAM discs are random writable, so using the pktcdvd driver is not
/linux-4.1.27/net/unix/
Daf_unix.c2373 unsigned int mask, writable; in unix_dgram_poll() local
2405 writable = unix_writable(sk); in unix_dgram_poll()
2406 if (writable) { in unix_dgram_poll()
2413 writable = 0; in unix_dgram_poll()
2418 if (writable) in unix_dgram_poll()
/linux-4.1.27/drivers/power/
Dsmb347-charger.c616 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.1.27/Documentation/ioctl/
Dcdrom.txt66 CDROM_NEXT_WRITABLE get next writable block
932 CDROM_NEXT_WRITABLE get next writable block
942 The next writable block.
/linux-4.1.27/arch/arm/boot/dts/
Darmada-370-netgear-rn104.dts182 /* Last MB is for the BBT, i.e. not writable */
Darmada-370-netgear-rn102.dts169 /* Last MB is for the BBT, i.e. not writable */
Darmada-xp-linksys-mamba.dts262 * 38MB, last MB is for the BBT, not writable
Darmada-xp-netgear-rn2120.dts210 /* Last MB is for the BBT, i.e. not writable */
/linux-4.1.27/Documentation/
Drfkill.txt25 - soft block: writable radio block (need not be readable) that is set by
Dnommu-mmap.txt84 case, a shared-writable memory mapping will be possible. It will work
218 assumed to be readable and writable, not executable, and only shareable
Ddebugging-via-ohci1394.txt107 controller implements a writable Physical Upper Bound register. This is
Dcachetlb.txt283 user space shared/writable mappings of this page potentially
300 which have shared+writable mappings of this file, we must make
Dmd.txt505 This file is writable, and each of the strings that could be
604 number of entries in the stripe cache. This is writable, but
DDMA-API.txt519 dma_alloc_coherent() be directly writable.
/linux-4.1.27/Documentation/sound/oss/
Dmwave33 readable and writable before it can be edited. This can be done with
/linux-4.1.27/Documentation/gpio/
Dgpio.txt43 - Output values are writable (high=1, low=0). Some chips also have
Dgpio-legacy.txt30 - Output values are writable (high=1, low=0). Some chips also have
/linux-4.1.27/arch/tile/include/hv/
Dhypervisor.h2346 _HV_BIT(writable, WRITABLE) in _HV_BIT()
/linux-4.1.27/drivers/infiniband/hw/mlx5/
Dodp.c242 if (mr->umem->writable) in pagefault_single_data_segment()
/linux-4.1.27/Documentation/fb/
Dviafb.txt218 These two files are readable and writable. iga1 and iga2 are the two
/linux-4.1.27/Documentation/video4linux/
Duvcvideo.txt207 must point to a valid writable buffer big enough to hold the indicated
/linux-4.1.27/Documentation/arm/SA1100/
DAssabet128 convenient way to store a writable filesystem into flash. JFFS2 is used in
/linux-4.1.27/Documentation/arm64/
Dbooting.txt167 All writable architected system registers at the exception level where
/linux-4.1.27/Documentation/usb/
Dmass-storage.txt42 read, but (if the logical unit is writable) due to buffering on
Dproc_usb_info.txt75 Note that since by default these BBB/DDD files are writable only by
Dpower-management.txt654 This writable flag controls the state of an idle port.
/linux-4.1.27/Documentation/networking/
Dnetlink_mmap.txt43 mapping still needs to be writable in order to update the frame status after
Dcdc_mbim.txt32 The parameter is writable, and can be changed at any time. A manual
/linux-4.1.27/arch/x86/kvm/
Dmmu.c3001 gva_t gva, pfn_t *pfn, bool write, bool *writable);
3431 gva_t gva, pfn_t *pfn, bool write, bool *writable) in try_async_pf() argument
3435 *pfn = gfn_to_pfn_async(vcpu->kvm, gfn, &async, write, writable); in try_async_pf()
3450 *pfn = gfn_to_pfn_prot(vcpu->kvm, gfn, write, writable); in try_async_pf()
/linux-4.1.27/drivers/mtd/
DKconfig105 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
/linux-4.1.27/sound/soc/codecs/
Dmax98088.c263 int writable; member
Dmax98095.c207 int writable; member
/linux-4.1.27/drivers/md/
DKconfig274 Allow volume managers to take writable snapshots of a device.
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt231 writable control files located in procfs (for system wide settings).
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt518 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.1.27/Documentation/x86/
Dboot.txt20 writable.
/linux-4.1.27/Documentation/scsi/
Dscsi_mid_low_api.txt135 those that are writable after the driver is loaded) could also be
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1423 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.1.27/Documentation/trace/
Dftrace.txt883 markers - When set, the trace_marker is writable (only by root).