Searched full:probe (Results 1 – 25 of 201) sorted by relevance
123456789
| /Documentation/ |
| D | kprobes.txt | 16 6. Probe Overhead
37 any instruction in the kernel. A return probe fires when a specified
44 the probe is to be inserted and what handler is to be called when
45 the probe is hit.
86 Since kprobes can probe into a running kernel code, it can change the
106 How Does a Return Probe Work?
111 probe is hit, Kprobes saves a copy of the return address, and replaces
117 passes to the trampoline and that probe is hit. Kprobes' trampoline
138 zero when the return probe is registered, and is incremented every
140 object available for establishing the return probe.
[all …]
|
| /Documentation/trace/ |
| D | tracepoints.rst | 10 connect probe functions to them and provides some examples of probe
16 A tracepoint placed in code provides a hook to call a function (probe)
17 that you can provide at runtime. A tracepoint can be "on" (a probe is
18 connected to it) or "off" (no probe is attached). When a tracepoint is
93 Connecting a function (probe) to a tracepoint is done by providing a
94 probe (function to call) for the specific tracepoint through
95 register_trace_subsys_eventname(). Removing a probe is done through
96 unregister_trace_subsys_eventname(); it will remove the probe.
100 the probe. This, and the fact that preemption is disabled around the
101 probe call, make sure that probe removal and module unload are safe.
[all …]
|
| D | kprobetrace.rst | 10 this is based on kprobes (kprobe and kretprobe). So it can probe wherever
11 kprobes can probe (this means, all functions except those with
19 current_tracer. Instead of that, add probe points via
31 p[:[GRP/]EVENT] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe
32 r[MAXACTIVE][:[GRP/]EVENT] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe
33 -:[GRP/]EVENT : Clear a probe
39 SYM[+offs] : Symbol+offset where the probe is inserted.
40 MEMADDR : Address where the probe is inserted.
45 FETCHARGS : Arguments. Each probe can have up to 128 args.
62 (\*1) only for the probe on function entry (offs == 0).
[all …]
|
| D | uprobetracer.rst | 14 current_tracer. Instead of that, add probe points via
37 OFFSET : Offset where the probe is inserted.
39 FETCHARGS : Arguments. Each probe can have up to 128 args.
54 (\*1) only for return probe.
79 You can check the total number of probe hits per event via
81 the second is the event name, the third is the number of probe hits.
85 * Add a probe as a new uprobe event, write a new definition to uprobe_events
90 * Add a probe as a new uretprobe event::
107 at the probed text address. Probe zfree function in /bin/zsh::
124 .. note:: User has to explicitly calculate the offset of the probe-point
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 2 * Samsung Exynos NoC (Network on Chip) Probe device
4 The Samsung Exynos542x SoC has NoC (Network on Chip) Probe for NoC bus.
15 - reg: physical base address of each NoC Probe and length of memory mapped region.
18 - clock-names : the name of clock used by the NoC Probe, "nocp"
21 Example : NoC Probe nodes in Device Tree are listed below.
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 17 - @probe:
73 The probe() callback
78 int (*probe) (struct usb_interface *intf,
144 No callbacks other than probe will be invoked for an interface
147 Probe will never be called for an interface bound to a driver.
148 Hence following a successful probe, disconnect will be called
149 before there is another probe for the same interface.
|
| D | hotplug.rst | 17 device driver's probe() routine.
133 .probe = my_probe,
146 choosing drivers to probe(). The thread doing new device processing checks
148 and device descriptors for the device. It will only call ``probe()`` if there
149 is a match, and the third argument to ``probe()`` will be the entry that
153 probed for each new device; the third parameter to ``probe()`` will be
|
| /Documentation/driver-api/ |
| D | device_link.rst | 23 another one can probe or function correctly.
61 device ``->probe`` callback or a boot-time PCI quirk.
65 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
70 ``->probe`` callback while the supplier is still probing, but the consumer must
76 is added in the ``->probe`` callback of the supplier or consumer driver, it is
91 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
95 probe or later unbinds.
97 Similarly, when the device link is added from supplier's ``->probe`` callback,
99 purged when the supplier fails to probe or later unbinds.
103 to probe for a driver for the consumer driver on the link automatically after
[all …]
|
| D | eisa.rst | 17 detection code is generally also used to probe ISA cards). Moreover,
38 implements the necessary callbacks to probe and release devices
60 int force_probe; /* Probe even when no slot 0 */
71 slots max slot number to probe
72 force_probe Probe even when slot 0 is empty (no EISA mainboard)
107 .probe and .remove members are mandatory.
122 .probe = vortex_eisa_probe,
130 The sysfs framework calls .probe and .remove functions upon device
197 Force the probing code to probe EISA slots even when it cannot find an
216 expect to have explored the whole machine when they exit their probe
|
| D | isa.rst | 11 finding their hardware due to a probe() error not being passed up
43 struct device_driver, the normal probe/remove/shutdown/suspend/resume
60 of the old .probe in .match, which would only keep them registered after
64 do everything in .probe() as before.
70 values have been passed in) and .probe() for everything else. This is
|
| /Documentation/i2c/ |
| D | old-module-parameters.rst | 7 control how the driver would probe i2c buses and attach to devices. These
8 parameters were known as "probe" (to let the driver probe for an extra
25 # modprobe <driver> probe=1,0x2d
|
| D | upgrading-clients.rst | 117 Add the probe and remove methods to the i2c_driver, as so::
120 + .probe = example_probe,
132 i2c_driver entry names. The rest of the probe routine will now need to be
136 the probe function is called, so the following client setup
150 The call to i2c_attach_client is no longer needed, if the probe
152 attached by the core. Change the probe routine as so::
182 In the probe routine, ensure that the new state has the client stored
283 .probe = example_probe,
|
| D | fault-codes.rst | 38 Also, codes returned by adapter probe methods follow rules which are
77 Returned by driver probe() methods. This is a bit more
82 about probe faults other than ENXIO and ENODEV.)
94 Returned by driver probe() methods to indicate that they
|
| D | writing-clients.rst | 49 .probe = foo_probe,
85 to NULL in remove() or if probe() failed anymore. The i2c-core does this
131 protocol to probe device presence. Another was that devices and their drivers
132 can be sufficiently configured using only such probe primitives.
153 kind of driver in Linux: they provide a probe() method to bind to
167 The probe function is called when an entry in the id_table name field
179 take care of finding the right driver and will call its probe() method.
190 possible I2C addresses to probe. A device is created for the first
212 for unsupported ones), a list of addresses to probe, and a device type
|
| /Documentation/sound/soc/ |
| D | machine.rst | 21 int (*probe)(struct platform_device *pdev);
40 probe()/remove()
42 probe/remove are optional. Do any machine specific probe here.
|
| /Documentation/networking/ |
| D | devlink-params.txt | 56 Controls the device's reset policy on driver probe.
61 Always reset device on driver probe.
63 Never reset device on driver probe.
|
| D | mac80211-auth-assoc-deauth.txt | 30 alt no probe request data known
31 mac80211->driver: TX directed probe request
32 driver->mac80211: RX probe response
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 39 provide probe() and remove() methods. They support power management
43 int (*probe)(struct platform_device *);
53 Note that probe() should in general verify that the specified device hardware
62 the probe() routine can live in an init section to reduce the driver's
66 int (*probe)(struct platform_device *))
124 original IBM PCs, rely on error-prone "probe-the-hardware" models for hardware
171 driver probe() after finding a match between device and driver. If the
172 probe() succeeds, the driver and device are bound as usual. There are
238 6. Inside the early platform driver probe()
242 in the probe() function can use is_early_platform_device() to check if
|
| D | driver.rst | 36 .probe = eepro100_probe,
68 .probe = eepro100_probe,
150 int (*probe) (struct device *dev);
152 The probe() entry is called in task context, with the bus's rwsem locked
154 container_of() to convert "dev" to a bus-specific type, both in probe()
164 When the driver has successfully bound itself to that device, then probe()
168 A driver's probe() may return a negative errno value to indicate that
190 device probe successfully. If during the reattempt, the driver core finds that
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7780.yaml | 47 specified, it will be asserted during driver probe. As the
55 driver probe. As the line is active low, it should be marked
63 during driver probe. As the line is active low, it should be
|
| /Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 40 An example of usage can be seen in the probe function of [#f2]_.
53 The FPGA region's probe function will need to get a reference to the FPGA
55 during the region's probe function.
63 the FPGA. The region driver can build a list of bridges during probe time
|
| /Documentation/driver-api/mei/ |
| D | mei-client-bus.rst | 38 int (*probe)(struct mei_cl_device *dev, const struct mei_cl_id *id);
98 .probe = contact_probe,
123 And the driver's simplified probe routine would look like that:
137 In the probe routine the driver first enable the MEI device and then registers
|
| /Documentation/ide/ |
| D | ide.rst | 103 probe/identification sequence. For example::
123 the probe to look harder by supplying a kernel command line parameter
178 alias block-major-3 ide-probe
191 you need to explicitly enable probing by using "probe" kernel parameter,
194 * "ali14xx.probe" boot option when ali14xx driver is built-in the kernel
196 * "probe" module parameter when ali14xx driver is compiled as module
197 ("modprobe ali14xx probe")
203 You also need to use "probe" kernel parameter for ide-4drives driver
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-sx150x.txt | 32 - semtech,probe-reset: Will trigger a reset of the GPIO expander on probe,
|
| /Documentation/scsi/ |
| D | g_NCR5380.txt | 15 If the irq parameter is 254 or is omitted entirely, the driver will probe
53 E.g. a port mapped NCR5380 board, driver to probe for IRQ:
|
123456789