| /linux/fs/nfs/blocklayout/ |
| H A D | extent_tree.c | 27 ext_tree_prev(struct pnfs_block_extent *be) in ext_tree_prev() argument 29 struct rb_node *node = rb_prev(&be->be_node); in ext_tree_prev() 34 ext_tree_next(struct pnfs_block_extent *be) in ext_tree_next() argument 36 struct rb_node *node = rb_next(&be->be_node); in ext_tree_next() 41 ext_f_end(struct pnfs_block_extent *be) in ext_f_end() argument 43 return be->be_f_offset + be->be_length; in ext_f_end() 50 struct pnfs_block_extent *be = NULL; in __ext_tree_search() local 53 be = ext_node(node); in __ext_tree_search() 54 if (start < be->be_f_offset) in __ext_tree_search() 56 else if (start >= ext_f_end(be)) in __ext_tree_search() [all …]
|
| /linux/Documentation/arch/arm64/ |
| H A D | booting.rst | 20 hypervisor code, or it may just be a handful of instructions for 53 The device tree blob (dtb) must be placed on an 8-byte boundary and must 54 not exceed 2 megabytes in size. Since the dtb will be mapped cacheable 55 using blocks of up to 2 megabytes in size, it must not be placed within 56 any 2M region which must be mapped with any specific attributes. 58 NOTE: versions prior to v4.2 also require that the DTB be placed within 67 therefore requires decompression (gzip etc.) to be performed by the boot 106 little-endian and must be respected. Where image_size is zero, 107 text_offset can be assumed to be 0x80000. 113 Bit 0 Kernel endianness. 1 if BE, 0 if LE. [all …]
|
| H A D | gcs.rst | 9 intended to be exhaustive. 28 GCSPR_EL0. This is readable by userspace but can only be updated 43 at runtime this should be done with great care. 47 * GCS specific errors (those reported with EC 0x2d) will be reported as 56 in LR match those in the GCS, the LR will be ignored. This is not supported 66 should be used. 82 status of the specified GCS mode bits will be rejected. 84 * PR_LOCK_SHADOW_STACK_STATUS allows any bit to be locked, this allows 91 thread that called them, any other running threads will be unaffected. 97 * The current GCS configuration for a thread may be read with the [all …]
|
| H A D | acpi_object_usage.rst | 55 Must be supplied if RAS support is provided by the platform. It 56 is recommended this table be supplied. 62 Microsoft only table, will not be supported. 96 License has changed and should be usable. Optional if used instead 103 Microsoft only table, will not be supported. 119 x86 only table, will not be supported. 131 Optional, not currently supported, but could be used on ARM if and 134 need to be modified in the ACPI specification. 142 if it had actually occurred. However, this table should not be 143 shipped with a production system; it should be dynamically loaded [all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 20 be allowed to plug one or more RTCs to your system. You will 29 If you say yes here, the system time (wall clock) will be set using 38 The RTC device that will be used to (re)initialize the system 44 This clock should be battery-backed, so that it reads the correct 49 be useful to reinitialize system time when resuming from system 57 If you say yes here, the system time (wall clock) will be stored 114 Other RTCs will not be available through that API. 129 can be accessed as /dev/rtc, which is a name 151 RTC test driver. It's a software RTC which can be 158 This driver can also be built as a module. If so, the module [all …]
|
| /linux/tools/perf/util/ |
| H A D | genelf_debug.c | 47 buffer_ext_dump(struct buffer_ext *be, const char *msg) in buffer_ext_dump() argument 51 for (i = 0 ; i < be->cur_pos; i++) in buffer_ext_dump() 52 warnx("%4zu 0x%02x", i, (((char *)be->data)[i]) & 0xff); in buffer_ext_dump() 56 buffer_ext_add(struct buffer_ext *be, void *addr, size_t sz) in buffer_ext_add() argument 59 size_t be_sz = be->max_sz; in buffer_ext_add() 62 if ((be->cur_pos + sz) < be_sz) { in buffer_ext_add() 63 memcpy(be->data + be->cur_pos, addr, sz); in buffer_ext_add() 64 be->cur_pos += sz; in buffer_ext_add() 73 tmp = realloc(be->data, be_sz); in buffer_ext_add() 77 be->data = tmp; in buffer_ext_add() [all …]
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 6 user mappings, and similar to be cached in the kernel for the use of 13 The key service can be configured on by enabling: 46 * Each key is of a defined "type". Types must be registered inside the 48 can be added or used. Userspace programs cannot define new types directly. 51 number of operations that can be performed on a key of that type. 53 Should a type be removed from the system, all the keys of that type will 54 be invalidated. 56 * Each key has a description. This should be a printable string. The key 62 whether a kernel service will be able to find the key. 64 * Each key can be set to expire at a specific time by the key type's [all …]
|
| /linux/sound/soc/ |
| H A D | soc-pcm.c | 47 /* is the current PCM operation for this BE ? */ 49 struct snd_soc_pcm_runtime *be, int stream) in snd_soc_dpcm_can_be_update() argument 53 be->dpcm[stream].runtime_update)) in snd_soc_dpcm_can_be_update() 59 struct snd_soc_pcm_runtime *be, in snd_soc_dpcm_check_state() argument 69 for_each_dpcm_fe(be, stream, dpcm) { in snd_soc_dpcm_check_state() 83 /* it's safe to do this BE DAI */ in snd_soc_dpcm_check_state() 88 * We can only hw_free, stop, pause or suspend a BE DAI if any of it's FE 92 struct snd_soc_pcm_runtime *be, int stream) in snd_soc_dpcm_can_be_free_stop() argument 100 return snd_soc_dpcm_check_state(fe, be, stream, state, ARRAY_SIZE(state)); in snd_soc_dpcm_can_be_free_stop() 104 * We can only change hw params a BE DAI if any of it's FE are not prepared, [all …]
|
| /linux/fs/btrfs/ |
| H A D | ref-verify.c | 30 * be used to verify the extent tree is consistent as these should all match 48 * were called with since it could be different from ref_root. We also store 99 struct block_entry *be) in insert_block_entry() argument 103 node = rb_find_add(&be->node, root, block_entry_bytenr_cmp); in insert_block_entry() 217 static void free_block_entry(struct block_entry *be) in free_block_entry() argument 224 while ((n = rb_first(&be->roots))) { in free_block_entry() 226 rb_erase(&re->node, &be->roots); in free_block_entry() 230 while((n = rb_first(&be->refs))) { in free_block_entry() 232 rb_erase(&ref->node, &be->refs); in free_block_entry() 236 while (!list_empty(&be->actions)) { in free_block_entry() [all …]
|
| /linux/drivers/i2c/muxes/ |
| H A D | Kconfig | 14 If you say yes to this option, support will be included for an 19 This driver can also be built as a module. If so, the module 20 will be called i2c-arb-gpio-challenge. 26 If you say yes to this option, support will be included for a 31 This driver can also be built as a module. If so, the module 32 will be called i2c-mux-gpio. 39 If you say yes to this option, support will be included for a 44 This driver can also be built as a module. If so, the module 45 will be called i2c-mux-gpmux. 55 This driver can also be built as a module. If so, the module [all …]
|
| /linux/net/sched/ |
| H A D | Kconfig | 17 is a FIFO (first come, first served). If you say Y here, you will be 19 then be attached to different network devices. This is useful for 23 This code is considered to be experimental. 37 If you say Y here and to "/proc file system" below, you will be able 60 module will be called sch_htb. 69 module will be called sch_hfsc. 78 module will be called sch_prio. 87 module will be called sch_multiq. 98 module will be called sch_red. 109 module will be called sch_sfb. [all …]
|
| /linux/Documentation/process/ |
| H A D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design 8 code. It is the code which will be examined by other developers and merged 34 the standard; many developers will request that the code be reformatted 42 win before the code can be merged. Putting code into the kernel means 53 on it for other reasons, but coding style changes should not be made for 56 The coding style document also should not be read as an absolute law which 57 can never be transgressed. If there is a good reason to go against the 69 Some basic editor settings, such as indentation and line endings, will be 81 But experience has shown that excessive or premature abstraction can be 82 just as harmful as premature optimization. Abstraction should be used to [all …]
|
| /linux/drivers/net/xen-netback/ |
| H A D | xenbus.c | 13 static int connect_data_rings(struct backend_info *be, 15 static void connect(struct backend_info *be); 16 static int read_xenbus_vif_flags(struct backend_info *be); 17 static int backend_create_xenvif(struct backend_info *be); 18 static void unregister_hotplug_status_watch(struct backend_info *be); 20 static void set_backend_state(struct backend_info *be, 206 struct backend_info *be = dev_get_drvdata(&xdev->dev); in netback_uevent() local 208 if (!be) in netback_uevent() 211 if (add_uevent_var(env, "script=%s", be->hotplug_script)) in netback_uevent() 214 if (!be->vif) in netback_uevent() [all …]
|
| /linux/Documentation/driver-api/ |
| H A D | vme.rst | 12 be provided to the registration function. Along with the maximum number of 16 :c:type:`struct vme_driver <vme_driver>` should be correctly set. The '.name' 19 The '.match' function allows control over which VME devices should be registered 20 with the driver. The match function should return 1 if a device should be 40 driver. The bridge number (or bus number) can be accessed using 44 :c:func:`vme_unregister_driver` and should usually be called from the device 52 be called the number of times specified during the registration. If a match 53 succeeds, a non-zero value should be returned. A zero return value indicates 56 device structure. This pointer should be saved, it will be required for 62 driver to request a specific window or DMA channel (which may be used by a [all …]
|
| /linux/drivers/media/usb/gspca/ |
| H A D | Kconfig | 17 module will be called gspca_main. 28 module will be called gspca_benq. 37 module will be called gspca_conex. 48 module will be called gspca_cpia1. 58 module will be called gspca_dtcs033. 67 module will be called gspca_etoms. 76 module will be called gspca_finepix. 85 module will be called gspca_jeilinj. 95 module will be called gspca_jl2005bcd. 104 module will be called gspca_kinect. [all …]
|
| /linux/sound/soc/meson/ |
| H A D | axg-card.c | 30 * Those will be over-written by the CPU side of the link 45 struct axg_dai_link_tdm_data *be = in axg_card_tdm_be_hw_params() local 48 return meson_card_i2s_set_sysclk(substream, params, be->mclk_fs); in axg_card_tdm_be_hw_params() 58 struct axg_dai_link_tdm_data *be = in axg_card_tdm_dai_init() local 65 be->codec_masks[i].tx, in axg_card_tdm_dai_init() 66 be->codec_masks[i].rx, in axg_card_tdm_dai_init() 67 be->slots, be->slot_width); in axg_card_tdm_dai_init() 75 ret = axg_tdm_set_tdm_slots(snd_soc_rtd_to_cpu(rtd, 0), be->tx_mask, be->rx_mask, in axg_card_tdm_dai_init() 76 be->slots, be->slot_width); in axg_card_tdm_dai_init() 88 struct axg_dai_link_tdm_data *be = in axg_card_tdm_dai_lb_init() local [all …]
|
| /linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 15 memory should be allocated. The GFP acronym stands for "get free 27 flags must be used. 33 zones can be used, how hard the allocator should try to find free 34 memory, whether the memory can be accessed by the userspace etc. The 43 direct reclaim may be triggered under memory pressure; the calling 44 context must be allowed to sleep. 52 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``. 53 * Untrusted allocations triggered from userspace should be a subject 56 allocations that should be accounted. 62 will be directly accessible by the kernel and implies that the [all …]
|
| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 15 say Yes and it will be accessible from within Linux. For 18 userspace enablement piece of the specification, can be 21 will be called tpm. If unsure, say N. 25 2) Without ACPI enabled, the BIOS event log won't be accessible, 69 specification (TPM2.0) say Yes and it will be accessible from 71 the module will be called tpm_tis. 81 specification (TPM2.0) say Yes and it will be accessible from 83 the module will be called tpm_tis_spi. 90 say Yes and it will be accessible from within Linux. 100 say Yes and it will be accessible from within Linux. [all …]
|
| /linux/Documentation/crypto/ |
| H A D | asymmetric-keys.rst | 21 The "asymmetric" key type is designed to be a container for the keys used in 27 However, no requirement is made that the key data actually be stored in the 30 A completely in-kernel key retention and operation subtype can be defined, but 31 it would also be possible to provide access to cryptographic hardware (such as 32 a TPM) that might be used to both retain the relevant key and perform 34 merely be an interface to the TPM driver. 39 subtype of the key and define the operations that can be done on that key. 51 should be given from the content of the key. 53 This can then be used to refer to the key, either by complete match or by 72 only keys of the specified subtype (e.g. tpm) will be matched. For [all …]
|
| /linux/include/linux/ |
| H A D | zlib.h | 6 warranty. In no event will the authors be held liable for any damages 13 1. The origin of this software must not be misrepresented; you must not 15 in a product, an acknowledgment in the product documentation would be 17 2. Altered source versions must be plainly marked as such, and must not be 19 3. This notice may not be removed or altered from any source distribution. 45 is a STORED block. It also resets the mode to be read for the next 56 (deflation) but other algorithms will be added later and will have the same 59 Compression can be done in a single step if the buffers are large 60 enough (for example if an input file is mmap'ed), or can be done by 72 The zlib format was designed to be compact and fast for use in memory [all …]
|
| /linux/drivers/iio/dac/ |
| H A D | Kconfig | 18 module will be called ad3530r. 33 module will be called ad3552r-hs. 49 module will be called ad3552r. 63 module will be called ad5064. 73 To compile this driver as module choose M here: the module will be called 86 To compile this driver as module choose M here: the module will be called 96 To compile this driver as module choose M here: the module will be called 110 module will be called ad5446. 120 module will be called ad5449. 135 module will be called ad5592r. [all …]
|
| /linux/drivers/usb/serial/ |
| H A D | Kconfig | 19 module will be called usbserial. 27 If you say Y here, it will be possible to use a USB to serial 30 allows logins in single user mode). This could be useful if some 34 (/dev/tty0) will still be used as the system console by default, but 52 support" be compiled as a module for this driver to be used 77 will be called usb-serial-simple. 85 will be called aircable. 94 module will be called ark3116 104 module will be called belkin_sa. 113 module will be called ch341. [all …]
|
| /linux/drivers/block/xen-blkback/ |
| H A D | xenbus.c | 38 struct xenbus_device *xen_blkbk_xenbus(struct backend_info *be) in xen_blkbk_xenbus() argument 40 return be->dev; in xen_blkbk_xenbus() 58 struct xenbus_device *dev = blkif->be->dev; in blkback_name() 88 if (blkif->be->dev->state == XenbusStateConnected) in xen_update_blkif_status() 92 connect(blkif->be); in xen_update_blkif_status() 93 if (blkif->be->dev->state != XenbusStateConnected) in xen_update_blkif_status() 98 xenbus_dev_error(blkif->be->dev, err, "get blkback dev name"); in xen_update_blkif_status() 104 xenbus_dev_error(blkif->be->dev, err, "block flush"); in xen_update_blkif_status() 115 xenbus_dev_fatal(blkif->be->dev, err, in xen_update_blkif_status() 180 * Because freeing back to the cache may be deferred, it is not in xen_blkif_alloc() [all …]
|
| /linux/Documentation/filesystems/caching/ |
| H A D | netfs-api.rst | 32 (4) Declaring a cookie to be in use 52 or server address, volume ID or share name). This must be rendered as a 53 printable string that can be used as a directory name (ie. no '/' characters 61 object key. Object keys are binary blobs and only need to be unique within 84 structures being used. The actual operation can then be issued and conflicting 85 invalidations can be detected upon completion. 106 The volume key must be a printable string with no '/' characters in it. It 107 should begin with the name of the filesystem and should be no longer than 254 108 characters. It should uniquely represent the volume and will be matched with 116 The specified coherency data is stored in the cookie and will be matched [all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | seccomp_filter.rst | 34 mechanism for minimizing the exposed kernel surface. It is meant to be 36 behavior and information flow should be managed with a combination of 40 system calls in socketcall() is allowed, for instance) which could be 48 ``CONFIG_HAVE_ARCH_SECCOMP_FILTER``, then filters may be added as below: 53 The BPF program will be executed over struct seccomp_data 56 acceptable values to inform the kernel which action should be 68 processes will be constrained to the same filters and system 73 true, ``-EACCES`` will be returned. This requirement ensures that filter 74 programs cannot be applied to child processes with greater privileges 78 additional filters may be layered on which will increase evaluation [all …]
|