Home
last modified time | relevance | path

Searched +refs:is +refs:pre +refs:merge (Results 1 – 23 of 23) sorted by relevance

/linux-6.15/drivers/gpu/drm/i915/
DTODO.txt4 - For discrete memory manager, merge enough dg1 to be able to refactor it to
15 1. Land a modern pre-bound uapi like VM_BIND
18 the bo and vm, plus some lru locks is all that needed. No complex rcu,
20 This is the matching task on the vm side compared to ttm/dma_resv on the
24 How-to-dma_fence is core and drivers really shouldn't build their own world
27 removed if dri-devel consensus is that it's not a good idea. Once that's done
/linux-6.15/tools/perf/Documentation/
Dperf-sched.txt40 Tasks with the same command name are merged and the merge count is
41 given within (), However if -p option is used, pid is mentioned.
47 via perf sched record. (this is done by starting up mockup threads
87 Input file name. (default: perf.data unless stdin is a fifo)
136 time is printed and is represented by '*-' for the given
138 ('-' indicates other tasks while '.' is idle).
207 have the format seconds.microseconds. If start is not given (i.e., time
208 string is ',x.y') then analysis starts at the beginning of the file. If
209 stop time is not given (i.e, time string is 'x.y,') then analysis goes
225 --pre-migrations::
[all …]
Dperf-stat.txt39 - a raw PMU event in the form of rN where N is a hexadecimal value
52 'percore' is a event qualifier that sums up the event counts for both
66 'uncore_' is also ignored when performing this match.
109 The default path is /sys/fs/bpf/perf_attr_map.
124 system-wide collection from all CPUs (default if no target is specified)
151 In per-thread mode, this option is ignored. The -a option is still necessary
152 to activate system-wide monitoring. Default is to count on all CPUs.
192 monitor only in the container (cgroup) called "name". This option is available only
195 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
196 to first event, second cgroup to second event and so on. It is possible to provide
[all …]
/linux-6.15/tools/power/pm-graph/config/
Dexample.cfg4 # This is the configuration file for sleepgraph. It contains
7 # and kprobes. It is run like this
102 # merge loops of the same call if each is less than maxgap apart (def: 100us)
106 # merge loops of the same call if each is less than maxlen in length (def: 5ms)
138 # pre-expand the callgraph data in the html output (default: disabled)
/linux-6.15/Documentation/mm/
Dslub.rst5 The basic philosophy of SLUB is very different from SLAB. SLAB
7 slab caches. SLUB always includes full debugging but it is off by default.
32 Parameters may be given to ``slab_debug``. If none is specified then full
33 debugging is enabled. Format:
43 blocks of options delimited by ';'. The last of "all slabs" blocks is applied
58 - Switch all debugging off (useful if the kernel is
107 If the file contains 1, the option is enabled, 0 means disabled. The debug
117 failslab file is writable, so writing 1 or 0 will enable or disable
118 the option at runtime. Write returns -EINVAL if cache is an alias.
125 If no debug options are specified then SLUB may merge similar slabs together
[all …]
/linux-6.15/tools/power/pm-graph/
DREADME49 This tool suite is designed to assist kernel and OS developers in optimizing
52 and will capture dmesg and ftrace data. This data is transformed into a set of
61 - runs with python2 or python3, choice is made by /usr/bin/python link
97 (kernel/pre-3.15/enable_trace_events_suspend_resume.patch)
98 (kernel/pre-3.15/enable_trace_events_device_pm_callback.patch)
112 There is a patch which does this for kernel v3.8.0:
113 (kernel/pre-3.11-rc2/enable_ftrace_in_suspendresume.patch)
160 timeline. This is useful in discovering dependent threads to get a better
161 idea of what each device is waiting for. For instance, the scsi_eh thread,
162 a.k.a. scsi resume error handler, is what each SATA disk device waits for
[all …]
/linux-6.15/Documentation/userspace-api/
Dlandlock.rst13 The goal of Landlock is to enable restriction of ambient rights (e.g. global
15 is a stackable LSM, it makes it possible to create safe security sandboxes as
17 This kind of sandbox is expected to help mitigate the security impact of bugs or
21 We can quickly make sure that Landlock is enabled in the running system by
26 If Landlock is not currently supported, we need to
33 perform. A set of rules is aggregated in a ruleset, which can then restrict
39 For these rules, the object is a file hierarchy,
44 For these rules, the object is a TCP port,
56 The ruleset then needs to handle both these kinds of actions. This is
90 on, it is safer to follow a best-effort security approach. Indeed, we
[all …]
/linux-6.15/Documentation/virt/uml/
Duser_mode_linux_howto_v2.rst15 User Mode Linux is the first Open Source virtualization platform (first
18 How is UML Different from a VM using Virtualization package X?
28 is not a single real device in sight. It is 100% artificial or if
34 packages is that there is a distinct difference between the way the UML
36 The UML kernel is just a process running on Linux - same as any other
39 The UML userspace, however, is a bit different. The Linux kernel on the
41 on a UML instance is trying to do and making the UML kernel handle all
43 This is different from other virtualization packages which do not make any
53 * If User Mode Linux kernel crashes, your host kernel is still fine. It
54 is not accelerated in any way (vhost, kvm, etc) and it is not trying to
[all …]
/linux-6.15/Documentation/admin-guide/
Dreporting-issues.rst27 <https://kernel.org/>`_. If the issue is present there, send a report.
32 check if backporting is in the works or was discarded; if it's neither, ask
47 Once the report is out, answer any questions that come up and help where you
57 everyone else there is this section. It is more detailed and uses a
64 early if an issue that looks like a Linux kernel problem is actually caused by
119 situations; during the merge window that actually might be even the best
134 details, and at the same time is easy to read and understand for others
141 * If your problem is a regression, try to narrow down when the issue was
154 thing a descriptive title or subject that yet again is shorter. Then you're
157 special care which is explained in 'Special handling for high priority
[all …]
Dquickly-build-trimmed-linux.rst15 section below: it contains a step-by-step guide, which is more detailed, but
57 Compiling your own Linux kernel is easy in principle. There are various ways to
58 do it. Which of them actually work and is the best depends on the circumstances.
62 goal is to cover everything typically needed on mainstream Linux distributions
65 The described approach is great for testing purposes, for example to try a
94 quickest and easiest way to achieve this on commodity x86 systems is to
130 partially cloning the Linux stable git repository. This is called a shallow
143 If you want to access recent mainline releases and pre-releases, deepen you
157 is ideal for checking whether developers already fixed an issue::
163 pre-release like ``v6.2-rc1`` will work, too. Stable or longterm versions
[all …]
Dkernel-parameters.txt4 By default, unaccepted memory is accepted lazily to
6 some runtime overhead until all memory is eventually
7 accepted. In most cases the overhead is negligible.
62 This option is useful for developers to identify the
88 Some values produce so much output that the system is
100 is denied; legacy drivers trying to access reserved
102 lax: access to resources claimed by ACPI is allowed;
104 will bind successfully but a warning message is logged.
110 By default, this is disabled due to x86 early mapping
142 This feature is enabled by default.
[all …]
/linux-6.15/Documentation/process/
Dadding-syscalls.rst15 The first thing to consider when adding a new system call is whether one of
38 relevant filesystem is mounted, which might not always be the case (e.g.
40 debugfs, as this is not considered a 'production' interface to userspace.
41 - If the operation is specific to a particular file or file descriptor, then
43 :manpage:`fcntl(2)` is a multiplexing system call that hides a lot of complexity, so
44 this option is best for when the new function is closely analogous to
45 existing :manpage:`fcntl(2)` functionality, or the new functionality is very simple
47 - If the operation is specific to a particular task or process, then an
49 with :manpage:`fcntl(2)`, this system call is a complicated multiplexor so
50 is best reserved for near-analogs of existing ``prctl()`` commands or
[all …]
Dhandling-regressions.rst27 is optional, but recommended):
132 All this is expected from you and important when it comes to regression, as
136 these tools is regzbot, which heavily relies on the "Closes:" tags to associate
152 should be less than two. And it ought to be just a few days, if the issue is
175 On timing once the culprit of a regression is known:
177 * Aim to mainline a fix within two or three days, if the issue is severe or
183 backport); if the culprit became known early during a week and is simple to
188 regression is something people can live with easily for a while -- like a
192 merge window, except when the fix is extraordinarily risky or when the
213 from the mailing list: he is totally fine with that for uncontroversial
[all …]
/linux-6.15/Documentation/kbuild/
Dmakefiles.rst21 The top Makefile is responsible for building two major products: vmlinux
62 This document is aimed towards normal developers and arch developers.
76 Section `Goal definitions`_ is a quick intro; further chapters provide
92 This tells kbuild that there is one object in that directory, named
95 If foo.o shall be built as a module, the variable obj-m is used.
96 Therefore the following pattern is often used:
103 If CONFIG_FOO is neither y nor m, then the file will not be compiled
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
115 This is a thin archive without a symbol table. It will be later
118 The order of files in $(obj-y) is significant. Duplicates in
[all …]
/linux-6.15/Documentation/filesystems/iomap/
Doperations.rst23 Buffered I/O is the default file I/O path in Linux.
81 If this function is not provided, iomap will call
89 If this function is not provided, iomap will ``folio_unlock`` and
99 If a file's space mapping data are mutable, it is possible that the
115 ``->iomap_valid`` function to decide if the mapping is still valid.
116 If the mapping is not valid, the mapping will be sampled again.
121 A simple validation cookie implementation is a sequence counter.
125 If the value in the cookie is found to be different to the value
126 the filesystem holds when the mapping is passed back to
139 If the fsblock size matches the size of a pagecache folio, it is assumed
[all …]
/linux-6.15/arch/arm/boot/dts/nvidia/
Dtegra20-asus-tf101.dts33 * pre-existing /chosen node to be available to insert the
34 * command line and merge other ATAGS info.
663 /* LDO0 is not connected to anything */
963 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1224 * 1: external that is connected to the CPU's diode
1228 * zone is a simpler solution which prevents TF101 from
1230 * The CPU zone is intended to protect silicon from damage.
Dtegra30-asus-nexus7-grouper-common.dtsi27 * pre-existing /chosen node to be available to insert the
28 * command line and merge other ATAGS info.
961 * SMB347 INOK input pin is connected to PMIC's
962 * ACOK output, which is fixed to ACTIVE_LOW as
963 * long as battery voltage is in a good range.
1062 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1242 * 1: external that is connected to the CPU's diode
1246 * zone is a simpler solution which prevents Nexus 7
1248 * The CPU zone is intended to protect silicon from damage.
Dtegra20-acer-a500-picasso.dts32 * pre-existing /chosen node to be available to insert the
33 * command line and merge other ATAGS info.
599 /* LDO0 is not connected to anything */
1195 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1205 * oscillator is used as a reference clock-source by the
1445 * 1: external that is connected to the CPU's diode
1449 * zone is a simpler solution which prevents A500 from
1451 * The CPU zone is intended to protect silicon from damage.
Dtegra30-asus-transformer-common.dtsi31 * pre-existing /chosen node to be available to insert the
32 * command line and merge other ATAGS info.
1234 /* VDD1 is not used by Transformers */
1298 /* LDO5 is not used by Transformers */
1489 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1699 * 1: external that is connected to the CPU's diode
1705 * tactile perspective. The CPU zone is intended to
Dtegra30-lg-x3.dtsi30 * pre-existing /chosen node to be available to insert the
31 * command line and merge other ATAGS info.
1461 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1732 * 1: external that is connected to the CPU's diode
1738 * tactile perspective. The CPU zone is intended to
Dtegra30-pegatron-chagall.dts35 * pre-existing /chosen node to be available to insert the
36 * command line and merge other ATAGS info.
1309 /* VDD1 is not used by Chagall */
2599 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
2780 * 1: external that is connected to the CPU's diode
2786 * perspective. The CPU zone is intended to protect
/linux-6.15/Documentation/
Dmemory-barriers.txt14 This document is not a specification; it is intentionally (for the sake of
15 brevity) and unintentionally (due to being human) incomplete. This document is
23 To repeat, this document is not a specification of what Linux expects from
26 The purpose of this document is twofold:
35 that, that architecture is incorrect.
37 Note also that it is possible that a barrier may be a no-op for an
136 abstract CPU, memory operation ordering is very relaxed, and a CPU may actually
189 There is an obvious address dependency here, as the value loaded into D depends
205 locations, but the order in which the control registers are accessed is very
270 WRITE_ONCE(). Without them, the compiler is within its rights to
[all …]
/linux-6.15/
DMAINTAINERS10 L: *Mailing list* that is relevant to this area
12 Supported: Someone is actually paid to look after this.
28 patches to the given subsystem. This is either an in-tree file,
32 Type is one of: git, hg, quilt, stgit, topgit
52 match occurs. When an N: match occurs, git log history is used
4022 T: git https://git.open-mesh.org/linux-merge.git
7088 F: scripts/sphinx-pre-install
7123 F: scripts/sphinx-pre-install
17358 M: YOKOTA Hiroshi <yokota@netlab.is.tsukuba.ac.jp>
17360 W: http://www.netlab.is.tsukuba.ac.jp/~yokota/izumi/ninja/
[all …]