| /Linux-v6.1/include/trace/events/ |
| D | cachefiles.h | 214 enum cachefiles_obj_ref_trace why),
216 TP_ARGS(object_debug_id, cookie_debug_id, usage, why),
222 __field(enum cachefiles_obj_ref_trace, why )
230 __entry->why = why;
235 __print_symbolic(__entry->why, cachefiles_obj_ref_traces))
327 enum fscache_why_object_killed why),
329 TP_ARGS(obj, ino, why),
335 __field(enum fscache_why_object_killed, why )
341 __entry->why = why;
346 __print_symbolic(__entry->why, cachefiles_obj_kill_traces))
[all …]
|
| D | fscache.h | 287 enum fscache_active_trace why),
289 TP_ARGS(cookie_debug_id, ref, n_active, n_accesses, why),
296 __field(enum fscache_active_trace, why )
304 __entry->why = why;
309 __print_symbolic(__entry->why, fscache_active_traces),
319 enum fscache_access_trace why),
321 TP_ARGS(cache_debug_id, ref, n_accesses, why),
327 __field(enum fscache_access_trace, why )
334 __entry->why = why;
339 __print_symbolic(__entry->why, fscache_access_traces),
[all …]
|
| D | rxrpc.h | 524 TP_PROTO(unsigned int call_nr, const char *why, u32 cid, u32 call_id,
527 TP_ARGS(call_nr, why, cid, call_id, seq, abort_code, error),
531 __array(char, why, 4 )
540 memcpy(__entry->why, why, 4);
552 __entry->abort_code, __entry->error, __entry->why)
582 TP_PROTO(struct rxrpc_call *call, enum rxrpc_transmit_trace why),
584 TP_ARGS(call, why),
588 __field(enum rxrpc_transmit_trace, why )
596 __entry->why = why;
604 __print_symbolic(__entry->why, rxrpc_transmit_traces),
[all …]
|
| /Linux-v6.1/fs/cachefiles/ |
| D | xattr.c | 100 enum cachefiles_coherency_trace why; in cachefiles_check_auxdata() local
120 why = cachefiles_coherency_check_xattr; in cachefiles_check_auxdata()
122 why = cachefiles_coherency_check_type; in cachefiles_check_auxdata()
124 why = cachefiles_coherency_check_aux; in cachefiles_check_auxdata()
126 why = cachefiles_coherency_check_objsize; in cachefiles_check_auxdata()
130 why = cachefiles_coherency_check_dirty; in cachefiles_check_auxdata()
132 why = cachefiles_coherency_check_ok; in cachefiles_check_auxdata()
137 buf->content, why); in cachefiles_check_auxdata()
239 enum cachefiles_coherency_trace why; in cachefiles_check_volume_xattr() local
262 why = cachefiles_coherency_vol_check_xattr; in cachefiles_check_volume_xattr()
[all …]
|
| D | io.c | 395 enum cachefiles_prepare_read_trace why; in cachefiles_prepare_read() local
412 why = cachefiles_trace_read_after_eof; in cachefiles_prepare_read()
418 why = cachefiles_trace_read_no_data; in cachefiles_prepare_read()
425 why = cachefiles_trace_read_no_file; in cachefiles_prepare_read()
443 why = cachefiles_trace_read_seek_nxio; in cachefiles_prepare_read()
448 why = cachefiles_trace_read_seek_error; in cachefiles_prepare_read()
453 why = cachefiles_trace_read_found_hole; in cachefiles_prepare_read()
460 why = cachefiles_trace_read_found_part; in cachefiles_prepare_read()
470 why = cachefiles_trace_read_seek_error; in cachefiles_prepare_read()
482 why = cachefiles_trace_read_have_data; in cachefiles_prepare_read()
[all …]
|
| D | interface.c | 52 enum cachefiles_obj_ref_trace why) in cachefiles_see_object() argument
55 refcount_read(&object->ref), why); in cachefiles_see_object()
62 enum cachefiles_obj_ref_trace why) in cachefiles_grab_object() argument
67 trace_cachefiles_ref(object->debug_id, object->cookie->debug_id, r, why); in cachefiles_grab_object()
75 enum cachefiles_obj_ref_trace why) in cachefiles_put_object() argument
84 trace_cachefiles_ref(object_debug_id, cookie_debug_id, r, why); in cachefiles_put_object()
|
| /Linux-v6.1/drivers/infiniband/core/ |
| D | uverbs_std_types.c | 43 enum rdma_remove_reason why, in uverbs_free_ah() argument
52 enum rdma_remove_reason why, in uverbs_free_flow() argument
72 enum rdma_remove_reason why, in uverbs_free_mw() argument
79 enum rdma_remove_reason why, in uverbs_free_rwq_ind_tbl() argument
103 enum rdma_remove_reason why, in uverbs_free_xrcd() argument
115 ret = ib_uverbs_dealloc_xrcd(uobject, xrcd, why, attrs); in uverbs_free_xrcd()
122 enum rdma_remove_reason why, in uverbs_free_pd() argument
159 enum rdma_remove_reason why) in uverbs_completion_event_file_destroy_uobj() argument
|
| D | uverbs_std_types_async_fd.c | 23 enum rdma_remove_reason why) in uverbs_async_event_destroy_uobj() argument
30 if (why == RDMA_REMOVE_DRIVER_REMOVE) in uverbs_async_event_destroy_uobj()
|
| /Linux-v6.1/fs/fscache/ |
| D | volume.c | 43 enum fscache_access_trace why) in __fscache_begin_volume_access() argument
51 n_accesses, why); in __fscache_begin_volume_access()
58 * @why: An indication of the circumstances of the access for tracing
80 * The datafile @cookie and the @why indicator are merely provided for tracing
85 enum fscache_access_trace why) in fscache_begin_volume_access() argument
89 __fscache_begin_volume_access(volume, cookie, why); in fscache_begin_volume_access()
101 * @why: An indication of the circumstances of the access for tracing
104 * @why indicator are merely provided for tracing purposes.
108 enum fscache_access_trace why) in fscache_end_volume_access() argument
116 n_accesses, why); in fscache_end_volume_access()
|
| D | cache.c | 267 * @why: An indication of the circumstances of the access for tracing
288 bool fscache_begin_cache_access(struct fscache_cache *cache, enum fscache_access_trace why) in fscache_begin_cache_access() argument
298 n_accesses, why); in fscache_begin_cache_access()
309 * @why: An indication of the circumstances of the access for tracing
311 * Unpin a cache after we've accessed it. The @why indicator is merely
314 void fscache_end_cache_access(struct fscache_cache *cache, enum fscache_access_trace why) in fscache_end_cache_access() argument
321 n_accesses, why); in fscache_end_cache_access()
|
| D | internal.h | 26 bool fscache_begin_cache_access(struct fscache_cache *cache, enum fscache_access_trace why);
27 void fscache_end_cache_access(struct fscache_cache *cache, enum fscache_access_trace why);
66 enum fscache_access_trace why);
152 enum fscache_access_trace why);
|
| /Linux-v6.1/fs/afs/ |
| D | dir_edit.c | 207 enum afs_edit_dir_reason why) in afs_edit_dir_add() argument
300 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_nospc, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
316 trace_afs_edit_dir(vnode, why, afs_edit_dir_create, b, slot, in afs_edit_dir_add()
351 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_inval, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
361 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_error, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
374 struct qstr *name, enum afs_edit_dir_reason why) in afs_edit_dir_remove() argument
440 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_noent, in afs_edit_dir_remove()
448 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete, b, slot, in afs_edit_dir_remove()
478 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_inval, in afs_edit_dir_remove()
489 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_error, in afs_edit_dir_remove()
|
| /Linux-v6.1/scripts/ |
| D | Kbuild.include | 96 echo ' $(call escsq,$($(quiet)cmd_$(1)))$(echo-why)';)
186 # why - tell why a target got built
205 why = \
222 echo-why = $(call escsq, $(strip $(why)))
|
| /Linux-v6.1/Documentation/RCU/ |
| D | UP.rst | 52 Why is it *not* legal to invoke synchronize_rcu() in this case?
100 Why can't synchronize_rcu() return immediately on UP systems running
106 Why is it *not* legal to invoke synchronize_rcu() in this case?
136 Why can't synchronize_rcu() return immediately on UP systems
|
| D | rcu.rst | 19 - Why would anyone want to use RCU?
50 thing at a time, why should I wait for a grace period?
68 - Why the name "RCU"?
|
| /Linux-v6.1/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 123 merge, say *why* the merge is being done. For a lower-level tree, "why" is
149 Why is that? Back merges will muddy the development history of your own
158 sure to document *why* it was required in the commit message. As always,
190 as always, in such situations, the merge commit should explain why the
226 arisen and be prepared to explain why something abnormal needs to be done.
|
| D | pull-requests.rst | 51 so outline what is contained here, why it should be merged, and what, if
60 to understand what I'm pulling, and why I should pull it. I also
71 what they do and why they do it, but explain the _timing_. What
159 description of that tag (which is why you need to provide good
|
| /Linux-v6.1/arch/um/drivers/ |
| D | slirp.h | 9 * XXX this next definition is here because I don't understand why this
14 * or why I can't typecast like this:
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 170 See the driver for the exact reasons as to why the packets were
180 why the packets were dropped.
188 FIFO error. See the driver for the exact reasons as to why the
198 reasons as to why the packets were dropped.
|
| /Linux-v6.1/Documentation/timers/ |
| D | timers-howto.rst | 66 - Why not usleep?
76 - Why not msleep for (1ms - 20ms)?
85 - Why is there no "usleep" / What is a good range?
|
| /Linux-v6.1/Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 14 There are a few reasons why you might want to consider building your firmware
21 Even if you have these needs there are a few reasons why you may not be
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | tainted-kernels.rst | 8 cause might be the event that got the kernel tainted. That's why bug reports
14 trustworthy. That's also why the kernel will print the tainted state when it
25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened
52 tainted; any other number indicates the reasons why it is. The easiest way to
152 there should be other information in the log indicating why this tainting
|
| D | reporting-regressions.rst | 148 system's configuration, or application. That's why in the end it's often up to
212 regzbot, the Linux kernel regression tracking bot. That's why you want to bring
291 basis. This is another reason why it's in everybody's interest to regularly test
319 but sometimes bend it to make progress. That's for example why some users had to
323 Why do later versions have to be "compiled with a similar configuration"?
359 What is regression tracking and why should I care about it?
364 true for Linux kernel development as well. That's why Thorsten Leemhuis, the
367 paid for this, that's why the work is done on a best effort basis.
369 Why and how are Linux kernel regressions tracked using a bot?
374 That's why the Linux kernel's regression tracker developed regzbot to facilitate
|
| /Linux-v6.1/fs/efs/ |
| D | file.c | 24 * i have no idea why this happens as often as it does in efs_get_block()
48 * i have no idea why this happens as often as it does in efs_bmap()
|
| /Linux-v6.1/Documentation/rust/ |
| D | coding-guidelines.rst | 89 before every ``unsafe`` block, and they explain why the code inside the block is
90 correct/sound, i.e. why it cannot trigger undefined behavior in any case, e.g.:
100 comments show why a call (for functions) or implementation (for traits) actually
168 describing why the code inside is sound.
|
