Searched full:handled (Results 1 – 25 of 324) sorted by relevance
12345678910>>...13
| /Documentation/trace/ |
| D | events-nmi.rst | 41 …>-0 [000] d.h3 505.397558: nmi_handler: perf_event_nmi_handler() delta_ns: 3236765 handled: 1
42 …>-0 [000] d.h3 505.805893: nmi_handler: perf_event_nmi_handler() delta_ns: 3174234 handled: 1
43 …>-0 [000] d.h3 506.158206: nmi_handler: perf_event_nmi_handler() delta_ns: 3084642 handled: 1
44 …>-0 [000] d.h3 506.334346: nmi_handler: perf_event_nmi_handler() delta_ns: 3080351 handled: 1
|
| /Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 19 all supported DIAGNOSE calls need to be handled by either KVM or its
53 Handled by userspace.
56 Handled by userspace.
59 Handled by userspace.
62 Handled by either userspace or KVM (ioeventfd case).
84 This function code is handled by userspace.
|
| /Documentation/leds/ |
| D | ledtrig-usbport.rst | 10 listed as separated entries in a "ports" subdirectory. Selecting is handled by
24 2) Device with a physical port handled by few controllers
28 port may be handled by ohci-platform, ehci-platform and xhci-hcd. If there is
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-flakey.rst | 44 Write I/O is handled correctly.
48 Read I/O is handled correctly.
52 Read I/O is handled correctly.
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | sharp,lq150x1lg11.yaml | 27 the RL/UD and/or SELLVDS pins are assumed to be handled
35 the RL/UD and/or SELLVDS pins are assumed to be handled
|
| /Documentation/admin-guide/ |
| D | devices.txt | 198 loop devices is handled by mount(8) or losetup(8).
207 Partitions are handled in the same way as for IDE
509 Partitions are handled the same way as for IDE disks
520 Partitions are handled the same way as for the first
628 Partitions are handled in the same way as for IDE
716 Partitions are handled the same way as for the first
734 Partitions are handled the same way as for the first
861 Partitions are handled in the same way as for IDE
885 Partitions are handled in the same way as for IDE
938 Partitions are handled as for major 48.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform_profile | 33 source such as e.g. a hotkey triggered profile change handled
34 either directly by the embedded-controller or fully handled
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-intro.rst | 21 CEC, need to be handled by the kernel, others can be handled either by
|
| D | cec-ioc-g-mode.rst | 215 does nothing and this message has to be handled by a follower
223 does nothing and this message has to be handled by a follower
231 and this message has to be handled by a follower instead.
237 and this message has to be handled by a follower instead.
244 does nothing and this message has to be handled by a follower
253 does nothing (for any CEC version) and this message has to be handled
|
| /Documentation/arch/arm/ |
| D | interrupts.rst | 10 MMU TLB. Each MMU TLB variant is now handled completely separately -
18 The 2.5 kernels will be having major changes to the way IRQs are handled.
50 SA11x0 IRQs are handled by two separate "chip" structures, one for
82 handled by do_level_IRQ.
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 22 - The ioctl can't be handled because the device is in state where it
34 - The ioctl can't be handled because the device is busy. This is
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 58 All Interrupts during some guest VMs running would be handled by GenieZone
61 handled by host VM directly for performance reason. Irqfd is also implemented
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,omap2-intc.txt | 15 - ti,intc-size: Number of interrupts handled by the interrupt controller.
|
| D | ti,cp-intc.txt | 16 - ti,intc-size: Number of interrupts handled by the interrupt controller.
|
| /Documentation/core-api/ |
| D | entry.rst | 29 functions are partially instrumentable, which is handled by marking them
124 the work handled on return to user space.
212 The state update on entry is handled in irqentry_nmi_enter() which updates
275 above cannot be handled in an exception-agnostic way.
|
| /Documentation/translations/zh_CN/rust/ |
| D | coding-guidelines.rst | 50 // `object` is ready to be handled now.
58 // FIXME: The error should be handled properly.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | brcm,iproc-pdc-mbox.txt | 4 handled by the FA2 (Northstar Plus).
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 168 the logical CPUs handled by the given driver.
235 handled by it.
244 all of the logical CPUs to be handled by the given ``CPUIdle`` driver with the
261 struct cpuidle_device objects representing CPUs handled by the given
266 along with all of the struct cpuidle_device objects representing CPUs handled
|
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 30 handled by this team and the reporter will be guided to contact the regular
46 While hardware security issues are often handled by the affected hardware
90 The Linux kernel community has successfully handled hardware security
195 time of the development process and needs to be handled in a timely manner.
303 Subscription is handled by the response teams. Disclosed parties who want
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lt3593.txt | 22 be handled by its own device node.
|
| /Documentation/arch/arm/nwfpe/ |
| D | todo.rst | 21 and are handled by routines in libc. These are not implemented by the FPA11
22 hardware, but are handled by the floating point support code. They should
|
| /Documentation/networking/ |
| D | ipvs-sysctl.rst | 57 connections handled by IPVS.
59 This should be enabled if connections handled by IPVS are to be
60 also handled by stateful firewall rules. That is, iptables rules
64 Connections handled by the IPVS FTP application module
|
| D | tls-offload.rst | 54 On the receive side if the device handled decryption and authentication
57 are handled normally. ``ktls`` is informed when data is queued to the socket
83 fails the connection is handled entirely in software using the same mechanism
281 the remainder of the previous record inside segment 3 cannot be handled.
364 fully acknowledged, so if skbs reach the wrong device they can be handled
383 had been handled successfully and authenticated or the packet has to be passed
391 A packet should also not be handled by the TLS offload if it contains
444 the driver was successfully handled.
|
| /Documentation/devicetree/bindings/phy/ |
| D | calxeda-combophy.yaml | 14 Programming the PHYs is typically handled by those device drivers,
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-dsp-keystone.txt | 13 - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
|
12345678910>>...13