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 |
|---|---|---|---|---|---|
other kernel configuration options: \* Are you running Debian? Then you want to avoid known problems by performing additional adjustments explained in the reference section. [:ref:`details `]. \* If you want to influence other aspects of the configuration, do so now using your preferred tool. Note, to use make targets ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.03327150642871857,
-0.00024328257131855935,
-0.02393954247236252,
-0.031055497005581856,
0.026812216266989708,
-0.055609263479709625,
-0.04314957559108734,
0.06293486803770065,
-0.04262775555253029,
-0.05005554482340813,
0.09478189796209335,
-0.06741882860660553,
-0.00445909146219492,
-... | 0.021973 |
case you plan to follow this guide further, check how much storage space the kernel, its modules, and other related files like the initramfs consume:: du -ch /boot/\*$(make -s kernelrelease)\* | tail -n 1 du -sh /lib/modules/$(make -s kernelrelease)/ Write down or remember those two values for later: they enable you to... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.012704940512776375,
-0.03626416251063347,
-0.0351402647793293,
-0.0024478279519826174,
0.12473545968532562,
-0.08030368387699127,
0.02616894245147705,
0.08174075186252594,
-0.008986118249595165,
-0.03453188017010689,
0.1063261479139328,
-0.020081134513020515,
0.0016064262017607689,
-0.0... | 0.059905 |
assumed to be 6.0 here):: cd ~/linux/ git switch --discard-changes --detach v6.0 Now use the checked out code to configure, build, and install another kernel using the commands the previous subsection explained in more detail:: cp ~/kernel-config-working .config make olddefconfig make -j $(nproc --all) # \* Check if th... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.01057991199195385,
-0.11361220479011536,
-0.003549338784068823,
0.004819842521101236,
0.04440635070204735,
-0.08112145215272903,
-0.015569995157420635,
0.03038574382662773,
-0.043042197823524475,
-0.03863061964511871,
0.12289901822805405,
-0.022010980173945427,
-0.09990254044532776,
-0.0... | 0.045582 |
so, it will print something like 'Bisecting: 675 revisions left to test after this (roughly 10 steps)' to indicate how many further changes it expects to be tested. Now build and install another kernel using the instructions from the previous step; afterwards follow the instructions in this step again. Repeat this agai... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.06093175336718559,
-0.02986500971019268,
0.038972172886133194,
-0.004115371964871883,
0.05952444672584534,
-0.10522603988647461,
0.01412465050816536,
0.016643110662698746,
0.014580098912119865,
0.007934470660984516,
0.06713280826807022,
-0.047264959663152695,
0.014360282570123672,
-0.048... | 0.046811 |
[:ref:`details `] .. \_introclosure\_bissbs: Complementary tasks: cleanup during and after the bisection ----------------------------------------------------------- During and after following this guide you might want or need to remove some of the kernels you installed: the boot menu otherwise will become confusing or ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.027867287397384644,
0.030764928087592125,
0.016339758411049843,
-0.04103948548436165,
0.11670234054327011,
-0.09360750019550323,
0.008893461897969246,
0.024158209562301636,
-0.022731047123670578,
-0.07295935600996017,
0.0993710532784462,
0.0040411869995296,
-0.009711874648928642,
-0.0623... | 0.074031 |
over:: cp ~/kernel-config-working .config \* Your next step depends on what you want to do: \* In case you just want to test the latest codebase, head to the next step, you are already all set. \* In case you want to test if a revert fixes an issue, revert one or multiple changes by specifying their commit ids:: git re... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.019070956856012344,
-0.025336854159832,
0.03812892362475395,
0.011684142053127289,
0.03918216750025749,
-0.043164730072021484,
-0.021817611530423164,
0.04021509736776352,
-0.04889378696680069,
0.006608861032873392,
0.08761047571897507,
-0.034781213849782944,
0.024766674265265465,
-0.071... | 0.06252 |
more detail. [:ref:`back to step-by-step guide `] .. \_secureboot\_bisref: Deal with techniques like Secure Boot ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ \*On platforms with 'Secure Boot' or similar techniques, prepare everything to ensure the system will permit your self-compiled kernel to boot later.\* [:ref:`... `] Man... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.017356593161821365,
0.029521115124225616,
-0.033140502870082855,
-0.010142548009753227,
0.08229546248912811,
0.0003452033270150423,
0.018904490396380424,
0.08608400076627731,
-0.041289739310741425,
-0.06270744651556015,
0.04176904633641243,
0.006092382594943047,
0.030531179159879684,
0.... | 0.042782 |
normally should not happen due to the way the stable/longterm maintainers maintain the code. It's thus pretty safe to assume 6.0 as a 'good' kernel. That assumption will be tested anyway, as that kernel will be built and tested in the segment '2' of this guide; Git would force you to do this as well, if you tried bisec... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.013427646830677986,
-0.07550762593746185,
-0.018644217401742935,
-0.024037186056375504,
0.04201948270201683,
-0.09921252727508545,
-0.1128091812133789,
0.06294562667608261,
-0.08209310472011566,
-0.04062037169933319,
0.06054597347974777,
0.006510119419544935,
-0.08185070753097534,
-0.09... | 0.037156 |
deepen your clone's history to the second predecessor of the mainline release of your 'good' version. In case the latter are 6.0 or 6.0.13, 5.19 would be the first predecessor and 5.18 the second -- hence deepen the history up to that version:: git fetch --shallow-exclude=v5.18 mainline Afterwards add the stable Git re... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.03144414350390434,
-0.02427217736840248,
0.13645517826080322,
-0.02833152748644352,
-0.03367334604263306,
-0.09442469477653503,
-0.07607237994670868,
0.03713344410061836,
0.013013877905905247,
-0.019191712141036987,
0.027100317180156708,
0.03431408852338791,
0.011389821767807007,
-0.096... | -0.024084 |
options manually, use ``make oldconfig`` instead. Then for each undefined configuration option you will be asked how to proceed; in case you are unsure what to answer, simply hit 'enter' to apply the default value. Note though that for bisections you normally want to go with the defaults, as you otherwise might enable ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.023467281833291054,
-0.04610270634293556,
0.030791280791163445,
0.06746235489845276,
0.1104949563741684,
-0.03459035977721214,
-0.04095656797289848,
0.031883783638477325,
-0.0914410948753357,
-0.0831252783536911,
0.14108650386333466,
0.031244441866874695,
-0.01629948616027832,
-0.0378335... | 0.003447 |
file to your build's host home directory. Then run these commands instead of the one the step-by-step guide mentions:: yes '' | make LSMOD=~/lsmod\_foo-machine localmodconfig [:ref:`back to step-by-step guide `] .. \_tagging\_bisref: Tag the kernels about to be build ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ \*Ensure all the k... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.009043268859386444,
-0.004894912708550692,
-0.005910996813327074,
-0.042547065764665604,
0.1154666468501091,
-0.05529548227787018,
-0.04945378378033638,
0.034544672816991806,
-0.08715006709098816,
-0.023524705320596695,
0.06595547497272491,
-0.08817107230424881,
-0.008739527314901352,
-... | -0.042034 |
missing. [:ref:`back to step-by-step guide `] .. \_saveconfig\_bisref: Put the .config file aside ~~~~~~~~~~~~~~~~~~~~~~~~~~ \*Reprocess the .config after the latest changes and store it in a safe place.\* [:ref:`... `] Put the .config you prepared aside, as you want to copy it back to the build directory every time du... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.0496329590678215,
-0.03692702576518059,
-0.033259302377700806,
-0.0069019608199596405,
0.09590374678373337,
-0.03314316272735596,
0.009279502555727959,
0.03285117819905281,
-0.07382676005363464,
-0.05298082157969475,
0.10293515771627426,
-0.022266538813710213,
-0.004908310249447823,
-0.... | 0.017066 |
developers tell you to evaluate which of the two cases it is before they take a closer look. [:ref:`back to step-by-step guide `] .. \_checkoutmaster\_bisref: Check out the latest Linux codebase ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ \*Check out the latest Linux codebase.\* [:ref:`... `] In case you later want to recheck ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.00012678749044425786,
-0.003986983094364405,
0.020521903410553932,
-0.03361450880765915,
0.09714864194393158,
-0.12455017119646072,
0.026774270460009575,
0.06275156885385513,
-0.020534545183181763,
-0.03745497390627861,
0.08868099004030228,
-0.018765680491924286,
0.015287050046026707,
-... | -0.018772 |
is just a selection of available make targets for this purpose, see ``make help`` for others. You can also use these targets after running ``make -j $(nproc --all)``, as they will pick up everything already built. If you employ the targets to generate deb or rpm packages, ignore the step-by-step guide's instructions on... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.06893881410360336,
-0.03733179718255997,
-0.010192431509494781,
-0.044068433344364166,
0.11897658556699753,
-0.08011199533939362,
-0.019762245938181877,
0.00021558649314101785,
-0.04460251331329346,
-0.059007428586483,
0.057669900357723236,
-0.04963088780641556,
0.006287275813519955,
-0... | 0.011586 |
as tainted when something happens that potentially leads to follow-up errors that look totally unrelated. That is why developers might ignore or react scantly to reports from tainted kernels -- unless of course the kernel set the flag right when the reported bug occurred. That's why you want check why a kernel is taint... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.017088305205106735,
-0.05504393205046654,
-0.02538404054939747,
0.05537174642086029,
0.17738306522369385,
-0.055969592183828354,
-0.01596660353243351,
0.07362312078475952,
-0.017408303916454315,
-0.017373668029904366,
0.013052075169980526,
-0.018317807465791702,
0.022123821079730988,
-0... | 0.041828 |
feature that broke with newer kernels does not work with your first self-built kernel, find and resolve the cause before moving on. There are a multitude of reasons why this might happen. Some ideas where to look: \* Check the taint status and the output of ``dmesg``, maybe something unrelated went wrong. \* Maybe loca... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.03576719015836716,
-0.07610740512609482,
0.05903548002243042,
0.029562927782535553,
0.1590433120727539,
-0.10042798519134521,
-0.10426533222198486,
0.04511810094118118,
-0.11293870955705643,
-0.0540732704102993,
0.09810386598110199,
-0.012896468862891197,
-0.07918159663677216,
0.02318512... | 0.013521 |
the current .config file in a safe place.\* [:ref:`... `] As indicated above: declaring just one kernel wrongly as 'good' or 'bad' will render the end result of a bisection useless. In that case you'd normally have to restart the bisection from scratch. The log can prevent that, as it might allow someone to point out w... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.00542067876085639,
-0.017405347898602486,
0.0131915882229805,
0.04614752158522606,
0.13848184049129486,
-0.07613322883844376,
0.007869459688663483,
0.040051866322755814,
-0.041984595358371735,
0.0068016923032701015,
0.05698360502719879,
0.032668400555849075,
-0.0075386893004179,
-0.03320... | 0.060246 |
that have '6.0-rc1-local-gcafec0cacaca0' in their name and consider deleting them as well. Now remove the boot entry for the kernel from your bootloader's configuration; the steps to do that vary quite a bit between Linux distributions. Note, be careful with wildcards like '\*' when deleting files or directories for ke... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
-0.018666855990886688,
0.028288166970014572,
0.020619576796889305,
-0.007910100743174553,
0.10373025387525558,
-0.05292121693491936,
0.038953352719545364,
-0.020001700147986412,
-0.004223525524139404,
-0.01764243096113205,
0.12077460438013077,
-0.03373977914452553,
-0.00849202647805214,
0.... | 0.051085 |
the guide, but ignore the instructions outlining how to compile, install, and reboot into a kernel every time they come up. Instead build like this:: cp ~/kernel-config-working .config make olddefconfig && make -j $(nproc --all) targz-pkg This will generate a gzipped tar file whose name is printed in the last line show... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst | master | linux | [
0.005306398496031761,
-0.03398919105529785,
-0.06190824881196022,
0.0023791438434273005,
0.09967754781246185,
-0.031007694080471992,
-0.0757906436920166,
0.06655744463205338,
-0.13743239641189575,
-0.043813399970531464,
0.06937135756015778,
-0.02519765868782997,
-0.04067762568593025,
-0.08... | 0.006243 |
.. SPDX-License-Identifier: GPL-2.0 .. \_kernelparameters: The kernel's command-line parameters ==================================== The following is a consolidated list of the kernel parameters as implemented by the \_\_setup(), early\_param(), core\_param() and module\_param() macros and sorted into English Dictionar... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-parameters.rst | master | linux | [
-0.07409179210662842,
-0.05555528402328491,
-0.07403683662414551,
0.005655194167047739,
-0.02668136917054653,
-0.04935352876782417,
0.10043930262327194,
0.04648618772625923,
-0.029293615370988846,
-0.09197421371936798,
0.013256196863949299,
0.022946177050471306,
0.061961617320775986,
-0.01... | 0.106653 |
2^50, and 2^60 bytes respectively. Such letter suffixes can also be entirely omitted. Kernel Build Options -------------------- The parameters listed below are only valid if certain kernel build options were enabled and if respective hardware is present. This list should be kept in alphabetical order. The text in squar... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/kernel-parameters.rst | master | linux | [
-0.009324642829596996,
-0.008814315311610699,
-0.018716752529144287,
0.0035724348854273558,
0.008110450580716133,
-0.04124690219759941,
0.013853747397661209,
0.11158009618520737,
-0.07387392222881317,
-0.06718652695417404,
0.029628785327076912,
-0.0496954619884491,
0.00905076414346695,
-0.... | 0.098684 |
Explaining the "No working init found." boot hang message ========================================================= :Authors: Andreas Mohr Cristian Souza This document provides some high-level reasons for failure (listed roughly in order of execution) to load the init binary. 1) \*\*Unable to mount root FS\*\*: Set "de... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/init.rst | master | linux | [
-0.0442521832883358,
-0.047174833714962006,
-0.024148428812623024,
0.020039858296513557,
0.1208738386631012,
-0.06873343884944916,
-0.03527877479791641,
0.11025728285312653,
-0.07747039198875427,
0.0019067837856709957,
0.057709578424692154,
-0.07357597351074219,
-0.021170074120163918,
0.02... | 0.07851 |
Software cursor for VGA ======================= by Pavel Machek and Martin Mares Linux now has some ability to manipulate cursor appearance. Normally, you can set the size of hardware cursor. You can now play a few new tricks: you can make your cursor look like a non-blinking red block, make it inverse background of th... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/vga-softcursor.rst | master | linux | [
-0.09767329692840576,
0.01384434662759304,
-0.0003015715046785772,
-0.056176140904426575,
-0.03813083469867706,
-0.007836295291781425,
0.030131448060274124,
-0.02144179493188858,
-0.010750385001301765,
-0.033423617482185364,
-0.03230789676308632,
-0.02588036097586155,
-0.02994447946548462,
... | 0.051364 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) .. [see the bottom of this file for redistribution information] ====================== Bisecting a regression ====================== This document describes how to use a ``git bisect`` to find the source code change that broke something -- for example when some functi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-bisect.rst | master | linux | [
-0.03224865719676018,
-0.03254558518528938,
-0.02410465106368065,
0.007588882930576801,
0.13150335848331451,
-0.08188706636428833,
0.05457284674048424,
0.02671675570309162,
0.021735774353146553,
-0.04368877783417702,
0.014231993816792965,
0.07575718313455582,
-0.013556402176618576,
-0.0663... | 0.113363 |
bisect log`` to print the status: it will show how many steps remain or mention the result of the bisection. \* Recommended complementary task: put the bisection log and the current .config file aside for the bug report; furthermore tell Git to reset the sources to the state before the bisection:: git bisect log > ~/bi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-bisect.rst | master | linux | [
-0.0002698562457226217,
-0.02660338021814823,
0.06951349973678589,
0.054115958511829376,
0.03505019098520279,
-0.09422200918197632,
0.019167518243193626,
-0.0006472708773799241,
0.03752078115940094,
0.007251841947436333,
0.0599246546626091,
-0.023934923112392426,
0.03148423507809639,
-0.01... | 0.036283 |
content of this RST file as found in the Linux kernel sources is available under CC-BY-4.0, as versions of this text that were processed (for example by the kernel's build system) might contain content taken from files which use a more restrictive license. | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-bisect.rst | master | linux | [
-0.043208856135606766,
0.017122698947787285,
-0.11501511931419373,
-0.008150745183229446,
0.1616557091474533,
0.018924009054899216,
-0.017139079049229622,
0.08952217549085617,
0.02163770981132984,
-0.025063881650567055,
0.06528864800930023,
0.09367328137159348,
-0.056087251752614975,
-0.00... | 0.157749 |
.. SPDX-License-Identifier: GPL-2.0 ==================================== File system Monitoring with fanotify ==================================== File system Error Reporting =========================== Fanotify supports the FAN\_FS\_ERROR event type for file system-wide error reporting. It is meant to be used by file ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/filesystem-monitoring.rst | master | linux | [
-0.04932565614581108,
-0.019965434446930885,
-0.01972413994371891,
0.0509948655962944,
0.09034214913845062,
-0.06811250746250153,
0.10166910290718079,
0.033785730600357056,
0.06737656891345978,
0.017997510731220245,
-0.028079966083168983,
-0.005373822059482336,
0.05141094699501991,
-0.0161... | 0.194262 |
=============================== Numa policy hit/miss statistics =============================== /sys/devices/system/node/node\*/numastat All units are pages. Hugepages have separate counters. The numa\_hit, numa\_miss and numa\_foreign counters reflect how well processes are able to allocate memory from nodes they pref... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/numastat.rst | master | linux | [
0.021256232634186745,
-0.033603474497795105,
-0.061420515179634094,
0.0408966951072216,
0.0168034415692091,
0.00005529496047529392,
-0.00752253457903862,
0.037739429622888565,
0.05074607580900192,
0.0647708848118782,
0.0053014191798865795,
-0.027609821408987045,
0.07816912233829498,
-0.072... | 0.324336 |
========================================== LDM - Logical Disk Manager (Dynamic Disks) ========================================== :Author: Originally Written by FlatCap - Richard Russon . :Last Updated: Anton Altaparmakov on 30 March 2007 for Windows Vista. Overview -------- Windows 2000, XP, and Vista use a new partiti... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/ldm.rst | master | linux | [
0.004990150686353445,
-0.02406046912074089,
0.0031603355892002583,
0.03206132352352142,
-0.0379246361553669,
-0.054314035922288895,
0.01535091269761324,
0.06889773160219193,
-0.050100360065698624,
-0.019240044057369232,
-0.061812497675418854,
0.0063020591624081135,
0.020504245534539223,
0.... | 0.067301 |
is a dummy MSDOS partition filling the whole disk. You won't be able to mount any of the volumes on the disk. Booting ------- If you enable LDM support, then lilo is capable of booting from any of the discovered partitions. However, grub does not understand the LDM partitioning and cannot boot from a Dynamic Disk. More... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/ldm.rst | master | linux | [
-0.007071979809552431,
-0.07031163573265076,
0.017083389684557915,
0.028801485896110535,
0.015670141205191612,
-0.05011916533112526,
0.02525375597178936,
0.0588504783809185,
-0.07268769294023514,
0.002296446356922388,
-0.002924282569438219,
-0.037935368716716766,
-0.029054950922727585,
-0.... | -0.043494 |
=============================================================== Softlockup detector and hardlockup detector (aka nmi\_watchdog) =============================================================== The Linux kernel can act as a watchdog to detect both soft and hard lockups. A 'softlockup' is defined as a bug that causes the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/lockup-watchdogs.rst | master | linux | [
-0.09781092405319214,
-0.08940722793340683,
-0.05728606507182121,
0.02515675500035286,
0.11634933203458786,
-0.06845900416374207,
0.0254313163459301,
0.03201211243867874,
0.011728914454579353,
-0.032435789704322815,
0.054360806941986084,
0.01722603850066662,
-0.009321887977421284,
-0.01921... | 0.191468 |
cores means that when those cores do enter the kernel, by default we will not be able to detect if they lock up. However, allowing the watchdog to continue to run on the housekeeping (non-tickless) cores means that we will continue to detect lockups properly on those cores. In either case, the set of cores excluded fro... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/lockup-watchdogs.rst | master | linux | [
-0.03026348352432251,
0.004023067653179169,
-0.04219554737210274,
0.06649353355169296,
0.13450482487678528,
0.015253125689923763,
-0.029355157166719437,
-0.03865322843194008,
-0.016435325145721436,
0.006248671095818281,
0.03891468793153763,
0.02051437832415104,
-0.005904010962694883,
-0.04... | 0.122506 |
.. SPDX-License-Identifier: GPL-2.0 The Android binderfs Filesystem =============================== Android binderfs is a filesystem for the Android binder IPC mechanism. It allows to dynamically add and remove binder devices at runtime. Binder devices located in a new binderfs instance are independent of binder device... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/binderfs.rst | master | linux | [
-0.07692188769578934,
-0.06356273591518402,
0.0017760106129571795,
-0.030454404652118683,
0.02226744405925274,
-0.023635271936655045,
0.0029874525498598814,
-0.01605931669473648,
0.0635838508605957,
-0.05428539589047432,
0.04473225027322769,
0.03275514021515846,
0.07506740093231201,
-0.019... | -0.085433 |
============================ A block layer cache (bcache) ============================ Say you've got a big slow raid 6, and an ssd or three. Wouldn't it be nice if you could use them as cache... Hence bcache. The bcache wiki can be found at: https://bcache.evilpiepirate.org This is the git repository of bcache-tools: ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
-0.03247779235243797,
0.01932819001376629,
-0.05895422026515007,
-0.03644772991538048,
-0.05257514864206314,
-0.08165261149406433,
-0.014179215766489506,
-0.003763254266232252,
0.0024052157532423735,
-0.0075495271012187,
-0.08778794854879379,
0.027107223868370056,
-0.031193917617201805,
-0... | 0.074491 |
'ATTACHING' section below. The devices show up as:: /dev/bcache As well as (with udev):: /dev/bcache/by-uuid/ /dev/bcache/by-label/ To get started:: mkfs.ext4 /dev/bcache0 mount /dev/bcache0 /mnt You can control bcache devices through sysfs at /sys/block/bcache/bcache . You can also control them through /sys/fs//bcache... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
-0.002927185036242008,
-0.03581990674138069,
-0.026369387283921242,
-0.0514848455786705,
-0.05146333575248718,
-0.05717064440250397,
0.030390629544854164,
0.03655274212360382,
-0.03686242550611496,
0.03681612387299538,
0.02548300102353096,
-0.016914844512939453,
0.007155003026127815,
-0.03... | 0.038811 |
running in writeback mode. B) Bcache does not find its cache:: host:/sys/block/md5/bcache# echo 0226553a-37cf-41d5-b3ce-8b1e944543a8 > attach [ 1933.455082] bcache: bch\_cached\_dev\_attach() Couldn't find uuid for md5 in set [ 1933.478179] bcache: \_\_cached\_dev\_store() Can't attach 0226553a-37cf-41d5-b3ce-8b1e94454... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
-0.020554760470986366,
0.00274518015794456,
-0.012835417874157429,
-0.041438207030296326,
-0.008954785764217377,
-0.04384702816605568,
-0.002126094186678529,
-0.02430180087685585,
-0.026569882407784462,
0.014406581409275532,
-0.04216450825333595,
-0.05466992035508156,
0.0036417075898498297,
... | -0.020661 |
2) But if your backing device is gone, this won't work:: host:/sys/block/bcache0# cd bcache bash: cd: bcache: No such file or directory In this case, you may have to unregister the dmcrypt block device that references this bcache to free it up:: host:~# dmsetup remove oldds1 bcache: bcache\_device\_free() bcache0 stopp... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
-0.06976368278265,
0.04388250410556793,
-0.014973417855799198,
-0.06622402369976044,
0.007422104477882385,
-0.07967472821474075,
0.03522373363375664,
0.02810068428516388,
0.018707895651459694,
0.016565382480621338,
-0.008466871455311775,
0.00508131692185998,
-0.0004106144479010254,
-0.0720... | -0.027235 |
the cache device, and gradually throttles traffic if the latency exceeds a threshold (it does this by cranking down the sequential bypass). You can disable this if you need to by setting the thresholds to 0:: # echo 0 > /sys/fs/bcache//congested\_read\_threshold\_us # echo 0 > /sys/fs/bcache//congested\_write\_threshol... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
0.029624732211232185,
-0.000337348465109244,
0.034129783511161804,
0.026563584804534912,
-0.06627093255519867,
-0.09289940446615219,
0.026185903698205948,
-0.023737451061606407,
0.014532632194459438,
0.0632837787270546,
-0.02950054034590721,
0.024422602728009224,
-0.04101012274622917,
-0.0... | 0.06562 |
corrupted. stop Write to this file to shut down the bcache device and close the backing device. writeback\_delay When dirty data is written to the cache and it previously did not contain any, waits some number of seconds before initiating writeback. Defaults to 30. writeback\_percent If nonzero, bcache tries to keep ar... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
-0.02494795061647892,
0.010646657086908817,
-0.043088268488645554,
-0.012540880590677261,
-0.012155932374298573,
-0.11473957449197769,
-0.008355220779776573,
0.025456933304667473,
-0.001047259895130992,
0.044437769800424576,
-0.006774476263672113,
0.057287830859422684,
-0.011359584517776966,... | 0.071994 |
be flushed. Sysfs - cache set internal ~~~~~~~~~~~~~~~~~~~~~~~~~~ This directory also exposes timings for a number of internal operations, with separate files for average duration, average frequency, last occurrence and max duration: garbage collection, btree read, btree node sorts and btree splits. active\_journal\_en... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bcache.rst | master | linux | [
0.009017270989716053,
-0.01687806099653244,
-0.01531908567994833,
0.043711915612220764,
0.008479616604745388,
-0.11368122696876526,
0.03150241822004318,
-0.00846191681921482,
0.011774868704378605,
0.0700119212269783,
0.004923379048705101,
0.043743737041950226,
-0.004954752512276173,
-0.099... | 0.112837 |
.. SPDX-License-Identifier: GPL-2.0 ABI testing symbols =================== Documents interfaces that are felt to be stable, as the main development of this interface has been completed. The interface can be changed to add new features, but the current interface will not break by doing this, unless grave errors or secu... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/abi-testing.rst | master | linux | [
-0.08903151750564575,
-0.035374440252780914,
-0.007010476663708687,
0.029224935919046402,
0.038140393793582916,
-0.10046996921300888,
0.022359231486916542,
-0.04407215490937233,
-0.010228532366454601,
-0.0562104657292366,
0.021746713668107986,
0.04874315485358238,
-0.016054989770054817,
-0... | 0.176845 |
Ramoops oops/panic logger ========================= Sergiu Iordache Updated: 10 Feb 2021 Introduction ------------ Ramoops is an oops/panic logger that writes its logs to RAM before the system crashes. It works by logging oopses and panics in a circular buffer. Ramoops needs a system with persistent RAM so that the con... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/ramoops.rst | master | linux | [
0.026386816054582596,
0.01852416805922985,
-0.01985720731317997,
0.033491987735033035,
0.01418172474950552,
-0.09431961178779602,
0.015548566356301308,
0.08266337215900421,
0.02895618975162506,
0.048771362751722336,
-0.052679773420095444,
0.07899226248264313,
0.029064485803246498,
-0.05992... | 0.13046 |
struct ramoops\_platform\_data ramoops\_data = { .mem\_size = <...>, .mem\_address = <...>, .mem\_type = <...>, .record\_size = <...>, .max\_reason = <...>, .ecc = <...>, }; static struct platform\_device ramoops\_dev = { .name = "ramoops", .dev = { .platform\_data = &ramoops\_data, }, }; [... inside a function ...] in... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/ramoops.rst | master | linux | [
0.0304570272564888,
0.03302060812711716,
-0.06650509685277939,
-0.0038479242939502,
0.006114285439252853,
-0.09519399702548981,
0.020241709426045418,
0.11831480264663696,
-0.05619359016418457,
-0.03407866507768631,
0.06727813184261322,
-0.05097421258687973,
0.017801867797970772,
-0.0547836... | 0.146615 |
================= The EFI Boot Stub ================= On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade as a PE/COFF image, thereby convincing EFI firmware loaders to load it as an EFI executable. The code that modifies the bzImage header, along with the EFI-specific entry point that the firmware loa... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/efi-stub.rst | master | linux | [
-0.05605404078960419,
0.0755852535367012,
0.0239487923681736,
-0.013526900671422482,
0.06594673544168472,
-0.025536108762025833,
0.05244974419474602,
0.0734492614865303,
-0.027325892820954323,
-0.028699927031993866,
0.023666543886065483,
-0.026602916419506073,
0.05108904093503952,
-0.03383... | 0.163108 |
runtime data provided by firmware will be lost. The dtb= option should only be used either as a debug tool, or as a last resort when a device tree is not provided in the EFI CONFIGURATION TABLE. "dtb=" is processed in the same manner as the "initrd=" option that is described above. | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/efi-stub.rst | master | linux | [
-0.01875094138085842,
0.004830261692404747,
0.010430390015244484,
0.037140652537345886,
0.054421164095401764,
-0.014253560453653336,
0.05066283419728279,
0.06348715722560883,
-0.06820863485336304,
-0.03678205981850624,
0.012852350249886513,
-0.02914860099554062,
-0.009610378183424473,
-0.0... | 0.09525 |
============= btmrvl driver ============= All commands are used via debugfs interface. Set/get driver configurations ============================= Path: /debug/btmrvl/config/ gpiogap=[n], hscfgcmd These commands are used to configure the host sleep parameters:: bit 8:0 -- Gap bit 16:8 -- GPIO where GPIO is the pin numb... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/btmrvl.rst | master | linux | [
-0.024309666827321053,
0.03642253205180168,
-0.027050020173192024,
0.06695163995027542,
0.07881215214729309,
-0.005305747967213392,
-0.039429664611816406,
0.022002264857292175,
-0.041844889521598816,
-0.025235487148165703,
-0.008715611882507801,
-0.10640037804841995,
-0.05614003539085388,
... | 0.11212 |
========= Using UFS ========= mount -t ufs -o ufstype=type\_of\_ufs device dir UFS Options =========== ufstype=type\_of\_ufs UFS is a file system widely used in different operating systems. The problem are differences among implementations. Features of some implementations are undocumented, so its hard to recognize typ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/ufs.rst | master | linux | [
-0.005769556388258934,
0.0215595755726099,
-0.01666966825723648,
0.017197709530591965,
0.07436512410640717,
-0.07175233215093613,
-0.01814587600529194,
0.049027811735868454,
0.015948891639709473,
-0.02808101288974285,
0.015905648469924927,
0.006512483116239309,
0.0025861558970063925,
0.037... | 0.071589 |
=========================================== How CPU topology info is exported via sysfs =========================================== CPU topology info is exported via sysfs. Items (attributes) are similar to /proc/cpuinfo output of some architectures. They reside in /sys/devices/system/cpu/cpuX/topology/. Please refer t... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/cputopology.rst | master | linux | [
-0.012634397484362125,
-0.0645771250128746,
-0.12423043698072433,
0.011617181822657585,
0.04459630325436592,
-0.06263871490955353,
0.01954961195588112,
-0.002128361724317074,
-0.05120769888162613,
-0.033955223858356476,
0.03218645602464676,
-0.060292523354291916,
-0.008674997836351395,
-0.... | 0.1487 |
.. \_admin\_devices: Linux allocated devices (4.x+ version) ====================================== This list is the Linux Device List, the official registry of allocated device numbers and ``/dev`` directory nodes for the Linux operating system. The version of this document at lanana.org is no longer maintained. This v... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/devices.rst | master | linux | [
-0.000716889975592494,
-0.06418445706367493,
-0.07023440301418304,
-0.036737244576215744,
0.004992300178855658,
-0.02506932243704796,
0.0038384234067052603,
0.08464161306619644,
-0.029852578416466713,
-0.005710546858608723,
0.11477072536945343,
0.04533776640892029,
-0.008093860931694508,
-... | 0.1183 |
hard Alternate SCSI CD-ROM name =============== =============== =============== =============================== Locally defined links +++++++++++++++++++++ The following links may be established locally to conform to the configuration of the system. This is merely a tabulation of existing practice, and does not constit... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/devices.rst | master | linux | [
-0.06884369254112244,
-0.05362320691347122,
-0.02926013059914112,
-0.14393390715122223,
-0.03967168182134628,
0.022321350872516632,
0.018742868676781654,
0.11261224001646042,
-0.15494748950004578,
-0.01688833348453045,
0.1416824460029602,
0.0028908774256706238,
0.006532736588269472,
0.0209... | 0.168007 |
port primary (``tty\*``, not ``cu\*``) device, depending on the configuration of the system. Serial ports ++++++++++++ Serial ports are RS-232 serial ports and any device which simulates one, either in hardware (such as internal modems) or in software (such as the ISDN driver.) Under Linux, each serial ports has two de... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/devices.rst | master | linux | [
-0.039425890892744064,
-0.06057391315698624,
-0.01484714262187481,
-0.08108655363321304,
-0.04406137019395828,
-0.039483487606048584,
-0.05338523909449577,
0.08085361868143082,
0.03857211396098137,
-0.055533360689878464,
0.10623415559530258,
0.03098541684448719,
0.009289879351854324,
0.016... | 0.183457 |
integers (``/dev/pts/#`` in our notation). This removes the problem of exhausting the namespace and enables the kernel to automatically create the device nodes for the slaves on demand using the "devpts" filesystem. | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/devices.rst | master | linux | [
-0.0719415545463562,
-0.007104604505002499,
-0.07974902540445328,
-0.010903917253017426,
0.009863472543656826,
-0.08483712375164032,
0.023330718278884888,
0.011264463886618614,
0.018218088895082474,
0.03517881780862808,
0.055445097386837006,
0.02218681573867798,
0.06929325312376022,
-0.044... | 0.221873 |
======================================= Real Time Clock (RTC) Drivers for Linux ======================================= When Linux developers talk about a "Real Time Clock", they usually mean something that tracks wall clock time and is battery backed so that it works even with system power off. Such clocks will normal... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/rtc.rst | master | linux | [
-0.04969586059451103,
-0.013268492184579372,
-0.11598294228315353,
0.05069529637694359,
0.09236399084329605,
-0.006226269993931055,
-0.022520702332258224,
0.045309942215681076,
0.038614679127931595,
-0.05474720150232315,
-0.03168817609548569,
-0.02195644937455654,
-0.12546837329864502,
0.0... | 0.057049 |
by doing a read(2) or a select(2) on /dev/rtc -- either will block/stop the user process until the next interrupt is received. This is useful for things like reasonably high frequency data acquisition where one doesn't want to burn up 100% CPU by polling gettimeofday etc. etc. At high frequencies, or under high loads, ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/rtc.rst | master | linux | [
0.023037925362586975,
-0.0228764396160841,
-0.11600690335035324,
0.04618866741657257,
-0.028617657721042633,
-0.0732966735959053,
0.05017499253153801,
0.042540766298770905,
0.008428875356912613,
0.0765889510512352,
-0.04491628706455231,
0.03804850950837135,
-0.0883062481880188,
-0.05895048... | 0.054459 |
on newer PCs through ACPI. The new framework also removes the "one RTC per system" restriction. For example, maybe the low-power battery-backed RTC is a discrete I2C chip, but a high functionality RTC is integrated into the SOC. That system might read the system clock from the discrete RTC, but use the integrated one f... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/rtc.rst | master | linux | [
-0.06863722205162048,
-0.002904157852753997,
-0.0989592969417572,
0.03141215071082115,
0.09172610938549042,
0.007692978251725435,
0.04307011887431145,
0.04259806126356125,
0.05261402577161789,
0.02752278931438923,
-0.007804227992892265,
0.05582244321703911,
-0.06227521598339081,
0.05574152... | 0.16944 |
======================= RapidIO Subsystem Guide ======================= :Author: Matt Porter Introduction ============ RapidIO is a high speed switched fabric interconnect with features aimed at the embedded market. RapidIO provides support for memory-mapped I/O as well as message-based transactions over the switched f... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/rapidio.rst | master | linux | [
-0.00821983627974987,
-0.02849387377500534,
-0.05154518783092499,
0.0045488085597753525,
-0.02548287808895111,
-0.011228611692786217,
0.025189485400915146,
0.03071407973766327,
-0.10786707699298859,
-0.07286570966243744,
0.07743175327777863,
0.0008655612473376095,
-0.012477736920118332,
-0... | 0.260649 |
=========================================== IBM's Journaled File System (JFS) for Linux =========================================== JFS Homepage: http://jfs.sourceforge.net/ The following mount options are supported: (\*) == default iocharset=name Character set to use for converting from Unicode to ASCII. The default i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/jfs.rst | master | linux | [
-0.008986962027847767,
-0.019853530451655388,
-0.06550119817256927,
-0.02796422317624092,
-0.020644603297114372,
-0.019442427903413773,
-0.03801260143518448,
0.07172439247369766,
-0.011715464293956757,
-0.05568266287446022,
0.010316155850887299,
-0.027230750769376755,
-0.011622646823525429,
... | 0.056625 |
.. SPDX-License-Identifier: GPL-2.0 pstore block oops/panic logger ============================== Introduction ------------ pstore block (pstore/blk) is an oops/panic logger that writes its logs to a block device and non-block device before the system crashes. You can get these log files by mounting pstore filesystem l... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/pstore-blk.rst | master | linux | [
0.00026860355865210295,
0.02154763601720333,
-0.06646832078695297,
0.016355132684111595,
0.029674680903553963,
-0.030154114589095116,
0.05990666523575783,
0.11268701404333115,
-0.006572413258254528,
-0.0494229756295681,
0.022356703877449036,
0.030376190319657326,
0.001816217671148479,
-0.0... | 0.083574 |
console front-end. All log of console will be appended to the chunk. On reboot the contents are available in \*/sys/fs/pstore/console-pstore-blk-0\*. ftrace\_size ~~~~~~~~~~~ The chunk size in KB for ftrace front-end. It \*\*MUST\*\* be a multiple of 4. It's optional if you do not care about the ftrace log. Similar to ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/pstore-blk.rst | master | linux | [
0.052740465849637985,
0.009262439794838428,
-0.09302346408367157,
0.035354986786842346,
0.11205470561981201,
-0.03220051899552345,
-0.03907126188278198,
0.10728146880865097,
0.05473899841308594,
0.018626084551215172,
-0.03311515226960182,
0.05409051105380058,
-0.11737482994794846,
-0.05452... | 0.091362 |
Can \*\*NOT\*\* take any lock. There is no other task, nor any shared resource; you are safe to break all locks. #. Just use CPU to transfer. Do not use DMA to transfer unless you are sure that DMA will not keep lock. #. Control registers directly. Please control registers directly rather than use Linux kernel resource... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/pstore-blk.rst | master | linux | [
-0.026202823966741562,
-0.006793294567614794,
-0.1074552983045578,
-0.023559605702757835,
0.02815163880586624,
-0.003973002545535564,
0.029315847903490067,
0.11565634608268738,
-0.016155358403921127,
-0.00021486844343598932,
-0.0028005612548440695,
0.01981079764664173,
0.010565982200205326,
... | 0.070083 |
Bug hunting =========== Kernel bug reports often come with a stack dump like the one below:: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 28102 at kernel/module.c:1108 module\_put+0x57/0x70 Modules linked in: dvb\_usb\_gp8psk(-) dvb\_usb dvb\_core nvidia\_drm(PO) nvidia\_modeset(PO) snd\_hda\_codec\_hdmi s... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-hunting.rst | master | linux | [
-0.04794005677103996,
-0.033394262194633484,
-0.0363394096493721,
0.01622462086379528,
0.08780264854431152,
-0.058613311499357224,
-0.06338420510292053,
0.06318376958370209,
-0.026186587288975716,
-0.03161333128809929,
0.019473159685730934,
-0.019034676253795624,
-0.0556018091738224,
-0.02... | 0.095131 |
(2) Boot with a serial console (see :ref:`Documentation/admin-guide/serial-console.rst `), run a null modem to a second machine and capture the output there using your favourite communication program. Minicom works well. (3) Use Kdump (see Documentation/admin-guide/kdump/kdump.rst), extract the kernel ring buffer from ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-hunting.rst | master | linux | [
0.053746819496154785,
0.023697663098573685,
-0.03363989293575287,
-0.012204879894852638,
0.04252966493368149,
-0.06437170505523682,
-0.04602028429508209,
0.10694251209497452,
-0.05596167966723442,
0.006169595755636692,
0.06786463409662247,
0.001136881415732205,
-0.0174701027572155,
-0.0834... | 0.044833 |
00 00 8b ac 24 d0 00 00 00 8b 5d 08 <8b> 83 3c 01 00 00 89 44 24 14 8b 45 28 85 c0 89 44 24 18 0f 85 Put the bytes into a "foo.s" file like this: .text .globl foo foo: .byte .... /\* bytes from Code: part of OOPS dump \*/ Compile it with "gcc -c -o foo.o foo.s" then look at the output of "objdump --disassemble foo.o". ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-hunting.rst | master | linux | [
-0.06011517718434334,
0.06085589528083801,
-0.04165322706103325,
-0.00257422705180943,
-0.053554147481918335,
-0.08957590162754059,
0.07514280825853348,
0.050787150859832764,
-0.009413478896021843,
-0.0016665409784764051,
0.015875181183218956,
0.002140011405572295,
-0.022308390587568283,
-... | 0.131875 |
whatever reporting mechanism ``klogd`` is using. The protection fault message can be simply cut out of the message files and forwarded to the kernel developers. Two types of address resolution are performed by ``klogd``. The first is static translation and the second is dynamic translation. Static translation uses the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/bug-hunting.rst | master | linux | [
0.015077612362802029,
0.06252294778823853,
0.005581654608249664,
-0.052987292408943176,
0.029822474345564842,
0.013450976461172104,
0.03607790172100067,
0.05114906281232834,
0.03433658927679062,
0.03553282096982002,
0.02768743596971035,
0.03610140085220337,
0.046595245599746704,
-0.0127943... | 0.185791 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) .. [see the bottom of this file for redistribution information] Reporting regressions +++++++++++++++++++++ "\*We don't cause regressions\*" is the first rule of Linux kernel development; Linux founder and lead developer Linus Torvalds established it himself and ensur... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
-0.09312090277671814,
-0.05955798923969269,
-0.032365601509809494,
0.047221630811691284,
0.1409558206796646,
-0.00876346044242382,
-0.026680856943130493,
0.0651983916759491,
0.023537807166576385,
-0.0335867777466774,
0.011622416786849499,
0.10427975654602051,
0.005671370308846235,
0.001635... | 0.121734 |
first broken one. Ideally try to find the exact change causing the regression using a bisection, as explained below in more detail. \* Remember to let the Linux regressions mailing list (regressions@lists.linux.dev) know about your report: \* If you report the regression by mail, CC the regressions list. \* If you repo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
-0.03298299014568329,
-0.008747993968427181,
0.006846456788480282,
0.0994291827082634,
0.1536654531955719,
-0.060251668095588684,
-0.1011485904455185,
0.05581466481089592,
-0.011623091995716095,
0.03406940773129463,
0.01541552972048521,
-0.0037461535539478064,
-0.04382915049791336,
-0.0185... | 0.020483 |
the culprit relatively quickly. If it's hard or time-consuming to reliably reproduce the issue, consider teaming up with other affected users to narrow down the search range together. Who can I ask for advice when it comes to regressions? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Send a mail to the regress... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
0.02190917544066906,
-0.05236237123608589,
-0.013599022291600704,
0.09359592944383621,
0.12778645753860474,
-0.041747912764549255,
-0.07909494638442993,
0.008211241103708744,
0.03647296875715256,
-0.035746555775403976,
0.05309435725212097,
-0.008774906396865845,
-0.017041994258761406,
-0.0... | -0.009076 |
percent slow-down in a micro-benchmark thus is unlikely to qualify as regression, unless it also influences the results of a broad benchmark by more than one percent. If in doubt, ask for advice. Is it a regression, if an external kernel module breaks when updating Linux? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
0.02320246584713459,
-0.05894101411104202,
-0.007035709451884031,
0.018027465790510178,
0.13561278581619263,
-0.06612398475408554,
-0.020842676982283592,
0.0747600719332695,
-0.00933865550905466,
0.01874963566660881,
0.02821209281682968,
0.046936407685279846,
0.008451983332633972,
0.006340... | 0.11992 |
might be in their and everyone else's interest to lettings things pass. Especially if there is an easy way to circumvent the regression somehow, for example by updating some software or using a kernel parameter created just for this purpose. Does the regression rule apply for code in the staging tree as well? ~~~~~~~~~... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
-0.0593857616186142,
-0.013352232053875923,
0.045437198132276535,
0.05837249383330345,
0.09356740117073059,
-0.059509169310331345,
-0.039068277925252914,
0.005688309669494629,
-0.0090536093339324,
0.04349341616034508,
0.03708527237176895,
0.049036070704460144,
0.03658917546272278,
-0.02968... | 0.10253 |
work, with the long term goal to automate regression tracking as much as possible for everyone involved. Regzbot works by watching for replies to reports of tracked regressions. Additionally, it's looking out for posted or committed patches referencing such reports with "Link:" tags; replies to such patch postings are ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-regressions.rst | master | linux | [
-0.09945939481258392,
-0.07264939695596695,
-0.06823773682117462,
0.07960615307092667,
0.12156213819980621,
-0.04343831166625023,
-0.007097932975739241,
0.02947034128010273,
-0.12057095021009445,
0.014480401761829853,
-0.045389268547296524,
-0.003532517934218049,
0.03952379524707794,
-0.00... | 0.054944 |
Java(tm) Binary Kernel Support for Linux v1.03 ---------------------------------------------- Linux beats them ALL! While all other OS's are TALKING about direct support of Java Binaries in the OS, Linux is doing it! You can execute Java applications and Java Applets just like any other program after you have done the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/java.rst | master | linux | [
-0.023431740701198578,
-0.037343885749578476,
-0.03589138388633728,
-0.08881966024637222,
0.01236323919147253,
-0.05734766274690628,
-0.027183547616004944,
0.13413116335868835,
-0.06950565427541733,
-0.06655367463827133,
0.008039631880819798,
-0.09143688529729843,
-0.0423940047621727,
-0.0... | 0.149648 |
$FQCLASS should be in a file called $GOODNAME" exit 1 fi if ! echo $CLASSPATH | grep -q "^\(.\*:\)\*$CLASSBASE\(:.\*\)\*"; then # class is not in CLASSPATH, so prepend dir of class to CLASSPATH if [ -z "${CLASSPATH}" ] ; then export CLASSPATH=$CLASSBASE else export CLASSPATH=$CLASSBASE:$CLASSPATH fi fi shift /usr/bin/j... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/java.rst | master | linux | [
-0.054718926548957825,
0.0740053653717041,
-0.044653892517089844,
0.0011890396708622575,
0.044628653675317764,
0.052958711981773376,
0.07191529124975204,
0.024521689862012863,
-0.02945087105035782,
0.009713460691273212,
0.006541740614920855,
-0.0549519881606102,
0.01837000995874405,
-0.035... | 0.070829 |
program, argv[1]); if(fseek(classfile, 8, SEEK\_SET)) /\* skip magic and version numbers \*/ seek\_error(); cp\_count = read\_16(classfile); pool = calloc(cp\_count, sizeof(long)); if(!pool) error("%s: Out of memory for constant pool\n", program); for(i = 1; i < cp\_count; ++i) skip\_constant(classfile, &i); if(fseek(c... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/java.rst | master | linux | [
-0.01653493195772171,
0.047229938209056854,
-0.07383961975574493,
-0.04635709151625633,
0.0024715845938771963,
-0.06695948541164398,
0.035170767456293106,
0.06669006496667862,
-0.05155956372618675,
-0.031747736036777496,
0.0022805342450737953,
-0.03814287111163139,
-0.005594075191766024,
-... | 0.069867 |
.. include:: ================================= Video Mode Selection Support 2.13 ================================= :Copyright: |copy| 1995--1999 Martin Mares, Intro ~~~~~ This small document describes the "Video Mode Selection" feature which allows the use of various special video modes supported by the video BIOS. Due... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/svga.rst | master | linux | [
0.01753082126379013,
-0.03158566355705261,
0.017010873183608055,
-0.047211144119501114,
0.08354415744543076,
0.0021230594720691442,
-0.03317836672067642,
0.03353738784790039,
-0.027500318363308907,
-0.08727286756038666,
0.02911331318318844,
-0.0163278728723526,
-0.13621290028095245,
0.0533... | 0.021923 |
a few basic modes and some VESA modes. In case your chipset has been detected, some chipset-specific modes are shown as well (some of these might be missing or unusable on your machine as different BIOSes are often shipped with the same card and the mode numbers depend purely on the VGA BIOS). The modes displayed on th... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/svga.rst | master | linux | [
0.005225827917456627,
-0.003576315473765135,
-0.015863265842199326,
-0.0042106639593839645,
0.06153986230492592,
-0.02155175618827343,
0.03824620693922043,
-0.011453276500105858,
-0.04192165657877922,
-0.0959412232041359,
0.0466526634991169,
-0.0720948874950409,
-0.1169515997171402,
0.0686... | 0.055654 |
to 132x43 etc. This is the only fully portable way to refer to a non-standard mode, but it relies on the mode being found and displayed on the menu (remember that mode scanning is not done automatically). 0xff00 to 0xffff - aliases for backward compatibility: 0xffff equivalent to 0x0f00 (standard 80x25) 0xfffe equivale... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/svga.rst | master | linux | [
0.027888301759958267,
0.08599726855754852,
-0.030253609642386436,
-0.03045363910496235,
-0.027026619762182236,
-0.05945011228322983,
-0.0609431266784668,
0.062025513499975204,
-0.04744983837008476,
-0.09812488406896591,
0.03178131952881813,
0.021043624728918076,
-0.037095505744218826,
0.01... | 0.043537 |
to work with 1.3.74 kernel. 2.4 (18-Mar-96) Added patches by Hans Lermen fixing a memory overwrite problem with some boot loaders. Memory management rewritten to reflect these changes. Unfortunately, screen contents retaining works only with some loaders now. Added a Tseng 132x60 mode. 2.5 (19-Mar-96) Fixed a VESA mode... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/svga.rst | master | linux | [
-0.06277183443307877,
0.018602803349494934,
0.004926234018057585,
-0.01872071623802185,
0.05735666677355766,
-0.0648517906665802,
-0.029541710391640663,
0.04908899962902069,
-0.07698008418083191,
-0.01149712409824133,
-0.01391100324690342,
0.013567272573709488,
-0.09451892971992493,
0.0477... | 0.090469 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) .. [see the bottom of this file for redistribution information] =========================================== How to quickly build a trimmed Linux kernel =========================================== This guide explains how to swiftly build Linux kernels that are ideal fo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.03295725956559181,
0.007146316114813089,
-0.01686864160001278,
-0.017657041549682617,
0.045911405235528946,
-0.13080324232578278,
0.03220925107598305,
0.04665226861834526,
-0.05497542768716812,
-0.05869312584400177,
0.0021264825481921434,
-0.030935419723391533,
-0.04400089383125305,
-0.... | 0.071769 |
things rolling again. .. Note: if you see this note, you are reading the text's source file. You might want to switch to a rendered version, as it makes it a lot easier to quickly look something up in the reference section and afterwards jump back to where you left off. Find a the latest rendered version here: https://... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.05256732925772667,
0.034708693623542786,
-0.0004644392756745219,
0.027891110628843307,
0.1127304807305336,
0.03289416804909706,
-0.017684826627373695,
-0.005028744228184223,
-0.014802186749875546,
-0.0752888023853302,
0.044218696653842926,
0.012677354738116264,
-0.08756758272647858,
-0.... | -0.015072 |
versions like ``v6.1.5`` work just the same, if you added the appropriate stable/longterm branch as described. [:ref:`details`] .. \_patching\_sbs: \* In case you want to apply a kernel patch, do so now. Often a command like this will do the trick:: patch -p1 < ../proposed-fix.patch If the ``-p1`` is actually needed, d... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.031632594764232635,
-0.05212454870343208,
0.04261353984475136,
-0.008965762332081795,
0.05637103319168091,
-0.01402145717293024,
-0.0568864643573761,
-0.0601365901529789,
-0.07654492557048798,
0.022156253457069397,
-0.0016004900680854917,
0.012030065059661865,
-0.0846371203660965,
-0.11... | -0.022772 |
[:ref:`details`] .. \_install\_sbs: \* Now install your kernel:: command -v installkernel && sudo make modules\_install install Often all left for you to do afterwards is a ``reboot``, as many commodity Linux distributions will then create an initramfs (also known as initrd) and an entry for your kernel in your bootloa... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
0.0006866464391350746,
-0.08708590269088745,
-0.017686503008008003,
0.021971795707941055,
0.06313443183898926,
-0.023419231176376343,
-0.022938024252653122,
0.04119875282049179,
-0.017106743529438972,
-0.05111664906144142,
0.03469708561897278,
-0.008497919887304306,
-0.10285826027393341,
-... | 0.073876 |
to improve this document further, which is in everybody's interest, as it will enable more people to master the task described here. Reference section for the step-by-step guide ============================================ This section holds additional information for each of the steps in the above guide. .. \_backup: ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.12458302080631256,
0.03045276366174221,
0.06277276575565338,
0.008365645073354244,
0.12411888688802719,
0.01928083784878254,
0.020937815308570862,
0.06977742165327072,
-0.10249906033277512,
-0.023964153602719307,
0.04324902221560478,
0.06694745272397995,
0.02320016734302044,
-0.06912733... | 0.053746 |
which many distributions enable in their kernel configuration for x86 machines. Sometimes you will need tools for compression formats like bzip2, gzip, lz4, lzma, lzo, xz, or zstd as well. You might need additional libraries and their development headers in case you perform tasks not covered in this guide. For example,... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.03170214965939522,
0.00827919039875269,
-0.02330618165433407,
-0.039000291377305984,
0.08493861556053162,
-0.037781842052936554,
-0.08191525936126709,
0.1032540574669838,
-0.04280991479754448,
-0.010005112737417221,
0.014559765346348286,
-0.06221513822674751,
-0.004353112541139126,
-0.0... | -0.001172 |
happen automatically when using ``--shallow-since=`` or ``--depth=``. \* Be warned, when deepening your clone you might encounter an error like 'fatal: error in object: unshallow cafecaca0c0dacafecaca0c0dacafecaca0c0da'. In that case run ``git repack -d`` and try again`` \* In case you want to revert changes from a cer... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.048210978507995605,
-0.036446187645196915,
0.07550325989723206,
0.013445182703435421,
0.026855645701289177,
-0.09440368413925171,
-0.033823996782302856,
0.0008248052909038961,
0.054262351244688034,
0.012842315249145031,
0.012361153960227966,
-0.02719103917479515,
0.027679499238729477,
-... | -0.020779 |
stick to the latest mainline release (say v6.1) before its successor's first pre-release (v6.2-rc1) is out. That is because compiler errors and other problems are more likely to occur during this time, as mainline then is in its 'merge window': a usually two week long phase, in which the bulk of the changes for the nex... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.07880783826112747,
-0.10457687824964523,
0.074091836810112,
0.018908653408288956,
0.08637676388025284,
-0.08552847057580948,
-0.13005755841732025,
0.062041375786066055,
-0.009360219351947308,
-0.02082820050418377,
0.07351476699113846,
0.010283077135682106,
-0.06168034300208092,
-0.14185... | -0.009524 |
is not the intended one, simply store it as '~/linux/.config' before using these make targets. \* Unexpected things might happen if you try to use a config file prepared for one kernel (say v6.0) on an older generation (say v5.15). In that case you might want to use a configuration as base which your distribution utili... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
0.008680326864123344,
-0.013675655238330364,
-0.05850428342819214,
-0.006244880147278309,
0.09120377153158188,
-0.018507830798625946,
-0.05683830380439758,
0.026584086939692497,
-0.06615596264600754,
-0.07765902578830719,
0.11381709575653076,
-0.03167692944407463,
-0.03815269097685814,
-0.... | -0.050285 |
want or have to adjust some kernel configuration options. .. \_configmods\_debugsymbols: Debug symbols ~~~~~~~~~~~~~ \*Evaluate how you want to handle debug symbols.\* [:ref:`...`] Most users do not need to care about this, it's often fine to leave everything as it is; but you should take a closer look at this, if you ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
0.001669449731707573,
-0.02061539702117443,
-0.0038926517590880394,
0.05099340155720711,
0.0986688956618309,
-0.11538690328598022,
-0.05788533389568329,
0.09066444635391235,
-0.028911497443914413,
-0.018154975026845932,
0.104454405605793,
-0.020928602665662766,
-0.008886829949915409,
-0.07... | 0.0219 |
quickly; other times though the problem lies in the code and can only be fixed by a developer. A close examination of the failure messages coupled with some research on the internet will often tell you which of the two it is. To perform such an investigation, restart the build process like this:: make V=1 The ``V=1`` a... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
-0.036814332008361816,
0.0021637091413140297,
0.0017744171200320125,
0.009636154398322105,
0.07058680802583694,
-0.11731239408254623,
-0.07641635090112686,
0.0023694930132478476,
-0.04707193002104759,
-0.02364964783191681,
0.035369712859392166,
-0.07309100031852722,
-0.042065754532814026,
... | 0.081313 |
an ``installkernel`` executable. Many commodity Linux distributions ship such a kernel installer in ``/sbin/`` that does everything needed, hence there is nothing left for you except rebooting. But some distributions contain an installkernel that does only part of the job -- and a few lack it completely and leave all t... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
0.011854630894958973,
-0.027926838025450706,
0.0024009239859879017,
-0.03910064324736595,
0.0807575061917305,
-0.04892145097255707,
-0.02200309932231903,
0.079073965549469,
-0.025311870500445366,
-0.030087897554039955,
0.11568142473697662,
0.06411928683519363,
-0.024380836635828018,
-0.062... | 0.109732 |
The other place is /boot/, where typically one to five files will be placed during installation of a kernel. All of them usually contain the release name in their file name, but how many files and their name depends somewhat on your distribution's installkernel executable (:ref:`see above `) and its initramfs generator... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/quickly-build-trimmed-linux.rst | master | linux | [
0.013734390027821064,
0.06194966286420822,
0.026792339980602264,
-0.038275230675935745,
0.08871882408857346,
-0.03557934984564781,
0.017335722222924232,
0.020395642146468163,
0.010523426346480846,
-0.03212491050362587,
0.10572629421949387,
0.042796991765499115,
-0.0027922289445996284,
-0.0... | 0.053122 |
Mono(tm) Binary Kernel Support for Linux ----------------------------------------- To configure Linux to automatically execute Mono-based .NET binaries (in the form of .exe files) without the need to use the mono CLR wrapper, you can use the BINFMT\_MISC kernel support. This will allow you to execute Mono-based .NET bi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/mono.rst | master | linux | [
-0.01399637944996357,
-0.04390673711895943,
-0.019137661904096603,
-0.0751950815320015,
-0.03631709888577461,
-0.048517871648073196,
-0.026180438697338104,
0.12063952535390854,
-0.009593711234629154,
0.02418169379234314,
-0.01294703222811222,
-0.13239426910877228,
-0.05191479250788689,
0.0... | 0.0939 |
.. SPDX-License-Identifier: GPL-2.0 ====================== USB4 and Thunderbolt ====================== USB4 is the public specification based on Thunderbolt 3 protocol with some differences at the register level among other things. Connection manager is an entity running on the host router (host controller) responsible... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/thunderbolt.rst | master | linux | [
0.025846591219305992,
-0.05807885155081749,
0.009308143518865108,
0.016279373317956924,
0.025824561715126038,
0.009625297039747238,
0.04503360763192177,
-0.030915172770619392,
0.034762829542160034,
-0.07405775040388107,
-0.0021636842284351587,
0.03408628702163696,
-0.02001277357339859,
-0.... | 0.069978 |
Available in some USB4 systems. The current security level can be read from ``/sys/bus/thunderbolt/devices/domainX/security`` where ``domainX`` is the Thunderbolt domain the host controller manages. There is typically one domain per Thunderbolt host controller. If the security level reads as ``user`` or ``secure`` the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/thunderbolt.rst | master | linux | [
0.025572823360562325,
-0.0677046999335289,
-0.022312454879283905,
-0.0038367165252566338,
0.056868672370910645,
0.011185521259903908,
0.05975951626896858,
0.03329877182841301,
0.012527172453701496,
-0.04277724772691727,
-0.0020627512130886316,
0.00331604084931314,
0.04543329030275345,
-0.0... | -0.011824 |
NVMe or similar involved, there is a risk for data loss if the filesystem on that storage is not properly shut down. You have been warned! DMA protection utilizing IOMMU ------------------------------ Recent systems from 2018 and forward with Thunderbolt ports may natively support IOMMU. This means that Thunderbolt sec... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/thunderbolt.rst | master | linux | [
0.030956467613577843,
0.03661063686013222,
0.03789680823683739,
0.07118748128414154,
0.030618587508797646,
-0.021008528769016266,
0.028465840965509415,
0.06993643939495087,
-0.028960861265659332,
-0.02614210918545723,
-0.05220001935958862,
0.04375931993126869,
-0.009418034926056862,
-0.020... | 0.055545 |
the non-active parts of NVM of the host or device. Example on how to update Intel NUC6i7KYK (Skull Canyon) Thunderbolt controller NVM:: # dd if=KYK\_TBT\_FW\_0018.bin of=/sys/bus/thunderbolt/devices/0-0/nvm\_non\_active0/nvmem Once the operation completes we can trigger NVM authentication and upgrade process as follows... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/thunderbolt.rst | master | linux | [
-0.014767768792808056,
-0.024939417839050293,
0.027021583169698715,
0.005719073582440615,
0.06494905054569244,
-0.06278388947248459,
-0.00466342456638813,
-0.055269770324230194,
-0.02046324498951435,
-0.005132921971380711,
0.08588636666536331,
-0.04580126330256462,
-0.0020272587426006794,
... | 0.063002 |
Thunderbolt technology allows software communication between two hosts connected by a Thunderbolt cable. It is possible to tunnel any kind of traffic over a Thunderbolt link but currently we only support Apple ThunderboltIP protocol. If the other host is running Windows or macOS, the only thing you need to do is to con... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/thunderbolt.rst | master | linux | [
-0.003657178021967411,
0.000868772272951901,
0.0011828856077045202,
0.0713651105761528,
-0.003277676412835717,
0.013541270978748798,
0.05686580017209053,
0.03053993359208107,
-0.007667172234505415,
-0.03261697664856911,
-0.050280388444662094,
-0.039692364633083344,
-0.023775776848196983,
-... | -0.028719 |
.. \_perf\_security: Perf events and tool security ============================= Overview -------- Usage of Performance Counters for Linux (perf\_events) [1]\_ , [2]\_ , [3]\_ can impose a considerable risk of leaking sensitive data accessed by monitored processes. The data leakage is possible both in scenarios of dire... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/perf-security.rst | master | linux | [
-0.010344191454350948,
-0.018707795068621635,
-0.13440191745758057,
-0.013077662326395512,
0.02043132111430168,
-0.054146721959114075,
0.06620719283819199,
0.07760817557573318,
0.06956032663583755,
0.016100766137242317,
0.015029998496174812,
-0.015765173360705376,
0.020232778042554855,
-0.... | 0.165499 |
process using perf\_events system call API contain denial records of acquiring both CAP\_PERFMON and CAP\_SYS\_ADMIN capabilities then providing the process with CAP\_PERFMON capability singly is recommended as the preferred secure approach to resolve double access denial logging related to usage of performance monitor... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/perf-security.rst | master | linux | [
-0.012238577008247375,
-0.03899681195616722,
-0.08139124512672424,
-0.06160177290439606,
0.08826757222414017,
-0.06238820031285286,
0.09670320898294449,
0.04013170674443245,
0.08587033301591873,
0.06653160601854324,
0.0003800160775426775,
0.005704850889742374,
-0.02769428677856922,
0.03878... | 0.19954 |
perf\_users group only. In order to create such environment: 1. Create shell script that uses capsh utility [16]\_ to assign CAP\_PERFMON and other required capabilities into ambient capability set of the shell process, lock the process security bits after enabling SECBIT\_NO\_SETUID\_FIXUP, SECBIT\_NOROOT and SECBIT\_... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/perf-security.rst | master | linux | [
0.012392440810799599,
-0.026898901909589767,
-0.08200764656066895,
-0.0729355439543724,
-0.005817926488816738,
-0.06141447648406029,
0.07886117696762085,
0.07640520483255386,
0.002377226483076811,
0.04307103529572487,
-0.01584833674132824,
-0.1168045774102211,
0.005155893508344889,
0.04939... | 0.08541 |
by the number of monitored CPUs. Memory allocation +++++++++++++++++ The amount of memory available to user processes for capturing performance monitoring data is governed by the perf\_event\_mlock\_kb [2]\_ setting. This perf\_event specific resource setting defines overall per-cpu limits of memory allowed for mapping... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/perf-security.rst | master | linux | [
0.047285936772823334,
-0.007220791187137365,
-0.09367170929908752,
-0.019667934626340866,
0.013943496160209179,
-0.04280257225036621,
0.07477355003356934,
0.052343010902404785,
0.026997176930308342,
-0.01616937853395939,
-0.022069592028856277,
0.002408035797998309,
0.021077478304505348,
-0... | 0.178811 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.