Home
last modified time | relevance | path

Searched refs:recursive (Results 1 – 25 of 30) sorted by relevance

12

/linux/scripts/kconfig/tests/err_recursive_dep/
H A Dexpected_stderr1 error: recursive dependency detected!
4 subsection "Kconfig recursive dependency limitations"
6 error: recursive dependency detected!
9 subsection "Kconfig recursive dependency limitations"
11 error: recursive dependency detected!
15 subsection "Kconfig recursive dependency limitations"
17 error: recursive dependency detected!
21 subsection "Kconfig recursive dependency limitations"
23 error: recursive dependency detected!
27 subsection "Kconfig recursive dependency limitations"
[all …]
/linux/Documentation/locking/
H A Dlockdep-design.rst405 spin_lock() or write_lock()), non-recursive readers (i.e. shared lockers, like
406 down_read()) and recursive readers (recursive shared lockers, like rcu_read_lock()).
410 r: stands for non-recursive readers.
411 R: stands for recursive readers.
412 S: stands for all readers (non-recursive + recursive), as both are shared lockers.
413 N: stands for writers and non-recursive readers, as both are not recursive.
421 While non-recursive readers will cause a self deadlock if trying to acquire inside
424 The difference between recursive readers and non-recursive readers is because:
425 recursive readers get blocked only by a write lock *holder*, while non-recursive
435 Task A gets the reader (no matter whether recursive or non-recursive) on X via
[all …]
H A Dpi-futex.rst18 recursive locking, etc.
/linux/Documentation/kbuild/
H A DKconfig.recursion-issue-011 # Simple Kconfig recursive issue
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
34 # the "recursive dependency detected" error.
41 # implications of this recursive issue where the solution is perhaps not so
43 # CORE also consist of a solution to this recursive problem.
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
H A DKconfig.recursion-issue-021 # Cumulative Kconfig recursive issue
8 # The recursive limitations with Kconfig has some non intuitive implications on
10 # of the recursive limitation is that drivers cannot negate features from other
47 mainmenu "Simple example to demo cumulative kconfig recursive dependency implication"
/linux/tools/perf/ui/browsers/
H A Dannotate-data.c447 bool recursive) in annotated_data_browser__fold() argument
453 if (entry->folded && !recursive) in annotated_data_browser__fold()
456 if (recursive) { in annotated_data_browser__fold()
467 bool recursive) in annotated_data_browser__unfold() argument
474 if (!entry->folded && !recursive) in annotated_data_browser__unfold()
479 if (recursive) in annotated_data_browser__unfold()
490 bool recursive) in annotated_data_browser__toggle_fold() argument
503 annotated_data_browser__unfold(browser, curr, recursive); in annotated_data_browser__toggle_fold()
505 annotated_data_browser__fold(browser, curr, recursive); in annotated_data_browser__toggle_fold()
/linux/scripts/gdb/linux/
H A Ddevice.py90 def _show_device(dev, level=0, recursive=False): argument
92 if recursive:
94 _show_device(child, level + 1, recursive)
147 _show_device(dev, level=0, recursive=True)
/linux/samples/vfs/
H A Dmountinfo.c216 bool recursive = false; in main() local
230 recursive = true; in main()
264 if (!recursive) in main()
/linux/tools/testing/selftests/cgroup/
H A Dmemcg_protection.m54 % recursive protection
/linux/Documentation/admin-guide/sysctl/
H A Duser.rst33 This recursive counting of created objects ensures that creating a
/linux/security/tomoyo/
H A Dutil.c867 goto recursive; in tomoyo_path_matches_pattern2()
883 recursive: in tomoyo_path_matches_pattern2()
/linux/lib/
H A DKconfig.kgdb38 difficult to inadvertently provoke recursive trap handling.
H A DKconfig360 modify. The algorithms are non-recursive, and the trees are highly
/linux/include/sound/
H A Dhda_codec.h361 hda_nid_t nid, int recursive);
/linux/sound/hda/common/
H A Dcodec.c265 hda_nid_t nid, int recursive) in snd_hda_get_conn_index() argument
274 if (!recursive) in snd_hda_get_conn_index()
276 if (recursive > 10) { in snd_hda_get_conn_index()
280 recursive++; in snd_hda_get_conn_index()
285 if (snd_hda_get_conn_index(codec, conn[i], nid, recursive) >= 0) in snd_hda_get_conn_index()
/linux/tools/net/ynl/pyynl/
H A Dynl_gen_c.py661 return self.family.pure_nested_structs[self.nested_attrs].recursive
969 self.recursive = False
1333 if self.pure_nested_structs[nested].recursive:
1449 struct.recursive = True
1461 if not child.recursive:
3598 if struct.recursive:
/linux/Documentation/trace/
H A Dkprobes.rst130 For example, if the function is non-recursive and is called with a
132 non-recursive and can never relinquish the CPU (e.g., via a semaphore
298 (trapping) such functions can cause a recursive trap (e.g. double
/linux/Documentation/admin-guide/cgroup-v1/
H A Dblkio-controller.rst247 same information as their non-recursive counterparts but
/linux/Documentation/driver-api/rapidio/
H A Drapidio.rst254 The enumeration process traverses the network using a recursive depth-first
/linux/Documentation/admin-guide/device-mapper/
H A Dthin-provisioning.rst17 recursive snapshots (snapshots of snapshots of snapshots ...). The
/linux/Documentation/core-api/
H A Dassoc_array.rst495 slot in that parent that points to it. None-recursive iteration uses these to
H A Dcpu_hotplug.rst312 example of a recursive fail due to a failed offline operation: ::
/linux/Documentation/kernel-hacking/
H A Dlocking.rst118 Neither type of lock is recursive: see
879 (spinlocks, rwlocks and mutexes are not recursive in Linux). This is
/linux/fs/
H A Dnamespace.c3060 static struct file *open_detached_copy(struct path *path, bool recursive) in open_detached_copy() argument
3086 mnt = __do_loopback(path, recursive); in open_detached_copy()
/linux/Documentation/process/
H A Dbackporting.rst400 git cherry-pick -strategy=recursive -Xrename-threshold=30

12