Home
last modified time | relevance | path

Searched full:why (Results 1 – 25 of 1246) sorted by relevance

12345678910>>...50

/Linux-v5.15/include/trace/events/
Dcachefiles.h74 enum cachefiles_obj_ref_trace why,
77 TP_ARGS(obj, cookie, why, usage),
83 __field(enum cachefiles_obj_ref_trace, why )
91 __entry->why = why;
96 __print_symbolic(__entry->why, cachefiles_obj_ref_traces))
169 enum fscache_why_object_killed why),
171 TP_ARGS(obj, de, why),
177 __field(enum fscache_why_object_killed, why )
183 __entry->why = why;
188 __print_symbolic(__entry->why, cachefiles_obj_kill_traces))
[all …]
Drxrpc.h697 TP_PROTO(unsigned int call_nr, const char *why, u32 cid, u32 call_id,
700 TP_ARGS(call_nr, why, cid, call_id, seq, abort_code, error),
704 __array(char, why, 4 )
713 memcpy(__entry->why, why, 4);
725 __entry->abort_code, __entry->error, __entry->why)
755 TP_PROTO(struct rxrpc_call *call, enum rxrpc_transmit_trace why),
757 TP_ARGS(call, why),
761 __field(enum rxrpc_transmit_trace, why )
769 __entry->why = why;
777 __print_symbolic(__entry->why, rxrpc_transmit_traces),
[all …]
Dfscache.h358 enum fscache_page_trace why),
360 TP_ARGS(cookie, page, why),
365 __field(enum fscache_page_trace, why )
371 __entry->why = why;
376 __print_symbolic(__entry->why, fscache_page_traces),
422 enum fscache_op_trace why),
424 TP_ARGS(cookie, op, why),
429 __field(enum fscache_op_trace, why )
435 __entry->why = why;
440 __print_symbolic(__entry->why, fscache_op_traces))
/Linux-v5.15/drivers/infiniband/core/
Duverbs_std_types.c43 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
Duverbs_std_types_async_fd.c23 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-v5.15/fs/afs/
Ddir_edit.c188 enum afs_edit_dir_reason why) in afs_edit_dir_add() argument
292 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_nospc, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
308 trace_afs_edit_dir(vnode, why, afs_edit_dir_create, b, slot, in afs_edit_dir_add()
343 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_inval, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
352 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_error, 0, 0, 0, 0, name->name); in afs_edit_dir_add()
365 struct qstr *name, enum afs_edit_dir_reason why) in afs_edit_dir_remove() argument
436 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_noent, in afs_edit_dir_remove()
444 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete, b, slot, in afs_edit_dir_remove()
474 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_inval, in afs_edit_dir_remove()
485 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_error, in afs_edit_dir_remove()
/Linux-v5.15/Documentation/RCU/
DUP.rst52 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
Drcu.rst20 - Why would anyone want to use RCU?
51 thing at a time, why should I wait for a grace period?
69 - Why the name "RCU"?
/Linux-v5.15/Documentation/maintainer/
Drebasing-and-merging.rst123 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.
Dpull-requests.rst51 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-v5.15/arch/um/drivers/
Dslirp.h9 * XXX this next definition is here because I don't understand why this
14 * or why I can't typecast like this:
/Linux-v5.15/Documentation/admin-guide/
Dtainted-kernels.rst8 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
145 there should be other information in the log indicating why this tainting
Dreporting-issues.rst265 development community, and this document. That's why you can't demand
307 face, even if they look small or totally unrelated. That's why you should report
481 your kernel gets enhanced in any way. That's why you should remove or disable
490 module not part of the Linux kernel. That why your might need to uninstall the
502 be such an error if your kernel is tainted. That's why it's in your interest to
504 only reason why this step is here, as this process later will tell you to
512 why the kernel also mentions the taint status when it reports an internal
521 to find out why. Try to eliminate the reason. Often it's caused by one these
582 might be caused by a bit flip due to cosmic radiation. That's why you should
622 That's why you have to find the right place and way to report issues yourself.
[all …]
/Linux-v5.15/scripts/
DKbuild.include92 echo ' $(call escsq,$($(quiet)cmd_$(1)))$(echo-why)';)
159 # why - tell why a target got built
178 why = \
195 echo-why = $(call escsq, $(strip $(why)))
/Linux-v5.15/Documentation/driver-api/firmware/
Dbuilt-in-fw.rst14 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-v5.15/Documentation/ABI/testing/
Dsysfs-class-net-statistics170 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-v5.15/Documentation/timers/
Dtimers-howto.rst66 - Why not usleep?
76 - Why not msleep for (1ms - 20ms)?
85 - Why is there no "usleep" / What is a good range?
/Linux-v5.15/fs/efs/
Dfile.c24 * 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-v5.15/include/rdma/
Duverbs_types.h71 enum rdma_remove_reason why,
104 enum rdma_remove_reason why,
147 enum rdma_remove_reason why);
/Linux-v5.15/sound/core/
Dpcm_trace.h84 TP_PROTO(struct snd_pcm_substream *substream, const char *why),
85 TP_ARGS(substream, why),
98 __entry->reason = (why);
/Linux-v5.15/arch/arm/kernel/
Dentry-common.S99 mov r2, why @ 'syscall'
109 * "slow" syscall return path. "why" tells us if this was a real syscall.
259 mov why, #0 @ no longer a real syscall
378 mov why, #0 @ prevent syscall restart handling
384 mov why, #0 @ prevent syscall restart handling
/Linux-v5.15/Documentation/power/
Dfreezing-of-tasks.rst101 IV. Why do we do that?
139 "RJW:> Why we freeze tasks at all or why we freeze kernel threads?
149 So in practice, the 'at all' may become a 'why freeze kernel threads?' and
180 may be undesirable. That's why kernel threads are not freezable by default.
/Linux-v5.15/Documentation/vm/
Dcleancache.rst159 * Why does cleancache have its sticky fingers so deep inside the
190 * Why not make cleancache asynchronous and batched so it can more
204 * Why is non-shared cleancache "exclusive"? And where is the
258 * Why not use the KVA of the inode as the key? (Christoph Hellwig)
273 * Why is a global variable required?
/Linux-v5.15/fs/cachefiles/
Dnamei.c86 enum fscache_why_object_killed why) in cachefiles_mark_object_buried() argument
107 trace_cachefiles_mark_buried(NULL, dentry, why); in cachefiles_mark_object_buried()
118 trace_cachefiles_mark_buried(object, dentry, why); in cachefiles_mark_object_buried()
125 if (why != FSCACHE_OBJECT_IS_STALE) in cachefiles_mark_object_buried()
126 fscache_object_mark_killed(&object->fscache, why); in cachefiles_mark_object_buried()
292 enum fscache_why_object_killed why) in cachefiles_bury_object() argument
311 trace_cachefiles_unlink(object, rep, why); in cachefiles_bury_object()
316 cachefiles_mark_object_buried(cache, rep, why); in cachefiles_bury_object()
422 trace_cachefiles_rename(object, rep, grave, why); in cachefiles_bury_object()
429 cachefiles_mark_object_buried(cache, rep, why); in cachefiles_bury_object()
/Linux-v5.15/Documentation/bpf/
Dbpf_design_QA.rst29 Q: Why C calling convention was chosen?
132 For example why BPF_JNE and other compare and jumps are not cpu-like?
137 Q: Why BPF_DIV instruction doesn't map to x64 div?
143 Q: Why there is no BPF_SDIV for signed divide operation?
148 Q: Why BPF has implicit prologue and epilogue?
157 Q: Why BPF_JLT and BPF_JLE instructions were not introduced in the beginning?

12345678910>>...50