| /Linux-v5.10/arch/powerpc/kernel/ |
| D | irq.c | 97 unsigned long happened; in get_irq_happened() local
100 : "=r" (happened) : "i" (offsetof(struct paca_struct, irq_happened))); in get_irq_happened()
102 return happened; in get_irq_happened()
136 unsigned char happened = local_paca->irq_happened; in __check_irq_replay() local
158 if (happened & PACA_IRQ_HARD_DIS) { in __check_irq_replay()
166 if (!(happened & PACA_IRQ_DEC)) { in __check_irq_replay()
169 happened |= PACA_IRQ_DEC; in __check_irq_replay()
174 if (happened & PACA_IRQ_DEC) { in __check_irq_replay()
179 if (happened & PACA_IRQ_EE) { in __check_irq_replay()
184 if (happened & PACA_IRQ_DBELL) { in __check_irq_replay()
[all …]
|
| /Linux-v5.10/drivers/usb/usbip/ |
| D | usbip_event.c | 176 int happened = 0; in usbip_event_happened() local
181 happened = 1; in usbip_event_happened()
184 return happened; in usbip_event_happened()
|
| /Linux-v5.10/arch/arm/kernel/ |
| D | hyp-stub.S | 49 strne \reg1, [\reg2, \reg3] @ record what happened and give up
|
| /Linux-v5.10/Documentation/networking/ |
| D | xfrm_sync.rst | 168 the change happened as a result of an update.
175 happened) is set to inform the user what happened.
|
| /Linux-v5.10/Documentation/leds/ |
| D | ledtrig-oneshot.rst | 8 happened, than the trigger turns the LED on and than keeps it off for a
|
| /Linux-v5.10/Documentation/parisc/ |
| D | debugging.rst | 43 where exactly it happened. If you're lucky the IAOQ will point to the
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 11 exactly as it happened originally.
52 which isn't quite what happened and wouldn't be caught during the log replay.
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same
60 has happened; look for lines saying "root hub lost power or was reset".
157 happened and will continue to use the partition tables, inodes, and
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | bug-bisect.rst | 56 depending if the bug happened on the changeset you're testing
|
| D | perf-security.rst | 183 monitoring. CPU and system events happened when executing either in
192 happened when executing either in user or in kernel space can be
199 system events happened when executing in user space only can be
|
| D | bug-hunting.rst | 41 Kernel's source code where the bug happened. Depending on the severity of
185 The position where the above call happened can be seen with::
244 Once you find where the bug happened, by inspecting its location,
|
| /Linux-v5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-handle.txt | 63 /* Something wrong happened, the counter is not incremented by 1 */
|
| /Linux-v5.10/Documentation/arm/ |
| D | kernel_user_helpers.rst | 144 Return zero if `*ptr` was changed or non-zero if no exchange happened.
237 changed or non-zero if no exchange happened.
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-led | 60 event has happened will return an ENODATA error.
|
| /Linux-v5.10/Documentation/filesystems/ext4/ |
| D | super.rst | 363 - First time an error happened, in seconds since the epoch.
375 - Name of function where the error happened.
379 - Line number where error happened.
391 - Line number where most recent error happened.
399 - Name of function where the most recent error happened.
|
| /Linux-v5.10/Documentation/networking/devlink/ |
| D | devlink-health.rst | 11 order to know when something bad happened to a PCI device.
|
| /Linux-v5.10/Documentation/input/devices/ |
| D | rotary-encoder.rst | 68 should have happened, unless it flipped back on half the way. The
|
| /Linux-v5.10/Documentation/timers/ |
| D | timers-howto.rst | 93 that may have happened for other reasons, or at the
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 89 it doesn't even know this happened).
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 56 1. If you want to know what error exactly happened to <inode> before fixing, do::
|
| D | inotify.rst | 52 which happened first. A single queue trivially gives you ordering. Such
|
| /Linux-v5.10/arch/openrisc/ |
| D | Kconfig | 147 the last exception has happened in delay slot.
|
| /Linux-v5.10/Documentation/input/joydev/ |
| D | joystick-api.rst | 146 presses happened at the same time, and similar.
191 The other reason is that you want to know all what happened, and not
|
| /Linux-v5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 66 counter increment or addition happened, function returned true),
|
| /Linux-v5.10/Documentation/scheduler/ |
| D | sched-domains.rst | 41 at the time the scheduler_tick() happened and iterates over all sched domains
|
