Home
last modified time | relevance | path

Searched full:ownership (Results 1 – 25 of 712) sorted by relevance

12345678910>>...29

/linux-6.14.4/drivers/i2c/muxes/
Di2c-mux-pca9541.c32 * Before each bus transaction, a master has to acquire bus ownership. After the
33 * transaction is complete, bus ownership has to be released. This fits well
67 #define ARB_TIMEOUT (HZ / 8) /* 125 ms until forcing bus ownership */
143 * the slave bus if it owns it; otherwise it has to request ownership first.
147 * Bus Ownership Other master Action
152 * off no no take ownership
159 * request ownership at the same time. In this case, one master will turn on
161 * bus ownership. Result is that the bus is turned on, and master which did
191 * Bus is off. Request ownership or turn it on unless in pca9541_arbitrate()
192 * other master requested ownership. in pca9541_arbitrate()
[all …]
/linux-6.14.4/Documentation/filesystems/
Didmappings.rst7 reading from or writing ownership to disk, reporting ownership to userspace, or
172 When a process creates or wants to change ownership of a file, or when the
173 ownership of a file is read from disk by a filesystem, the userspace id is
200 example, it is used when reporting back the ownership of a file to userspace
240 ownership information about the file the kernel can't simply map the id back up
350 but they are exclusively used when determining file ownership which is why they
495 In order to report ownership to userspace the kernel uses the crossmapping
509 idmapping. Thus, the kernel will report the ownership of this file as the
521 In order to report ownership to userspace the kernel uses the crossmapping
535 idmapping. Thus, the kernel will report the ownership of this file as the
[all …]
/linux-6.14.4/drivers/net/wireless/intel/iwlwifi/mei/
Diwl-mei.h19 * iwlwifi can request or release ownership on the WiFi device through iwlmei.
96 * to release the ownership on the device through the HW registers. In that
97 * case, iwlwifi must first request ownership using the SAP protocol.
99 * Once iwlwifi will request ownership through the SAP protocol, CSME will
100 * grant the ownership on the device through the HW registers as well.
101 * In order to request ownership over SAP, we first need to have an interface
105 * this is impossible as long as we don't have ownership on the device.
113 * DOC: CSME behavior regarding the ownership requests
115 * The ownership requests from the host can come in two different ways:
120 * and it can request ownership with %SAP_MSG_NOTIF_HOST_ASKS_FOR_NIC_OWNERSHIP.
[all …]
Dsap.h76 * DOC: Ownership
87 * CSME can take ownership.
91 * DOC: Ownership transfer
96 * host know whether the ownership is granted or no. If the ownership is
99 * When CSME requests ownership, it'll send the
104 * CSME will take ownership on the device anyway.
105 * When CSME is willing to release the ownership, it'll send
198 * the host will not get ownership. Any other value means the host is
/linux-6.14.4/tools/perf/pmu-events/arch/x86/goldmontplus/
Dcache.json327 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
333 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
338 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
344 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
349 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
355 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
360 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
366 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
371 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
377 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
[all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/goldmont/
Dcache.json327 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
333 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
338 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
344 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
349 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
355 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
360 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
366 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
371 …"BriefDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand & …
377 …"PublicDescription": "Counts data read, code read, and read for ownership (RFO) requests (demand &…
[all …]
/linux-6.14.4/include/uapi/linux/
Dnl80211-vnd-intel.h15 * @IWL_MVM_VENDOR_CMD_HOST_GET_OWNERSHIP: asks for ownership on the device.
18 * kernel will manage on its own to get ownership of the device.
34 * 6) The user space asks iwlmei to request ownership on the device (with
36 * 7) iwlmei requests ownership from the CSME firmware
37 * 8) The CSME firmware grants ownership
/linux-6.14.4/Documentation/bpf/
Dgraph_ds_impl.rst101 program has ownership of the pointee's (object pointed to by ``n``) lifetime.
102 The BPF program must pass off ownership before exiting - either via
107 "ownership is acquired" and "ownership is passed", respectively)
109 What should the verifier do with ``n`` after ownership is passed off? If the
115 When ownership is passed to ``tree`` via ``bpf_rbtree_add`` the answer is less
151 to pass ownership.
165 * Ownership of pointee must be 'released' by passing it to some graph API
205 has already been added (or already removed), as the ownership model
/linux-6.14.4/tools/perf/pmu-events/arch/x86/icelakex/
Dother.json223 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
233 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
243 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
253 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
263 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
273 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
283 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
293 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/perf/pmu-events/arch/x86/meteorlake/
Dother.json66 …"BriefDescription": "Counts demand reads for ownership (RFO) and software prefetches for exclusive…
77 …efDescription": "Counts demand read for ownership (RFO) requests and software prefetches for exclu…
88 …"BriefDescription": "Counts demand reads for ownership (RFO) and software prefetches for exclusive…
/linux-6.14.4/kernel/printk/
Dnbcon.c82 * b) Gives up console ownership by clearing the 'prio' field.
248 * acquire ownership in order to satisfy the assumptions of in nbcon_context_try_acquire_direct()
295 * directly takes ownership. in nbcon_waiter_matches()
296 * 3. The higher priority context releases the ownership. in nbcon_waiter_matches()
297 * 4. Another lower priority context takes the ownership. in nbcon_waiter_matches()
358 * The previous owner should have never released ownership in nbcon_context_try_acquire_requested()
679 * nbcon_context_can_proceed - Check whether ownership can proceed
684 * ownership was handed over or taken.
737 * It is not clear whether the waiter really took over ownership. The in nbcon_context_can_proceed()
739 * ownership is needed for it to proceed. If yes, it must reacquire in nbcon_context_can_proceed()
[all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/alderlaken/
Dmemory.json80 …"BriefDescription": "Counts demand reads for ownership (RFO) and software prefetches for exclusive…
90 …"BriefDescription": "Counts demand reads for ownership (RFO) and software prefetches for exclusive…
/linux-6.14.4/drivers/video/
Daperture.c25 * ownership of framebuffer memory and hand-over between drivers.
64 * have previously claimed ownership of the range and are currently driving
77 * framebuffer apertures. Ownership of the framebuffer memory is achieved
119 * The similar to the previous example, the generic driver claims ownership
220 * devm_aperture_acquire_for_platform_device - Acquires ownership of an aperture
228 * driver takes over ownership of the aperture, aperture helpers will then
311 * should acquire ownership of those memory areas and afterwards call
/linux-6.14.4/drivers/net/ethernet/broadcom/bnxt/
Dbnxt_hwrm.c52 * passing it to hwrm_req_send() unless ownership of the request has been
54 * consumed, either because it is never sent or because ownership has been
82 ctx->flags = 0; /* __GFP_ZERO, but be explicit regarding ownership */ in __hwrm_req_init()
254 * hwrm_req_hold() - Claim ownership of the request's resources.
259 * Take ownership of the request. Ownership places responsibility on the
261 * hwrm_req_drop(). The caller taking ownership implies that a subsequent
264 * Taking ownership returns a reference to the response. Retaining and
265 * accessing the response data is the most common reason to take ownership
266 * of the request. Ownership can also be acquired in order to reuse the same
272 * caller until ownership of the request is relinquished via a call to
[all …]
/linux-6.14.4/fs/tracefs/
Dinternal.h21 * struct eventfs_attr - cache the mode and ownership of a eventfs entry
39 * @entry_attrs: Saved mode and ownership of the @d_children
41 * @attr: Saved mode and ownership of eventfs_inode itself
/linux-6.14.4/tools/perf/pmu-events/arch/x86/lunarlake/
Dother.json47 …"BriefDescription": "Counts demand reads for ownership, including SWPREFETCHW which is an RFO Catc…
58 …efDescription": "Counts demand read for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/perf/pmu-events/arch/x86/emeraldrapids/
Dother.json109 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
119 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
129 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
139 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/perf/pmu-events/arch/x86/rocketlake/
Dcache.json136 …"PublicDescription": "Counts the total number of RFO (read for ownership) requests to L2 cache. L2…
199 "PublicDescription": "Counts the RFO (Read-for-Ownership) requests that hit L2 cache.",
208 "PublicDescription": "Counts the RFO (Read-for-Ownership) requests that miss L2 cache.",
244 …Longest Latency cache). Requests include data and code reads, Reads-for-Ownership (RFOs), speculat…
589 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
599 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
609 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
619 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
629 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
639 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
[all …]
Dother.json90 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
100 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
110 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/perf/pmu-events/arch/x86/icelake/
Dcache.json136 …"PublicDescription": "Counts the total number of RFO (read for ownership) requests to L2 cache. L2…
199 "PublicDescription": "Counts the RFO (Read-for-Ownership) requests that hit L2 cache.",
208 "PublicDescription": "Counts the RFO (Read-for-Ownership) requests that miss L2 cache.",
244 …Longest Latency cache). Requests include data and code reads, Reads-for-Ownership (RFOs), speculat…
589 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
599 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
609 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
619 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
629 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
639 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
[all …]
Dother.json90 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
100 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
110 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/testing/selftests/ftrace/test.d/00basic/
Dtest_ownership.tc3 # description: Test file and directory ownership changes for eventfs
17 # Remove any group ownership already
42 # Note, the remount does not update ownership so test going to and from owner
/linux-6.14.4/tools/perf/pmu-events/arch/x86/grandridge/
Duncore-cache.json428 …"BriefDescription": "Counts when a RFO (the Read for Ownership issued before a write) request hit…
477 …otal number of requests coming from a unit on this socket for exclusive ownership of a cache line …
487 …otal number of requests coming from a unit on this socket for exclusive ownership of a cache line …
496 …o this CHA. Reads include all read opcodes (including RFO: the Read for Ownership issued before a …
506 …o this CHA. Reads include all read opcodes (including RFO: the Read for Ownership issued before a …
697 …"BriefDescription": "Last level cache prefetch read for ownership from local IA that hit the cache…
707 "BriefDescription": "Read for ownership from local IA that hit the cache",
717 "BriefDescription": "Read for ownership prefetch from local IA that hit the cache",
767 …"BriefDescription": "Last level cache prefetch read for ownership from local IA that miss the cach…
897 …"BriefDescription": "Last level cache prefetch read for ownership from local IA that miss the cach…
[all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/sapphirerapids/
Dother.json139 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
149 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
159 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
169 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
/linux-6.14.4/tools/perf/pmu-events/arch/x86/graniterapids/
Dother.json69 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…
79 …fDescription": "Counts demand reads for ownership (RFO) requests and software prefetches for exclu…

12345678910>>...29