content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
.. \_serial\_console: Linux Serial Console ==================== To use a serial port as console you need to compile the support into your kernel - by default it is not compiled in. For PC style serial ports it's the config option next to menu option: :menuselection:`Character devices --> Serial drivers --> 8250/16550 a... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/serial-console.rst | master | linux | [
0.07914970070123672,
-0.028789134696125984,
-0.06962940096855164,
-0.11727333813905716,
-0.03136470168828964,
0.00826823990792036,
-0.08263025432825089,
0.07569395005702972,
-0.03272321820259094,
-0.04116459935903549,
0.04273965209722519,
-0.030302278697490692,
-0.052807435393333435,
0.000... | -0.003293 |
character device 5,1. (You can also use a network device as a console. See ``Documentation/networking/netconsole.rst`` for information on that.) Here's an example that will use ``/dev/ttyS1`` (COM2) as the console. Replace the sample values as needed. 1. Create ``/dev/console`` (real console) and ``/dev/tty0`` (master ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/serial-console.rst | master | linux | [
0.03870130330324173,
-0.056598518043756485,
-0.051951970905065536,
-0.08237999677658081,
-0.05950767919421196,
0.04124655947089195,
-0.05740850046277046,
0.11175784468650818,
-0.06331232190132141,
0.04498240351676941,
0.07300242781639099,
-0.02941228076815605,
-0.02625972591340542,
-0.0172... | 0.133161 |
Linux Braille Console ===================== To get early boot messages on a braille device (before userspace screen readers can start), you first need to compile the support for the usual serial console (see :ref:`Documentation/admin-guide/serial-console.rst `), and for braille device (in :menuselection:`Device Drivers... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/braille-console.rst | master | linux | [
0.04886878654360771,
-0.03490409627556801,
-0.07510124891996384,
-0.03824912756681442,
0.008540991693735123,
0.07088863849639893,
0.014547162689268589,
0.13061805069446564,
-0.025303972885012627,
-0.029367296025156975,
0.05310286581516266,
0.0008419935475103557,
0.015899527817964554,
0.066... | 0.069216 |
================================= Linux Plug and Play Documentation ================================= :Author: Adam Belay :Last updated: Oct. 16, 2002 Overview -------- Plug and Play provides a means of detecting and setting resources for legacy or otherwise unconfigurable devices. The Linux Plug and Play Layer provide... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/pnp.rst | master | linux | [
0.006548951845616102,
-0.07084624469280243,
-0.0464179590344429,
-0.12296595424413681,
0.058650076389312744,
0.04710856452584267,
0.029568888247013092,
0.032976869493722916,
-0.08419165760278702,
0.05553774535655975,
0.0509573332965374,
0.032644372433423996,
-0.05944643169641495,
0.0396512... | 0.163326 |
bus - ACPI: among its many uses, ACPI provides information about system level devices. It is meant to replace the PNPBIOS. It is not currently supported by Linux Plug and Play but it is planned to be in the near future. Requirements for a Linux PnP protocol: 1. the protocol must use EISA IDs 2. the protocol must inform... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/pnp.rst | master | linux | [
-0.0380253903567791,
0.03242699056863785,
-0.05138039216399193,
-0.006843808572739363,
0.048528313636779785,
0.028265105560421944,
0.12798026204109192,
0.07692555338144302,
-0.005097915884107351,
0.058652520179748535,
0.08784244954586029,
-0.010849889367818832,
0.02699529193341732,
0.02017... | 0.223732 |
.. SPDX-License-Identifier: GPL-2.0 .. \_bootconfig: ================== Boot Configuration ================== :Author: Masami Hiramatsu Overview ======== The boot configuration expands the current kernel command line to support additional key-value data when booting the kernel in an efficient way. This allows administr... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bootconfig.rst | master | linux | [
-0.04644108936190605,
0.010533345863223076,
-0.054208219051361084,
-0.006212074309587479,
-0.017926163971424103,
-0.03914625570178032,
0.10551489889621735,
0.03275463357567787,
-0.07188837230205536,
-0.04648565128445625,
0.0030474760569632053,
0.04722917079925537,
0.05837029963731766,
-0.0... | 0.06214 |
syntax accepts shell-script style comments. The comments starting with hash ("#") until newline ("\n") will be ignored. :: # comment line foo = value # value is set to foo. bar = 1, # 1st element 2, # 2nd element 3 # 3rd element This is parsed as below:: foo = value bar = 1, 2, 3 Note that you can not put a comment bet... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bootconfig.rst | master | linux | [
-0.09125632047653198,
-0.004926907364279032,
-0.017285240814089775,
-0.014234879985451698,
0.02695171721279621,
0.028617840260267258,
0.10289463400840759,
0.07883938401937485,
-0.014275806024670601,
-0.009097208268940449,
0.030069610103964806,
0.029820900410413742,
0.10534073412418365,
-0.... | 0.03965 |
bootconfig which attached to the initrd. Kernel parameters via Boot Config ================================= In addition to the kernel command line, the boot config can be used for passing the kernel parameters. All the key-value pairs under ``kernel`` key will be passed to kernel cmdline directly. Moreover, the key-va... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bootconfig.rst | master | linux | [
-0.07800900936126709,
0.026154955849051476,
-0.07531347125768661,
0.030494244769215584,
0.0009331816690973938,
0.02584567479789257,
0.0362449586391449,
0.13222557306289673,
-0.07682368159294128,
-0.03474902734160423,
0.05136127769947052,
-0.008030839264392853,
0.05251048505306244,
-0.07057... | 0.073308 |
Parport +++++++ The ``parport`` code provides parallel-port support under Linux. This includes the ability to share one port between multiple device drivers. You can pass parameters to the ``parport`` code to override its automatic detection of your hardware. This is particularly useful if you want to use IRQs, since i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/parport.rst | master | linux | [
-0.019071877002716064,
-0.0847516879439354,
-0.0559145025908947,
-0.03527522832155228,
-0.030829856172204018,
-0.03223370760679245,
-0.0024267721455544233,
0.02773595042526722,
-0.04378627985715866,
-0.021806735545396805,
0.08663316816091537,
-0.02960299141705036,
-0.008428139612078667,
-0... | 0.134998 |
`-- timeslice | |-- base-addr | |-- irq | |-- dma | |-- modes | `-- spintime `-- parport1 |-- autoprobe |-- autoprobe0 |-- autoprobe1 |-- autoprobe2 |-- autoprobe3 |-- devices | |-- active | `-- ppa | `-- timeslice |-- base-addr |-- irq |-- dma |-- modes `-- spintime .. tabularcolumns:: |p{4.0cm}|p{13.5cm}| ===========... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/parport.rst | master | linux | [
-0.056264109909534454,
0.011852437630295753,
-0.138341024518013,
-0.10093227028846741,
-0.07573319971561432,
0.028824614360928535,
0.043896570801734924,
0.08373291790485382,
-0.07496669888496399,
0.03061952069401741,
0.0959116667509079,
-0.027060173451900482,
-0.021633049473166466,
-0.0456... | 0.000578 |
``lp=auto`` on the kernel command line, and lp will create devices only for those ports that seem to have printers attached. \* If you give PLIP the ``timid`` parameter, either with ``plip=timid`` on the command line, or with ``insmod plip timid=1`` when using modules, it will avoid any ports that seem to be in use by ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/parport.rst | master | linux | [
-0.04231712967157364,
-0.04772718623280525,
-0.06267904490232468,
-0.009527476504445076,
-0.08764254301786423,
-0.040289562195539474,
0.00869553443044424,
0.08886153995990753,
-0.08889969438314438,
0.021908361464738846,
0.11797238141298294,
-0.019415434449911118,
-0.008592024445533752,
0.0... | 0.063729 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) ====================================================== Discovering Linux kernel subsystems used by a workload ====================================================== :Authors: - Shuah Khan - Shefali Sharma :maintained-by: Shuah Khan Key Points ========== \* Understandi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.059926655143499374,
0.03242938593029976,
-0.11884670704603195,
-0.0006936901481822133,
0.052592258900403976,
-0.10794684290885925,
0.10034719109535217,
0.06789566576480865,
-0.027935883030295372,
-0.06741335242986679,
-0.042888861149549484,
0.007436503656208515,
0.02732713520526886,
-0.... | 0.250683 |
tools that aren’t usually included to build Linux kernel. Please note that the following works on Debian based distributions. You might have to find equivalent packages on other Linux distributions. Install tools to build Linux kernel and tools in kernel repository. scripts/ver\_linux is a good way to check if your sys... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.04724929481744766,
-0.06348197907209396,
-0.07195909321308136,
0.012298964895308018,
0.08593373000621796,
-0.09773830324411392,
-0.020822105929255486,
0.07513193786144257,
-0.05664049834012985,
-0.040731851011514664,
0.027018658816814423,
-0.11883465945720673,
-0.06886602193117142,
-0.0... | 0.105886 |
when run in verbose mode gives more detailed information about the system calls invoked by a process. Running strace -c generates a report of the percentage of time spent in each system call, the total time in seconds, the microseconds per call, the total number of calls, the count of each system call that has failed w... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.035188715904951096,
0.0222571212798357,
-0.14887635409832,
0.06284970790147781,
-0.005524173844605684,
-0.1063910499215126,
0.05623670294880867,
0.1145481988787651,
0.013832639902830124,
-0.019626501947641373,
-0.07935921847820282,
-0.03548751771450043,
-0.009150352329015732,
-0.0612389... | 0.178122 |
following benchmarks: \* sched/messaging \* sched/pipe \* syscall/basic \* mem/memcpy \* mem/memset What is stress-ng and how do we use it? ======================================= As mentioned earlier, stress-ng is used for performing stress testing on the kernel. It allows you to exercise various physical subsystems o... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.0921732485294342,
0.008305368013679981,
-0.028822513297200203,
0.05838337913155556,
0.03622617945075035,
-0.1120951697230339,
0.0727471113204956,
0.06880535930395126,
-0.03483707085251808,
0.05391886085271835,
-0.06107902154326439,
-0.03225310891866684,
-0.04235001653432846,
-0.04347299... | 0.28963 |
| 1 | Process Mgmt. | sys\_getgid() | +-------------------+-----------+-----------------+-------------------------+ | geteuid | 1 | Process Mgmt. | sys\_geteuid() | +-------------------+-----------+-----------------+-------------------------+ | getegid | 1 | Process Mgmt. | sys\_getegid | +-------------------+---------... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.0461246483027935,
0.02939889021217823,
-0.13809101283550262,
-0.031724076718091965,
-0.05661652237176895,
-0.0677095353603363,
0.09230228513479233,
0.05518753454089165,
0.041365236043930054,
0.013362190686166286,
0.05679697170853615,
-0.026902880519628525,
0.005568863358348608,
-0.10756... | 0.165154 |
1 | Filesystem | sys\_lseek() | +-------------------+-----------+-----------------+-------------------------+ | access | 2 | Filesystem | sys\_access() | +-------------------+-----------+-----------------+-------------------------+ | getcwd | 1 | Filesystem | sys\_getcwd() | +-------------------+-----------+-----------... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.06802535802125931,
0.020144525915384293,
-0.13508138060569763,
0.00009040031727636233,
0.012869037687778473,
-0.03342559188604355,
0.045832548290491104,
0.09683873504400253,
-0.008751402609050274,
0.006092282012104988,
0.11915216594934464,
-0.008558472618460655,
0.05155879631638527,
-0.... | 0.050104 |
mmap | 7 | Memory Mgmt. | sys\_mmap() | +-------------------+-----------+-----------------+----------------------+ | mprotect | 3 | Memory Mgmt. | sys\_mprotect() | +-------------------+-----------+-----------------+----------------------+ | munmap | 1 | Memory Mgmt. | sys\_munmap() | +-------------------+-----------+-... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/workload-tracing.rst | master | linux | [
-0.0046676634810864925,
-0.013277304358780384,
-0.10537862777709961,
-0.05945587903261185,
-0.03320062905550003,
-0.08831287175416946,
0.06988987326622009,
0.06445464491844177,
-0.019883563742041588,
0.016280755400657654,
0.1060030609369278,
-0.014126744121313095,
0.03327199071645737,
-0.0... | 0.190605 |
========================================= Dell Remote BIOS Update driver (dell\_rbu) ========================================= Purpose ======= Document demonstrating the use of the Dell Remote BIOS Update driver for updating BIOS images on Dell servers and desktops. Scope ===== This document discusses the functionality... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dell_rbu.rst | master | linux | [
-0.01398871187120676,
0.0031402879394590855,
-0.12068060785531998,
0.012151815928518772,
0.007798866834491491,
0.007112696301192045,
-0.001281849923543632,
0.03357267379760742,
-0.025555217638611794,
-0.027353577315807343,
0.05673793703317642,
0.07171457260847092,
0.06360945850610733,
0.01... | 0.171714 |
in a single operation. In monolithic update the user simply get the BIOS image (.hdr file) and copies to the data file as is without any change to the BIOS image itself. Do the steps below to download the BIOS image. 1) echo 1 > /sys/class/firmware/dell\_rbu/loading 2) cp bios\_image.hdr /sys/class/firmware/dell\_rbu/d... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dell_rbu.rst | master | linux | [
-0.035378240048885345,
0.05105343461036682,
-0.03055001050233841,
-0.048090167343616486,
-0.019698161631822586,
-0.06736952811479568,
0.016795065253973007,
0.064185731112957,
-0.0551302470266819,
0.010546856559813023,
0.07807004451751709,
0.024933042004704475,
0.02324390783905983,
-0.02519... | 0.188312 |
================================= Hardware random number generators ================================= Introduction ============ The hw\_random framework is software that makes use of a special hardware feature on your CPU or motherboard, a Random Number Generator (RNG). The software has two parts: a core providing the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/hw_random.rst | master | linux | [
-0.021066876128315926,
-0.03267772123217583,
-0.05031820759177208,
0.003789805807173252,
-0.011832093819975853,
-0.051000453531742096,
0.09854383766651154,
-0.0069188582710921764,
0.005099709611386061,
-0.06137888878583908,
-0.007629009895026684,
0.00968338642269373,
-0.032462265342473984,
... | 0.150983 |
.. \_cgroup-v2: ================ Control Group v2 ================ :Date: October, 2015 :Author: Tejun Heo This is the authoritative documentation on the design, interface and conventions of cgroup v2. It describes all userland-visible aspects of cgroup including core and specific controller behaviors. All future chang... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.06772909313440323,
-0.05092185363173485,
-0.09619724750518799,
0.07586153596639633,
-0.0015823403373360634,
0.041257958859205246,
0.011059961281716824,
0.02486879751086235,
0.009995521046221256,
-0.0033589734230190516,
0.049922045320272446,
-0.054979875683784485,
-0.010803709737956524,
... | 0.178494 |
affects all processes which belong to the cgroups consisting the inclusive sub-hierarchy of the cgroup. When a controller is enabled on a nested cgroup, it always restricts the resource distribution further. The restrictions set closer to the root in the hierarchy can not be overridden from further away. Basic Operatio... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.08663187175989151,
-0.06328190118074417,
-0.045936860144138336,
0.04287523776292801,
0.0661180391907692,
-0.0384536013007164,
-0.10234565287828445,
0.057982973754405975,
0.06561876833438873,
-0.05230022966861725,
0.07051070034503937,
0.006085284519940615,
-0.02732899971306324,
-0.036034... | 0.022948 |
protection values at higher tree levels). memory\_hugetlb\_accounting Count HugeTLB memory usage towards the cgroup's overall memory usage for the memory controller (for the purpose of statistics reporting and memory protetion). This is a new behavior that could regress existing setups, so it must be explicitly opted i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.04473606124520302,
0.030677806586027145,
-0.05469899624586105,
0.024818625301122665,
0.008705389685928822,
0.001471786294132471,
0.015973269939422607,
0.08425480127334595,
0.041611701250076294,
0.020732911303639412,
0.049421656876802444,
-0.03278857469558716,
0.04940258711576462,
-0.037... | 0.066793 |
entry for cgroup v2 is always in the format "0::$PATH":: # cat /proc/842/cgroup ... 0::/test-cgroup/test-cgroup-nested If the process becomes a zombie and the cgroup it was associated with is removed subsequently, " (deleted)" is appended to the path:: # cat /proc/842/cgroup ... 0::/test-cgroup/test-cgroup-nested (dele... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.059626899659633636,
-0.08058489859104156,
-0.10550832748413086,
0.04301414638757706,
0.04377283155918121,
-0.022574407979846,
0.011913588270545006,
-0.035551100969314575,
0.10521280765533447,
-0.008460364304482937,
0.09339557588100433,
-0.009384660981595516,
-0.029436230659484863,
-0.02... | 0.11226 |
are enabled in the "cgroup.subtree\_control" file while there are processes in the cgroup. A threaded domain reverts to a normal domain when the conditions clear. When read, "cgroup.threads" contains the list of the thread IDs of all threads in the cgroup. Except that the operations are per-thread instead of per-proces... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.07905232161283493,
-0.11470822244882584,
-0.11640775948762894,
-0.0245999563485384,
0.005233035422861576,
-0.033225107938051224,
-0.009259150363504887,
-0.002865730319172144,
0.10908281058073044,
0.04444006457924843,
0.023688139393925667,
-0.013545442372560501,
-0.011776183731853962,
-0... | 0.102417 |
listed in "cgroup.controllers" can be enabled. When multiple operations are specified as above, either they all succeed or fail. If multiple operations on the same controller are specified, the last one is effective. Enabling a controller in a cgroup indicates that the distribution of the target resource across its imm... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.0527396984398365,
-0.03889801353216171,
-0.11675842106342316,
0.0353173203766346,
-0.03918066620826721,
0.062103528529405594,
-0.015504140406847,
-0.022846518084406853,
-0.00631870049983263,
-0.011407929472625256,
0.07501300424337387,
0.020551886409521103,
0.02238483913242817,
-0.052348... | 0.08358 |
a given directory control the distribution of the parent's resources, the delegatee shouldn't be allowed to write to them. For the first method, this is achieved by not granting access to these files. For the second, files outside the namespace should be hidden from the delegatee by the means of at least mount namespac... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.08264301717281342,
-0.052330728620290756,
-0.055938974022865295,
0.06733793765306473,
0.0085908817127347,
-0.03139366954565048,
0.013971920125186443,
0.02818470075726509,
0.05898332968354225,
0.017366820946335793,
0.03285810723900795,
-0.027426252141594887,
0.0252245981246233,
0.0020398... | 0.028716 |
once on start-up. Dynamic adjustments to resource distribution can be made by changing controller configuration through the interface files. Avoid Name Collisions ~~~~~~~~~~~~~~~~~~~~~ Interface files for a cgroup and its children cgroups occupy the same directory and it is possible to create children cgroups which col... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.10061188787221909,
-0.0416787751019001,
-0.041283246129751205,
0.047666557133197784,
-0.0842842385172844,
0.02627723291516304,
0.0350944884121418,
0.05498150363564491,
0.03548811748623848,
-0.003505661152303219,
0.04604971781373024,
-0.03142872825264931,
0.08019667863845825,
0.016526753... | 0.126183 |
the parent. Allocations are in the range [0, max] and defaults to 0, which is no resource. As allocations can't be over-committed, some configuration combinations are invalid and should be rejected. Also, if the resource is mandatory for execution of processes, process migrations may be rejected. "cpu.rt.max" hard-allo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.03969050571322441,
-0.04881885647773743,
-0.10720144212245941,
-0.023329615592956543,
-0.039103105664253235,
-0.09756561368703842,
-0.007407156750559807,
0.0730639323592186,
-0.0396246574819088,
0.05113941803574562,
0.020036939531564713,
0.03334486484527588,
0.009489856660366058,
-0.025... | 0.116142 |
happens, file modified event should be generated on the file. Core Interface Files -------------------- All cgroup core files are prefixed with "cgroup." cgroup.type A read-write single value file which exists on non-root cgroups. When read, it indicates the current type of the cgroup, which can be one of the following... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.09738786518573761,
-0.07845472544431686,
-0.11270388960838318,
0.005057787988334894,
-0.015233734622597694,
-0.013777356594800949,
0.027896346524357796,
0.06753171235322952,
0.10297437012195587,
0.06222585588693619,
0.06522445380687714,
-0.04166161268949509,
-0.012567004188895226,
-0.07... | 0.092641 |
controller appears more than once on the list, the last one is effective. When multiple enable and disable operations are specified, either all succeed or all fail. cgroup.events A read-only flat-keyed file which exists on non-root cgroups. The following entries are defined. Unless specified otherwise, a value change i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.048060350120067596,
-0.059389062225818634,
-0.1122511476278305,
0.045042626559734344,
-0.020870622247457504,
-0.0024675459135323763,
-0.08216968178749084,
0.09556205570697784,
0.0021617072634398937,
0.05101107060909271,
0.1083587184548378,
-0.009550178423523903,
-0.0011019099038094282,
... | 0.063363 |
as create new sub-cgroups. cgroup.kill A write-only single value file which exists in non-root cgroups. The only allowed value is "1". Writing "1" to the file causes the cgroup and all descendant cgroups to be killed. This means that all processes located in the affected cgroup tree will be killed via SIGKILL. Killing ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.03058328665792942,
-0.00591904204338789,
-0.03923116251826286,
0.0012694140896201134,
-0.045010071247816086,
-0.01639256440103054,
0.01767723448574543,
0.03057507611811161,
0.012215499766170979,
0.06605573743581772,
0.04015442356467247,
-0.05174056813120842,
-0.040556203573942184,
-0.08... | 0.095127 |
the fair-class scheduler or a BPF scheduler, check out :ref:`Documentation/scheduler/sched-ext.rst `. For each of the following interface files, the above categories will be referred to. All time durations are in microseconds. cpu.stat A read-only flat-keyed file. This file exists whether the controller is enabled or n... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.0582977719604969,
-0.061562471091747284,
-0.13482177257537842,
0.07631780207157135,
0.07971730828285217,
0.012063339352607727,
0.05171247571706772,
0.07097315788269043,
0.028227953240275383,
0.041154876351356506,
0.023426640778779984,
-0.03835992142558098,
-0.05635971948504448,
-0.02761... | 0.138451 |
all the processes in the cgroup. cpu.idle A read-write single value file which exists on non-root cgroups. The default is 0. This is the cgroup analog of the per-task SCHED\_IDLE sched policy. Setting this value to a 1 will make the scheduling policy of the cgroup SCHED\_IDLE. The threads inside the cgroup will retain ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.023743942379951477,
-0.022851591929793358,
-0.08375433087348938,
0.06869523972272873,
0.02382282353937626,
0.005588752683252096,
0.03806423023343086,
0.0419502891600132,
0.0523025207221508,
0.06387494504451752,
0.018661269918084145,
0.04177247732877731,
-0.018022725358605385,
-0.0382891... | 0.193799 |
cgroup's usage goes over the high boundary, the processes of the cgroup are throttled and put under heavy reclaim pressure. Going over the high limit never invokes the OOM killer and under extreme conditions the limit may be breached. The high limit should be used in scenarios where an external process monitors the lim... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.08661327511072159,
0.003638690337538719,
-0.07935734838247299,
0.05341312289237976,
-0.00908561609685421,
-0.0807204321026802,
0.02047579549252987,
0.03146108239889145,
0.028910242021083832,
-0.0213212538510561,
0.03627956286072731,
0.08896380662918091,
-0.03561338037252426,
-0.06116374... | 0.104967 |
recent reset for that FD. A write of any non-empty string to this file resets it to the current memory usage for subsequent reads through the same file descriptor. memory.oom.group A read-write single value file which exists on non-root cgroups. The default value is "0". Determines whether the cgroup should be treated ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.030139464884996414,
0.005729992873966694,
-0.07394426316022873,
0.06368139386177063,
0.05018550157546997,
-0.055059678852558136,
0.029491716995835304,
0.06522082537412643,
0.052908603101968765,
0.041728679090738297,
0.01784813590347767,
0.0866718515753746,
-0.0657513216137886,
-0.050696... | 0.155162 |
such as brk(), sbrk(), and mmap(MAP\_ANONYMOUS). Note that some kernel configurations might account complete larger allocations (e.g., THP) if only some, but not all the memory of such an allocation is mapped anymore. file Amount of memory used to cache filesystem data, including tmpfs and shared memory. kernel (npn) A... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
0.02963060885667801,
-0.02163080871105194,
-0.0820571556687355,
-0.028464175760746002,
0.01668180152773857,
-0.01896066404879093,
-0.05821412801742554,
0.09553959965705872,
0.023907827213406563,
0.05202292650938034,
0.02950112149119377,
0.027375435456633568,
-0.013490292243659496,
-0.04983... | 0.214309 |
scanned pages proactively (in an inactive LRU list) pgsteal\_kswapd (npn) Amount of reclaimed pages by kswapd pgsteal\_direct (npn) Amount of reclaimed pages directly pgsteal\_khugepaged (npn) Amount of reclaimed pages by khugepaged pgsteal\_proactive (npn) Amount of reclaimed pages proactively pgfault (npn) Total numb... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.07656146585941315,
0.016670558601617813,
-0.05289313197135925,
0.04451865330338478,
0.03779745101928711,
-0.02232172153890133,
0.03211350739002228,
0.029833951964974403,
-0.021389689296483994,
0.0661889836192131,
0.07293665409088135,
0.1113615408539772,
0.05572713911533356,
-0.055073454... | 0.088895 |
this limit, all its further allocations will be throttled to allow userspace to implement custom out-of-memory procedures. This limit marks a point of no return for the cgroup. It is NOT designed to manage the amount of swapping a workload does during regular operation. Compare to memory.swap.max, which prohibits swapp... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.04404862970113754,
-0.032645028084516525,
-0.07632233947515488,
0.0517658069729805,
-0.07889688014984131,
-0.004556308034807444,
-0.012039278633892536,
0.0969843938946724,
0.014409818686544895,
0.02050165832042694,
-0.010865277610719204,
0.11299174278974533,
-0.026555875316262245,
-0.06... | 0.093992 |
a viable strategy. Because breach of the high limit doesn't trigger the OOM killer but throttles the offending cgroup, a management agent has ample opportunities to monitor and take appropriate actions such as granting more memory or terminating the workload. Determining whether a cgroup has enough memory is not trivia... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.0176080334931612,
0.04741501808166504,
-0.04899002984166145,
0.018727796152234077,
0.01118389330804348,
-0.015868814662098885,
0.059810563921928406,
0.059673815965652466,
0.01415765006095171,
0.046279098838567734,
0.020497586578130722,
0.000810596568044275,
0.01379162073135376,
-0.04376... | 0.108025 |
Lines are keyed by $MAJ:$MIN device numbers and not ordered. The line for a given device is populated on the first write for the device on "io.cost.qos" or "io.cost.model". The following nested keys are defined. ====== ===================================== enable Weight-based control enable ctrl "auto" or "user" rpct R... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.026253243908286095,
0.00811234675347805,
-0.0928364172577858,
0.06660528481006622,
-0.060902614146471024,
-0.0635441318154335,
0.06732871383428574,
0.0938340276479721,
0.020855288952589035,
-0.0016674763755872846,
0.061506155878305435,
-0.06766753643751144,
0.007222567219287157,
-0.0157... | 0.098422 |
coefficients. io.weight A read-write flat-keyed file which exists on non-root cgroups. The default is "default 100". The first line is the default weight applied to devices without specific override. The rest are overrides keyed by $MAJ:$MIN device numbers and not ordered. The weights are in the range [1, 10000] and sp... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.09372473508119583,
0.05524077266454697,
-0.05202452093362808,
0.0878443568944931,
-0.05347788333892822,
-0.04720332846045494,
0.02521289512515068,
0.11244837194681168,
0.0007336398120969534,
0.035406097769737244,
0.050450727343559265,
-0.025778327137231827,
0.01658996380865574,
-0.04050... | 0.148318 |
the inode to that cgroup. While this model is enough for most use cases where a given inode is mostly dirtied by a single cgroup even when the main writing cgroup changes over time, use cases where multiple cgroups write to a single inode simultaneously are not supported well. In such circumstances, a significant porti... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.03351578488945961,
-0.03432429954409599,
-0.019593296572566032,
0.042102888226509094,
-0.052849072962999344,
-0.03640091046690941,
-0.023516876623034477,
-0.03589436411857605,
0.0337308906018734,
0.022673390805721283,
0.08100837469100952,
0.018932688981294632,
-0.002734891604632139,
-0.... | 0.053119 |
or metadata IO occurring we limit the individual delay events to 1 second at a time. Once the victimized group starts meeting its latency target again it will start unthrottling any peer groups that were throttled previously. If the victimized group simply stops doing IO the global counter will unthrottle appropriately... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.018153907731175423,
-0.01578657142817974,
-0.09089306741952896,
0.045664120465517044,
0.0926392525434494,
-0.04308009147644043,
0.03266855329275131,
-0.015261088497936726,
0.07360817492008209,
0.029296686872839928,
0.051573943346738815,
-0.045732636004686356,
-0.005886839237064123,
-0.0... | 0.185783 |
the kernel. PID Interface Files ~~~~~~~~~~~~~~~~~~~ pids.max A read-write single value file which exists on non-root cgroups. The default is "max". Hard limit of number of processes. pids.current A read-only single value file which exists on non-root cgroups. The number of processes currently in the cgroup and its desc... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.05522012710571289,
-0.054346222430467606,
-0.06304468214511871,
-0.004254417028278112,
0.009246633388102055,
-0.042719416320323944,
-0.0036392558831721544,
0.08316294848918915,
0.11455389857292175,
0.0421995148062706,
0.040617506951093674,
0.07731829583644867,
-0.0036053715739399195,
-0... | 0.114536 |
which exists on non-root cpuset-enabled cgroups. It lists the requested memory nodes to be used by tasks within this cgroup. The actual list of memory nodes granted, however, is subjected to constraints imposed by its parent and can differ from the requested memory nodes. The memory node numbers are comma-separated num... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
0.02101970836520195,
-0.02092644013464451,
-0.06392911821603775,
0.10987842828035355,
0.0031626049894839525,
-0.04473428800702095,
0.02239607647061348,
-0.013011361472308636,
0.010579847730696201,
0.012864655815064907,
0.06356202065944672,
-0.05718619003891945,
-0.005446150898933411,
-0.08... | 0.169037 |
on all non-root cpuset-enabled cgroups. This file shows the effective set of exclusive CPUs that can be used to create a partition root. The content of this file will always be a subset of its parent's "cpuset.cpus.exclusive.effective" if its parent is not the root cgroup. It will also be a subset of "cpuset.cpus.exclu... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.04089454934000969,
-0.016735054552555084,
-0.08885486423969269,
0.06459260731935501,
0.02201208472251892,
-0.040075112134218216,
0.030338631942868233,
0.08523847907781601,
0.005727491341531277,
-0.03814765438437462,
0.041697368025779724,
-0.03840676322579384,
-0.023243499919772148,
-0.0... | 0.099469 |
invalid partition root, a descriptive string on why the partition is invalid is included within parentheses. For a local partition root to be valid, the following conditions must be met. 1) The parent cgroup is a valid partition root. 2) The "cpuset.cpus.exclusive.effective" file cannot be empty, though it may contain ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.04680763930082321,
-0.04267014563083649,
0.010861705988645554,
0.03326571360230446,
0.03746628761291504,
-0.014893979765474796,
-0.0011594898533076048,
0.08218710124492645,
0.049684204161167145,
0.012399046681821346,
0.05515196546912193,
-0.0369134396314621,
0.008930576033890247,
0.0228... | 0.066598 |
that describes current resource usage. It exists for all the cgroup except root. An example for mlx4 and ocrdma device follows:: mlx4\_0 hca\_handle=1 hca\_object=20 ocrdma1 hca\_handle=1 hca\_object=23 DMEM ---- The "dmem" controller regulates the distribution and accounting of device memory regions. Because each memo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.014449638314545155,
-0.02437068335711956,
-0.07775165885686874,
-0.02006090246140957,
0.0049085295759141445,
-0.06286653131246567,
0.043203774839639664,
0.11391066014766693,
0.03138541057705879,
-0.019927145913243294,
0.03663600981235504,
0.033799909055233,
0.03376356512308121,
-0.04438... | 0.178281 |
8 misc.max A read-write flat-keyed file shown in the non root cgroups. Allowed maximum usage of the resources in the cgroup and its children.:: $ cat misc.max res\_a max res\_b 4 Limit can be set by:: # echo res\_a 1 > misc.max Limit can be set to max by:: # echo res\_a max > misc.max Limits can be set higher than the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.01850801892578602,
-0.020345915108919144,
-0.08368227630853653,
0.034105729311704636,
-0.0027401663828641176,
-0.057145364582538605,
0.03676178678870201,
0.071810781955719,
0.07880545407533646,
0.05980829894542694,
0.04185662046074867,
-0.01941780187189579,
-0.034655991941690445,
-0.029... | 0.132372 |
path. For example, before creating a cgroup namespace, one would see:: # ls -l /proc/self/ns/cgroup lrwxrwxrwx 1 root root 0 2014-07-15 10:37 /proc/self/ns/cgroup -> cgroup:[4026531835] # cat /proc/self/cgroup 0::/batchjobs/container\_id1 After unsharing a new namespace, the view changes:: # ls -l /proc/self/ns/cgroup ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.08706993609666824,
-0.11236919462680817,
-0.04782683402299881,
0.037065811455249786,
-0.0015859849518164992,
-0.017573976889252663,
-0.02662561647593975,
-0.07084979861974716,
0.05452869087457657,
-0.047752443701028824,
0.057570792734622955,
-0.0983918085694313,
-0.047581978142261505,
-... | 0.098015 |
combined with restricting the view of cgroup hierarchy by namespace-private cgroupfs mount provides a properly isolated cgroup view inside the container. Information on Kernel Programming ================================= This section contains kernel programming information in the areas where interacting with cgroup is... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.08568261563777924,
0.001548352767713368,
-0.0986296683549881,
0.04317314177751541,
-0.003993417136371136,
0.0006910474039614201,
-0.019091617316007614,
0.03950483351945877,
0.01725577376782894,
0.0112658916041255,
0.025993576273322105,
-0.08079836517572403,
0.015278358943760395,
-0.0492... | 0.094843 |
how many hierarchies there might be, which meant that a thread's cgroup membership couldn't be described in finite length. The key might contain any number of entries and was unlimited in length, which made it highly awkward to manipulate and led to addition of controllers which existed only to identify membership, whi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.05382595211267471,
-0.1184573620557785,
-0.035473402589559555,
-0.036684732884168625,
-0.03093409724533558,
0.011111225001513958,
-0.10509265959262848,
0.029921365901827812,
0.09976218640804291,
-0.018279721960425377,
0.026225028559565544,
-0.03811237961053848,
0.014899462461471558,
-0.... | -0.019866 |
children cgroups competed for resources. This was nasty as two different types of entities competed and there was no obvious way to settle it. Different controllers did different things. The cpu controller considered threads and cgroups as equivalents and mapped nice levels to cgroup weights. This worked for some cases... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.0968305915594101,
-0.02181847020983696,
-0.014163770712912083,
0.07568242400884628,
-0.009009240195155144,
-0.03143120929598808,
-0.048184290528297424,
0.038479048758745193,
0.07779283076524734,
0.02047407068312168,
0.05814310535788536,
-0.06470607221126556,
-0.010898135602474213,
-0.04... | 0.142472 |
groups are organized in a global rbtree and treated like equal peers, regardless where they are located in the hierarchy. This makes subtree delegation impossible. Second, the soft limit reclaim pass is so aggressive that it not just introduces high allocation latencies into the system, but also impacts system performa... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
0.018437650054693222,
-0.00670617027208209,
0.006451827473938465,
0.060151491314172745,
0.023280475288629532,
-0.05486661195755005,
-0.012998140417039394,
0.1088583916425705,
0.05821472406387329,
-0.00536475470289588,
-0.07125336676836014,
0.05952863767743111,
0.0008863171096891165,
-0.035... | 0.085658 |
physical resources. Swap space is a resource like all others in the system, and that's why unified hierarchy allows distributing it separately. | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cgroup-v2.rst | master | linux | [
-0.03253757208585739,
-0.05365768074989319,
-0.03005211427807808,
-0.020976172760128975,
0.015394392423331738,
-0.03837968409061432,
-0.03901063650846481,
0.042529355734586716,
0.07204271852970123,
0.03561900928616524,
-0.019531385973095894,
0.04782441630959511,
0.015046135522425175,
-0.03... | 0.176434 |
Video Output Switcher Control ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2006 luming.yu@intel.com The output sysfs class driver provides an abstract video output layer that can be used to hook platform specific methods to enable/disable video output device through common sysfs interface. For example, on my IBM ThinkPad T42 laptop, ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/video-output.rst | master | linux | [
0.001731440657749772,
-0.0405910424888134,
-0.06346580386161804,
-0.03717459738254547,
0.023028897121548653,
0.006990776397287846,
0.0329812727868557,
0.06699511408805847,
-0.013887250795960426,
0.0050997985526919365,
0.06276851892471313,
-0.05954112485051155,
-0.0685466080904007,
0.038044... | 0.132513 |
.. SPDX-License-Identifier: GPL-2.0 ==== EDID ==== In the good old days when graphics parameters were configured explicitly in a file called xorg.conf, even broken hardware could be managed. Today, with the advent of Kernel Mode Setting, a graphics board is either correctly working because all components follow the sta... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/edid.rst | master | linux | [
0.016759615391492844,
0.0049754236824810505,
0.010505087673664093,
0.04574260488152504,
0.017502402886748314,
-0.037580013275146484,
0.0006821730057708919,
0.014070679433643818,
-0.01063680648803711,
-0.09020918607711792,
0.04710552841424942,
-0.015667863190174103,
0.01898888312280178,
0.0... | 0.03701 |
.. \_readme: Linux kernel release 6.x ============================================= These are the release notes for Linux version 6. Read them carefully, as they tell you what this is all about, explain how to install the kernel, and what to do if something goes wrong. What is Linux? -------------- Linux is a clone of ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/README.rst | master | linux | [
-0.0054183583706617355,
-0.018933165818452835,
-0.03284525126218796,
-0.0357644185423851,
0.08174435049295425,
-0.03643812611699104,
-0.027335764840245247,
0.04717361181974411,
-0.04443453252315521,
0.015482018701732159,
0.04978585243225098,
0.024350568652153015,
-0.11219605058431625,
-0.1... | 0.216311 |
failed patches (some-file-name# or some-file-name.rej). If there are, either you or I have made a mistake. Unlike patches for the 6.x kernels, patches for the 6.x.y kernels (also known as the -stable kernels) are not incremental but instead apply directly to the base 6.x kernel. For example, if your base kernel is 6.0 ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/README.rst | master | linux | [
-0.022887730970978737,
-0.0859249010682106,
0.01013310719281435,
-0.04194924235343933,
0.03547493368387222,
-0.021727537736296654,
-0.02275083027780056,
0.055755507200956345,
-0.03939417377114296,
0.026924483478069305,
0.06993792951107025,
0.06605326384305954,
-0.02500941790640354,
-0.1013... | 0.054631 |
to 'y' as much as possible. "make allmodconfig" Create a ./.config file by setting symbol values to 'm' as much as possible. "make allnoconfig" Create a ./.config file by setting symbol values to 'n' as much as possible. "make randconfig" Create a ./.config file by setting symbol values to random values. "make localmod... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/README.rst | master | linux | [
-0.01596776209771633,
-0.06489817053079605,
-0.08957643061876297,
-0.00039553127135150135,
0.05705946311354637,
0.02153816632926464,
-0.024751707911491394,
0.030823033303022385,
-0.09507810324430466,
-0.04567055031657219,
0.09278607368469238,
-0.0347999632358551,
0.08971909433603287,
-0.08... | -0.005656 |
backup kernel handy in case something goes wrong. This is especially true for the development releases, since each new release contains new code which has not been debugged. Make sure you keep a backup of the modules corresponding to that kernel, as well. If you are installing a new kernel with the same version number ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/README.rst | master | linux | [
0.02486920915544033,
-0.04318476840853691,
0.02361634559929371,
-0.0283596683293581,
0.10808692127466202,
-0.03485099598765373,
-0.05134017765522003,
0.04412221908569336,
-0.058044880628585815,
-0.0381002202630043,
0.09267707914113998,
-0.02893933095037937,
-0.06839613616466522,
-0.0446745... | -0.011255 |
Dynamic debug +++++++++++++ Introduction ============ Dynamic debug allows you to dynamically enable/disable kernel debug-print code to obtain additional kernel information. If ``/proc/dynamic\_debug/control`` exists, your kernel has dynamic debug. You'll need root access (sudo su) to use this. Dynamic debug provides: ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dynamic-debug-howto.rst | master | linux | [
-0.004137392155826092,
-0.00836828351020813,
-0.08463267236948013,
0.07690693438053131,
0.06257805973291397,
-0.06378581374883652,
0.02273797057569027,
0.10451986640691757,
-0.057553596794605255,
0.021163374185562134,
0.04521565139293671,
-0.03699984773993492,
-0.02357463911175728,
-0.0776... | 0.025521 |
note:: ``line-range`` cannot contain space, e.g. "1-30" is valid range but "1 - 30" is not. The meanings of each keyword are: func The given string is compared against the function name of each callsite. Example:: func svc\_tcp\_accept func \*recv\* # in rfcomm, bluetooth, ping, tcp file The given string is compared ag... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dynamic-debug-howto.rst | master | linux | [
-0.10040159523487091,
-0.023312652483582497,
-0.11350356787443161,
-0.029842883348464966,
-0.01707160472869873,
-0.04482538253068924,
0.05435902997851372,
0.14795127511024475,
0.04202154278755188,
-0.03935999050736427,
0.07784320414066315,
-0.015307096764445305,
-0.02231440320611,
-0.07875... | 0.178045 |
matches a flags specification. To clear all flags at once, use ``=\_`` or ``-fslmptd``. Debug messages during Boot Process ================================== To activate debug messages for core code and built-in modules during the boot process, even before userspace and debugfs exists, use ``dyndbg="QUERY"`` or ``modul... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dynamic-debug-howto.rst | master | linux | [
-0.014306011609733105,
0.02198304980993271,
-0.01878206618130207,
0.057362549006938934,
0.01872495748102665,
-0.0898522362112999,
0.06310909241437912,
0.10845000296831131,
-0.07912175357341766,
-0.030333848670125008,
0.04885509982705116,
-0.051466204226017,
0.032906435430049896,
-0.0528025... | 0.007885 |
boot-args example, with newlines and comments for readability Kernel command line: ... // see what's going on in dyndbg=value processing dynamic\_debug.verbose=3 // enable pr\_debugs in the btrfs module (can be builtin or loadable) btrfs.dyndbg="+p" // enable pr\_debugs in all files under init/ // and the function pars... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/dynamic-debug-howto.rst | master | linux | [
-0.07336551696062088,
-0.028338313102722168,
-0.046126920729875565,
0.06361677497625351,
0.10728061199188232,
-0.11037641018629074,
0.004422985948622227,
0.11953015625476837,
-0.08674459904432297,
0.008340477012097836,
0.07801198214292526,
0.001498713972978294,
-0.07255911082029343,
-0.017... | 0.062701 |
.. SPDX-License-Identifier: GPL-2.0 ==================== Linux NVMe multipath ==================== This document describes NVMe multipath and its path selection policies supported by the Linux NVMe host driver. Introduction ============ The NVMe multipath feature in Linux integrates namespaces with the same identifier ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/nvme-multipath.rst | master | linux | [
-0.02928159572184086,
-0.05231161415576935,
-0.021280717104673386,
0.002830951241776347,
0.01929851807653904,
-0.08438464254140854,
0.006643001921474934,
0.004927078727632761,
0.00953049585223198,
-0.10400951653718948,
-0.04727303236722946,
0.041302021592855453,
0.004528724122792482,
-0.01... | 0.144915 |
Linux Magic System Request Key Hacks ==================================== Documentation for sysrq.c What is the magic SysRq key? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It is a 'magical' key combo you can hit which the kernel will respond to regardless of whatever else it is doing, unless it is completely locked up. How do I enab... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/sysrq.rst | master | linux | [
-0.005508748814463615,
-0.08971866220235825,
-0.13612611591815948,
-0.037300944328308105,
-0.008977722376585007,
-0.019556617364287376,
0.0741969421505928,
0.032772623002529144,
-0.060157306492328644,
0.049559514969587326,
0.034493181854486465,
0.018649116158485413,
0.048375993967056274,
-... | 0.06961 |
all processes, except for init. ``f`` Will call the oom killer to kill a memory hog process, but do not panic if nothing can be killed. ``g`` Used by kgdb (kernel debugger) ``h`` Will display help (actually any other key than those listed here will display help. but ``h`` is easy to remember :-) ``i`` Send a SIGKILL to... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/sysrq.rst | master | linux | [
0.0037899650633335114,
0.018528573215007782,
-0.05544523149728775,
-0.007887311279773712,
0.10528622567653656,
-0.023997794836759567,
0.04329359903931618,
0.10680839419364929,
-0.0032347191590815783,
0.0819615051150322,
-0.007731628604233265,
0.055878445506095886,
0.021625623106956482,
-0.... | 0.172082 |
mark filesystems as properly unmounted. From the running system's point of view, they will be remounted read-only. The remount isn't complete until you see the "OK" and "Done" message appear on the screen. The loglevels ``0``-``9`` are useful when your console is being flooded with kernel messages you do not want to se... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/sysrq.rst | master | linux | [
0.019467242062091827,
-0.013610480353236198,
-0.008840525522828102,
-0.026867864653468132,
0.12253863364458084,
-0.03949753940105438,
0.018825408071279526,
0.10344812273979187,
0.061074111610651016,
0.059793632477521896,
0.05519988760352135,
0.027090443298220634,
-0.014462419785559177,
0.0... | 0.176397 |
key table has a number of operations registered into it at compile time, but is mutable, and 2 functions are exported for interface to it:: register\_sysrq\_key and unregister\_sysrq\_key. Of course, never ever leave an invalid pointer in the table. I.e., when your module that called register\_sysrq\_key() exits, it mu... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/sysrq.rst | master | linux | [
0.007560115773230791,
-0.060193419456481934,
-0.11045534163713455,
0.011367790400981903,
-0.05258360877633095,
0.012462995015084743,
0.118016816675663,
0.07617819309234619,
-0.012484386563301086,
0.055249761790037155,
0.06337825953960419,
-0.020054617896676064,
0.04021888226270676,
-0.0399... | 0.061936 |
===================== I/O statistics fields ===================== The kernel exposes disk statistics via ``/proc/diskstats`` and ``/sys/block//stat``. These stats are usually accessed via tools such as ``sar`` and ``iostat``. Here are examples using a disk with two partitions:: /proc/diskstats: 259 0 nvme0n1 255999 814... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/iostats.rst | master | linux | [
0.0013524049427360296,
-0.05886707454919815,
-0.08166870474815369,
0.03983926773071289,
0.05755230039358139,
-0.14565975964069366,
-0.028563054278492928,
0.10449188202619553,
0.041246529668569565,
0.022244160994887352,
-0.004846236202865839,
-0.013326271437108517,
0.01569278910756111,
-0.0... | 0.136681 |
so long as field 9 is nonzero. Since 5.0 this field counts jiffies when at least one request was started or completed. If request runs more than 2 jiffies then some I/O time might be not accounted in case of concurrent requests. Field 11 -- weighted # of milliseconds spent doing I/Os (unsigned int) This field is increm... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/iostats.rst | master | linux | [
-0.02550976350903511,
-0.014867370016872883,
-0.011955476365983486,
-0.003507989924401045,
0.06319724023342133,
-0.12722735106945038,
0.029036972671747208,
0.021222125738859177,
0.0864541307091713,
-0.014696970582008362,
-0.01333626452833414,
0.0493764765560627,
-0.02757997065782547,
-0.04... | 0.143967 |
the total number of sectors requested to be written to this partition. Note that since the address is translated to a disk-relative one, and no record of the partition-relative address is kept, the subsequent success or failure of the read cannot be attributed to the partition. In other words, the number of reads for p... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/iostats.rst | master | linux | [
-0.025338463485240936,
-0.04499058052897453,
0.0624672994017601,
0.03483746573328972,
0.013126086443662643,
-0.133819580078125,
-0.014572692103683949,
0.06514361500740051,
0.11926432698965073,
0.008883210830390453,
-0.050483960658311844,
0.04492298886179924,
0.024732666090130806,
-0.028303... | 0.050678 |
Using the initial RAM disk (initrd) =================================== Written 1996,2000 by Werner Almesberger and Hans Lermen initrd provides the capability to load a RAM disk by the boot loader. This RAM disk can then be mounted as the root file system and programs can be run from it. Afterwards, a new root file sys... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/initrd.rst | master | linux | [
-0.05509171262383461,
-0.0007648630999028683,
-0.068367138504982,
0.04959452152252197,
0.029177727177739143,
-0.011696649715304375,
-0.013739385642111301,
0.13577470183372498,
0.04486796632409096,
-0.014559742994606495,
0.05839253589510918,
0.15563605725765228,
0.04497344046831131,
-0.0405... | 0.157381 |
is just as simple:: mkdir /tmp/imagefile cd /tmp/imagefile gzip -cd /boot/imagefile.img | cpio -imd --quiet Installation ------------ First, a directory for the initrd file system has to be created on the "normal" root file system, e.g.:: # mkdir /initrd The name is not relevant. More details can be found on the :manpa... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/initrd.rst | master | linux | [
-0.06961599737405777,
0.0018174091819673777,
-0.04737453907728195,
-0.06011922284960747,
0.06964470446109772,
-0.08252926915884018,
-0.0028354476671665907,
0.13475275039672852,
-0.000742491742130369,
0.026210375130176544,
0.14272339642047882,
0.08456166088581085,
0.08136925846338272,
0.012... | 0.110868 |
either the global section or to the section of the respective kernel in ``/etc/lilo.conf``, and pass the options using APPEND, e.g.:: image = /bzImage initrd = /boot/initrd.gz append = "root=/dev/ram0 rw" and run ``/sbin/lilo`` For other boot loaders, please refer to the respective documentation. Now you can boot and e... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/initrd.rst | master | linux | [
-0.05090663954615593,
-0.028509007766842842,
-0.05526191368699074,
-0.011324071325361729,
0.04233768209815025,
-0.035962894558906555,
-0.014455821365118027,
0.1280284821987152,
-0.11254166811704636,
0.02196025289595127,
0.0812368243932724,
0.06921364367008209,
0.027892721816897392,
-0.0025... | 0.062228 |
file system (this doesn't have to be a very usable system yet) 5) ``/sbin/init`` invokes ``pivot\_root`` to change the root file system and execs - via chroot - a program that continues the installation 6) the boot loader is installed 7) the boot loader is configured to load an initrd with the set of modules that was u... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/initrd.rst | master | linux | [
-0.07536495476961136,
-0.007493475452065468,
-0.045106567442417145,
-0.015969814732670784,
0.08449932187795639,
-0.04540829733014107,
-0.005758954212069511,
0.12049997597932816,
-0.01734163798391819,
-0.017376212403178215,
0.07329956442117691,
0.08422491699457169,
0.02441692166030407,
-0.0... | 0.130841 |
exited, the kernel would mount again your initrd as root, this time executing ``/sbin/init``. Again, it would be the duty of this init to build the right environment (maybe using the ``root= device`` passed on the cmdline) before the final execution of the real ``/sbin/init``. Resources --------- .. [#f1] Almesberger, ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/initrd.rst | master | linux | [
-0.045706529170274734,
0.0020919209346175194,
-0.04106386750936508,
0.024973178282380104,
0.15769049525260925,
-0.11647839099168777,
-0.052229441702365875,
0.12038067728281021,
-0.04334493353962898,
-0.047184206545352936,
0.04766504466533661,
0.05581789091229439,
-0.014117701910436153,
0.0... | 0.061916 |
========================================== Reducing OS jitter due to per-cpu kthreads ========================================== This document lists per-CPU kthreads in the Linux kernel and presents options to control their OS jitter. Note that non-per-CPU kthreads are not listed here. To reduce OS jitter from non-per-... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.03993845731019974,
0.004581197164952755,
-0.10449253022670746,
0.06316440552473068,
-0.05950404331088066,
-0.11224061250686646,
0.060712121427059174,
0.01180310733616352,
-0.003997372929006815,
-0.03034420683979988,
0.007407653611153364,
-0.007780849002301693,
-0.03144599497318268,
-0.0... | 0.184198 |
I/O on other CPUs. 3. Once your application has started, prevent CPU-hotplug operations from being initiated from tasks that might run on the CPU to be de-jittered. (It is OK to force this CPU offline and then bring it back online before you start your application.) IRQ\_POLL\_SOFTIRQ ---------------- Do all of the fol... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.059582777321338654,
-0.029057027772068977,
-0.042440466582775116,
0.05370680242776871,
0.0012001552386209369,
-0.09820961207151413,
0.0571339949965477,
0.0436202809214592,
-0.022215772420167923,
0.006336777471005917,
-0.0006715768831782043,
-0.000253343372605741,
-0.046253710985183716,
... | 0.123303 |
the CPU goes idle frequently, allowing other CPUs to detect that it has passed through an RCU quiescent state. If the kernel is built with CONFIG\_NO\_HZ\_FULL=y, userspace execution also allows other CPUs to detect that the CPU in question has passed through a quiescent state. c. To the extent possible, keep the CPU o... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.05053244158625603,
0.04534224420785904,
-0.03210531547665596,
0.05710400640964508,
0.03601113706827164,
-0.09491346031427383,
0.004353432450443506,
0.0023799960035830736,
0.06927461177110672,
-0.021595660597085953,
0.013446218334138393,
-0.057799432426691055,
-0.010367278009653091,
-0.0... | 0.095247 |
from being created in the first place, and also obviates the need for RCU priority boosting. This approach is feasible for workloads that do not require high degrees of responsiveness. 2. Build the kernel with CONFIG\_RCU\_BOOST=n. This prevents these kthreads from being created in the first place. This approach is fea... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.11524944752454758,
0.04138917475938797,
-0.02593618631362915,
0.03344263508915901,
0.012682924047112465,
-0.010632087476551533,
-0.04497218132019043,
-0.038741711527109146,
0.0013902049977332354,
-0.025317557156085968,
0.02008719928562641,
-0.004474654793739319,
0.010039440356194973,
-0... | 0.077373 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) .. See the bottom of this file for additional redistribution information. Reporting issues ++++++++++++++++ The short guide (aka TL;DR) =========================== Are you facing a regression with vanilla kernels from the same stable or longterm series? One still supp... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.03498361259698868,
-0.08567182719707489,
-0.0019017213489860296,
0.04086824133992195,
0.08761459589004517,
-0.028711983934044838,
-0.06783454120159149,
-0.004684747196733952,
-0.03875764086842537,
-0.02476668916642666,
-0.022978372871875763,
0.01325589045882225,
-0.021951304748654366,
0... | -0.007953 |
invest in this process won't feel wasted in the end: \* Are you facing an issue with a Linux kernel a hardware or software vendor provided? Then in almost all cases you are better off to stop reading this document and reporting the issue to your vendor instead, unless you are willing to install the latest Linux version... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.028752973303198814,
-0.005523581523448229,
0.010102961212396622,
0.01943461410701275,
0.1146743893623352,
-0.11338485777378082,
-0.05280674248933792,
0.10447447001934052,
-0.06159164011478424,
0.009513122960925102,
0.04908722639083862,
0.0023431621957570314,
-0.04330070689320564,
-0.036... | 0.130249 |
longterm kernels. \* Optimize your notes: try to find and write the most straightforward way to reproduce your issue. Make sure the end result has all the important details, and at the same time is easy to read and understand for others that hear about it for the first time. And if you learned something in this process... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.0076898448169231415,
-0.03627489507198334,
0.02216409705579281,
0.025080835446715355,
0.059571634978055954,
-0.11051807552576065,
-0.09455568343400955,
0.09977322071790695,
-0.05065656080842018,
-0.007090551778674126,
0.03825102746486664,
-0.008619974367320538,
-0.02198931574821472,
-0.0... | 0.099974 |
build of the last version known to work performs fine as well. \* Send a short problem report to the Linux stable mailing list (stable@vger.kernel.org) and CC the Linux regressions mailing list (regressions@lists.linux.dev); if you suspect the cause in a particular subsystem, CC its maintainer and its mailing list. Rou... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.016328858211636543,
-0.08875510096549988,
0.06363441795110703,
0.06420400738716125,
0.11132846027612686,
-0.0687488466501236,
-0.138572558760643,
0.012694668024778366,
-0.04799431934952736,
-0.025032546371221542,
0.05682627111673355,
0.043773356825113297,
-0.06800290197134018,
0.01404444... | -0.028153 |
are completely outside the scope of the Linux kernel, its development community, and this document. That's why you can't demand anything such a contract guarantees in this context, not even if the developer handling the issue works for the vendor in question. If you want to claim your rights, use the vendor's support c... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.06662243604660034,
0.0348496250808239,
-0.0331195704638958,
0.00502148037776351,
0.02391481213271618,
-0.01774112693965435,
-0.032739877700805664,
0.13232025504112244,
-0.07524276524782181,
0.01632028818130493,
0.014545666985213757,
-0.022944269701838493,
-0.009429807774722576,
-0.05475... | 0.044592 |
kernel based on a recent Linux version; that for example often holds true for the mainline kernels shipped by Debian GNU/Linux Sid or Fedora Rawhide. Some developers will also accept reports about issues with kernels from distributions shipping the latest stable kernel, as long as it's only slightly modified; that for ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.03907281532883644,
-0.09797312319278717,
0.028704455122351646,
0.045812107622623444,
0.10458691418170929,
-0.07582849264144897,
-0.10070762038230896,
0.0822349414229393,
-0.08606970310211182,
-0.02572246827185154,
0.05149422585964203,
0.0030312733724713326,
-0.07274909317493439,
-0.01768... | 0.016755 |
involved. Note, searching `bugzilla.kernel.org `\_ might also be a good idea, as that might provide valuable insights or turn up matching reports. If you find the latter, just keep in mind: most subsystems expect reports in different places, as described below in the section "Check where you need to report your issue".... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.05894682556390762,
-0.046675506979227066,
-0.04588025063276291,
0.044631361961364746,
0.04982512816786766,
-0.07224101573228836,
-0.030145304277539253,
0.05779512971639633,
-0.09813182801008224,
0.012361746281385422,
0.025808600708842278,
0.042928870767354965,
0.001138880499638617,
-0.0... | 0.105399 |
\* When dealing with a regression, make sure it's not something else that changed in parallel to updating the kernel. The problem for example might be caused by other software that was updated at the same time. It can also happen that a hardware component coincidentally just broke when you rebooted into a new kernel fo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.04433516785502434,
-0.07118601351976395,
0.0723460242152214,
0.05801587924361229,
0.1096569299697876,
-0.10131483525037766,
-0.04215015098452568,
0.05967806652188301,
-0.018013207241892815,
-0.025317242369055748,
0.02097262628376484,
0.036173202097415924,
-0.04636330530047417,
-0.002675... | 0.103814 |
search for a line starting with 'CPU:'. It should end with 'Not tainted' if the kernel was not tainted when it noticed the problem; it was tainted if you see 'Tainted:' followed by a few spaces and some letters. If your kernel is tainted, study Documentation/admin-guide/tainted-kernels.rst to find out why. Try to elimi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.034859757870435715,
-0.054668597877025604,
0.03808533027768135,
0.04205365851521492,
0.14559891819953918,
-0.09794337302446365,
-0.01536782830953598,
0.037563834339380264,
0.054054249078035355,
-0.07766994833946228,
0.003866475075483322,
-0.02089347504079342,
-0.011055279523134232,
0.023... | -0.004915 |
you will have to test if the issue happens with other kernel versions. Therefore, it will make your work easier if you know exactly how to reproduce an issue quickly on a freshly booted system. Note: it's often fruitless to report issues that only happened once, as they might be caused by a bit flip due to cosmic radia... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.013727943412959576,
-0.08313494175672531,
0.07749711722135544,
0.09704497456550598,
0.16495424509048462,
-0.08392436802387238,
-0.1543184369802475,
0.023275908082723618,
-0.02373453602194786,
-0.04326217994093895,
0.06178942322731018,
0.024105237796902657,
-0.018397534266114235,
-0.0148... | -0.002185 |
you for example might want to look at the output of ``lspci -k``, as it lists devices on the PCI/PCIe bus and the kernel module driving it:: [user@something ~]$ lspci -k [...] 3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. Device 1535 Ke... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.009846191853284836,
-0.0018106262432411313,
-0.08222927898168564,
0.03172357752919197,
0.07162589579820633,
-0.0036029554903507233,
-0.028685949742794037,
-0.04500235244631767,
0.01369587704539299,
0.007479379884898663,
0.0967441126704216,
0.016181200742721558,
-0.020382283255457878,
0.... | 0.016447 |
Kernel Mailing List (LKML) to CC. Don't omit either of the mailing lists when sending your issue report by mail later! Maintainers are busy people and might leave some work for other developers on the subsystem specific list; and LKML is important to have one place where all issue reports can be found. Finding the main... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.06208473816514015,
0.0013937753392383456,
-0.055336154997348785,
0.0422641783952713,
0.15604016184806824,
-0.04803026467561722,
0.018736179918050766,
0.07540544122457504,
-0.06860622018575668,
-0.05032553896307945,
0.0565020851790905,
-0.06394047290086746,
-0.016931157559156418,
-0.0636... | 0.049741 |
It's also wise to check the internet, LKML and maybe bugzilla.kernel.org again at this point. If your report needs to be filed in a bug tracker, you may want to check the mailing list archives for the subsystem as well, as someone might have reported it only there. For details how to search and what to do if you find m... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.017442917451262474,
-0.05498875305056572,
-0.0528225302696228,
0.04057281091809273,
0.09772714227437973,
-0.05409525707364082,
-0.14175909757614136,
0.09643857926130295,
-0.08047320693731308,
-0.03292739763855934,
0.055899884551763535,
0.022837145254015923,
-0.047726355493068695,
-0.003... | 0.043514 |
(5.8-rc1) shows up on kernel.org. That's because the Linux development cycle then is in its two-week long 'merge window'. The bulk of the changes and all intrusive ones get merged for the next release during this time. It's a bit more risky to use mainline during this period. Kernel developers are also often quite busy... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.009754616767168045,
-0.05582521855831146,
0.05700007826089859,
0.060061998665332794,
0.10196197032928467,
-0.040738996118307114,
-0.10561614483594894,
0.12007986009120941,
-0.02885768935084343,
-0.029062969610095024,
0.05796852335333824,
0.05350343883037567,
-0.07586901634931564,
0.0034... | -0.002411 |
in this document. Also be aware that pre-compiled kernels might lack debug symbols that are needed to decode messages the kernel prints when a panic, Oops, warning, or BUG occurs; if you plan to decode those, you might be better off compiling a kernel yourself (see the end of this subsection and the section titled 'Dec... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.046906717121601105,
-0.05130131542682648,
0.03882180526852608,
0.024036981165409088,
0.0728849247097969,
-0.05655408278107643,
-0.005661180708557367,
0.06953482329845428,
-0.03872746229171753,
-0.010328643023967743,
0.07957220822572708,
0.03535335883498192,
-0.020943686366081238,
-0.077... | 0.112862 |
those). If you prefer to use one of those or just want to help their users, head over to the section "Details about reporting issues only occurring in older kernel version lines" below. Optimize description to reproduce issue --------------------------------------- \*Optimize your notes: try to find and write the most ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.03883688151836395,
0.05632559210062027,
-0.029846487566828728,
0.03860769793391228,
0.05794762820005417,
-0.06648143380880356,
-0.04337180405855179,
0.10700208693742752,
-0.05353284627199173,
0.011340096592903137,
0.056783951818943024,
0.01615498960018158,
-0.013673958368599415,
0.00091... | 0.145653 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.