Searched full:itself (Results 1 – 25 of 2443) sorted by relevance
12345678910>>...98
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-hypervisor-xen | 22 "self" The guest can profile itself
23 "hv" The guest can profile itself and, if it is
25 "all" The guest can profile itself, the hypervisor
|
| D | sysfs-firmware-dmi-entries | 10 The kernel itself does not rely on the majority of the
45 assigned entry handles as the kernel itself makes no
58 entry itself. Note that this is _not the
|
| /Linux-v5.15/drivers/xen/ |
| D | xen-front-pgdir-shbuf.c | 97 * shared by the frontend itself) or map the provided granted
118 * shared by the frontend itself) or unmap the provided granted
163 * Get the number of pages the page directory consumes itself.
180 /* Only for pages the page directory consumes itself. */ in backend_calc_num_grefs()
193 * Number of pages the page directory consumes itself in guest_calc_num_grefs()
277 * so buf->num_grefs has number of pages in the page directory itself. in backend_map()
334 * page directory itself.
350 /* Fill only grefs for the page directory itself. */ in backend_fill_page_dir()
378 * granted for the page directory itself. in guest_fill_page_dir()
|
| /Linux-v5.15/scripts/kconfig/tests/err_recursive_dep/ |
| D | Kconfig | 3 # depends on itself
9 # select itself
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | uncore-power.json | 10 …event that tracks the number of cores that are in C0. It can be used by itself to get the average…
21 …event that tracks the number of cores that are in C3. It can be used by itself to get the average…
32 …event that tracks the number of cores that are in C6. It can be used by itself to get the average…
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-power.json | 10 …event that tracks the number of cores that are in C0. It can be used by itself to get the average…
21 …event that tracks the number of cores that are in C3. It can be used by itself to get the average…
32 …event that tracks the number of cores that are in C6. It can be used by itself to get the average…
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | uncore-power.json | 10 …event that tracks the number of cores that are in C0. It can be used by itself to get the average…
21 …event that tracks the number of cores that are in C3. It can be used by itself to get the average…
32 …event that tracks the number of cores that are in C6. It can be used by itself to get the average…
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 7 by the device itself. The full description of the bitfields
21 by the device itself. The full description of the bitfields
|
| /Linux-v5.15/include/linux/ |
| D | posix-clock.h | 99 * A clock driver calls this function to register itself with the
112 * A clock driver calls this function to remove itself from the clock
113 * device subsystem. The posix_clock itself will remain (in an
|
| /Linux-v5.15/drivers/hwmon/occ/ |
| D | Kconfig | 15 the P8, not the POWER processor itself. Communications with the OCC are
30 the P9, not the POWER processor itself. Communications with the OCC are
|
| /Linux-v5.15/drivers/char/ |
| D | nwbutton.h | 10 #ifdef __NWBUTTON_C /* Actually compiling the driver itself */
34 #else /* Not compiling the driver itself */
|
| /Linux-v5.15/Documentation/security/tpm/ |
| D | tpm_ftpm_tee.rst | 19 implemented in firmware. The driver itself doesn't contain much logic and is
22 The firmware itself is based on the following paper:
|
| /Linux-v5.15/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 5 used by the firmware itself for configuring the port. From the linux
21 The node contains a number of other properties that are used by the FW itself
|
| /Linux-v5.15/Documentation/filesystems/ext4/ |
| D | verity.rst | 12 stored after the end of the file data itself, in the following format:
38 is encrypted as well as the data itself.
|
| /Linux-v5.15/drivers/staging/media/atomisp/include/hmm/ |
| D | hmm_bo.h | 201 * object but will not free the buffer object itself, as the
204 * of the buffer object itself manually. below example shows
225 * or by ISP driver itself.
234 * or by ISP driver itself.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | dell_rbu.rst | 16 update itself with the image downloaded in to the memory.
90 to the data file as is without any change to the BIOS image itself.
126 the BIOS knows about the new image downloaded and it updates itself.
|
| /Linux-v5.15/lib/kunit/ |
| D | Kconfig | 32 the KUnit test framework itself; the tests are both written using
44 itself, lib/kunit/example-test.c, for more information. This option
|
| /Linux-v5.15/fs/nfsd/ |
| D | filecache.h | 12 * The fsnotify_mark is itself refcounted, but that's not sufficient to tell us
28 * hold a reference to the inode by itself, so the nf_inode pointer should
|
| /Linux-v5.15/include/xen/ |
| D | xen-front-pgdir-shbuf.h | 30 * of grant references for the page directory itself as grant
39 * Number of pages for the shared buffer itself (excluding the page
|
| /Linux-v5.15/Documentation/networking/ |
| D | x25.rst | 11 implement LAPB on the card itself, and unintelligent ones that simply do
17 layer of the Linux kernel and therefore it did not concern itself with
|
| /Linux-v5.15/include/xen/interface/ |
| D | xenpmu.h | 47 * itself and Xen
49 * everyone: itself, the hypervisor and the guests.
|
| /Linux-v5.15/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 35 irq-flags state, and complains loudly (and turns itself off) if the
48 turn itself off. I.e. the lock validator will still be reliable. There
|
| /Linux-v5.15/fs/ocfs2/cluster/ |
| D | tcp_internal.h | 96 * itself if a connect attempt fails and so can be self-arming.
133 * still on the nn and will call ensure_shutdown itself.. this
138 * sc and rearm itself.
|
| /Linux-v5.15/Documentation/userspace-api/ |
| D | landlock.rst | 108 The current thread is now ready to sandbox itself with the ruleset.
131 Each time a thread enforces a ruleset on itself, it updates its Landlock domain
134 thread can then safely add more constraints to itself with a new enforced
176 Landlock rules to itself, but they will not be automatically applied to other
180 When a thread sandboxes itself, we have the guarantee that the related security
|
| D | no_new_privs.rst | 52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
63 dangerous than chroot by itself.
|
12345678910>>...98
