| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse-passthrough.rst | 10 FUSE (Filesystem in Userspace) passthrough is a feature designed to improve the 25 Currently, passthrough is supported for operations like ``read(2)``/``write(2)`` 31 To use FUSE passthrough: 47 when it's no longer needed for passthrough setups. 52 Setting up passthrough functionality currently requires the FUSE daemon to 61 The core mechanism for passthrough involves the FUSE daemon opening a file 71 an open FUSE file in passthrough mode). 102 filesystem stacking scenarios if unprivileged users could set up passthrough. 103 A FUSE passthrough filesystem might use a backing file that resides: 114 To mitigate this, FUSE passthrough already incorporates checks based on
|
| H A D | index.rst | 14 fuse-passthrough
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-g-mode.rst | 61 by the follower. The follower can enable the passthrough mode. In that 65 the passthrough mode. See :ref:`cec-core-processing` for details. 149 CEC device into passthrough mode, allowing the exclusive follower 214 except when in passthrough mode. In passthrough mode the core 222 except when in passthrough mode. In passthrough mode the core 230 passthrough mode. In passthrough mode the core does nothing 236 in passthrough mode. In passthrough mode the core does nothing 243 except when in passthrough mode. In passthrough mode the core 252 except when in passthrough mode. In passthrough mode the core
|
| H A D | cec-ioc-adap-g-caps.rst | 106 - Userspace can use the passthrough mode by calling
|
| /linux/fs/fuse/ |
| H A D | passthrough.c | 179 ff->passthrough = backing_file; in fuse_passthrough_open() 183 backing_id, fb, ff->passthrough, err); in fuse_passthrough_open() 191 fb, ff->passthrough); in fuse_passthrough_release() 193 fput(ff->passthrough); in fuse_passthrough_release() 194 ff->passthrough = NULL; in fuse_passthrough_release()
|
| H A D | backing.c | 93 if (!fc->passthrough || !capable(CAP_SYS_ADMIN)) in fuse_backing_open() 149 if (!fc->passthrough || !capable(CAP_SYS_ADMIN)) in fuse_backing_close()
|
| H A D | Kconfig | 58 bool "FUSE passthrough operations support" 66 If you want to allow passthrough operations, answer Y.
|
| H A D | Makefile | 17 fuse-$(CONFIG_FUSE_PASSTHROUGH) += passthrough.o backing.o
|
| H A D | fuse_i.h | 303 struct file *passthrough; member 913 unsigned int passthrough:1; member 1603 return ff->passthrough; in fuse_file_passthrough()
|
| H A D | iomode.c | 176 if (!IS_ENABLED(CONFIG_FUSE_PASSTHROUGH) || !fc->passthrough || in fuse_file_passthrough_open()
|
| /linux/Documentation/networking/ |
| H A D | net_failover.rst | 64 the VF passthrough device for normal communication. The virtio-net device will 67 The second device definition is for the VF passthrough interface. Here the 88 virtio-net interface, and ens11 is the slave 'primary' VF passthrough interface. 122 device to the VM. This is not the VF that was passthrough'd to the VM (seen in 151 # Remove the VF that was passthrough'd to the VM.
|
| /linux/drivers/vfio/pci/ |
| H A D | Kconfig | 48 bool "VFIO PCI extensions for s390x KVM passthrough" 53 to KVM passthrough capabilities, such as interpretive execution of
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache.rst | 82 passthrough. 92 If passthrough is selected, useful when the cache contents are not known 96 block invalidates. To enable passthrough mode the cache must be clean. 113 importance if writeback mode is used. Writethrough and passthrough 192 feature args writethrough or passthrough (The default is writeback.) 212 passthrough a degraded mode useful for various cache coherency 217 To enable passthrough mode the cache must be clean. 315 invalidation of larger caches. The cache must be in passthrough mode
|
| H A D | era.rst | 86 - Cache enters passthrough mode (see: dm-cache's docs in cache.txt)
|
| H A D | dm-ima.rst | 349 <passthrough> "," <no_discard_passdown> ";" 359 passthrough := "passthrough=" <yes_no> 372 passthrough=n,metadata2=y,no_discard_passdown=n;
|
| /linux/drivers/xen/xen-pciback/ |
| H A D | Makefile | 15 passthrough.o
|
| H A D | xenbus.c | 22 static bool __read_mostly passthrough; variable 23 module_param(passthrough, bool, S_IRUGO); 24 MODULE_PARM_DESC(passthrough, 748 if (passthrough) in xen_pcibk_xenbus_register()
|
| /linux/drivers/media/cec/core/ |
| H A D | cec-api.c | 487 adap->passthrough = in cec_s_mode() 491 adap->passthrough = false; in cec_s_mode() 640 adap->passthrough = false; in cec_release()
|
| H A D | cec-adap.c | 2066 if (!adap->passthrough && from_unregistered) in cec_receive_notify() 2076 if (adap->passthrough) in cec_receive_notify() 2311 adap->passthrough ? " (in passthrough mode)" : ""); in cec_adap_status()
|
| /linux/drivers/target/ |
| H A D | Kconfig | 36 passthrough access to Linux/SCSI device
|
| /linux/drivers/xen/ |
| H A D | Kconfig | 220 The parameter "passthrough" allows you specify how you want the PCI 222 PCI topology starts at 00.00.0, or (1) for passthrough if you want 263 tristate "Xen hypercall passthrough driver" 267 The hypercall passthrough driver allows privileged user programs to
|
| /linux/arch/um/drivers/ |
| H A D | Kconfig | 185 bool "Enable VFIO-based PCI passthrough" 188 This driver provides support for VFIO-based PCI passthrough.
|
| /linux/Documentation/arch/s390/ |
| H A D | vfio-ap.rst | 244 | | 9 create vfio_ap-passthrough | | 270 9. The administrator creates a passthrough type vfio_ap mediated device to be 325 passthrough devices: 327 /sys/devices/vfio_ap/matrix/mdev_supported_types/vfio_ap-passthrough 344 the number of vfio_ap mediated passthrough devices 780 ------ [vfio_ap-passthrough] (passthrough vfio_ap mediated device type) 802 ------ [vfio_ap-passthrough] 951 ------ [vfio_ap-passthrough]
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | todo.rst | 60 (passthrough ioctl/fsctl is now implemented in cifs.ko to allow
|
| /linux/Documentation/sound/hd-audio/ |
| H A D | realtek-pc-beep.rst | 6 Realtek HDA codecs and controls a muxer and pair of passthrough mixers that can
|