| /kernel/linux/linux-6.6/net/mac80211/ |
| D | Kconfig | 88 bool "Trace all mac80211 debug messages"
93 collect all debugging messages, independent of
96 The overhead in this option is that all the messages
127 many debugging messages. It should not be selected
128 on production systems as some of the messages are
138 debugging messages for the managed-mode MLME. It
140 of the messages are remotely triggerable.
149 debugging messages for station addition/removal.
161 of the messages are remotely triggerable.
170 very verbose OCB debugging messages. It should not
[all …]
|
| /kernel/linux/linux-5.10/net/mac80211/ |
| D | Kconfig | 88 bool "Trace all mac80211 debug messages"
93 collect all debugging messages, independent of
96 The overhead in this option is that all the messages
127 many debugging messages. It should not be selected
128 on production systems as some of the messages are
138 debugging messages for the managed-mode MLME. It
140 of the messages are remotely triggerable.
149 debugging messages for station addition/removal.
161 of the messages are remotely triggerable.
170 very verbose OCB debugging messages. It should not
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig.debug | 86 bool "Verbose user fault messages"
121 bool "Kernel low-level debugging messages via Alpine UART0"
223 bool "Kernel low-level debugging messages via BCM KONA UART"
255 messages to appear over the UART, select this option.
258 bool "Kernel low-level debugging messages via UART1"
265 bool "Kernel low-level debugging messages via UART2"
304 bool "Kernel low-level debugging messages via footbridge serial port"
311 bool "Kernel low-level debugging messages via Digicolor UA0"
318 bool "Kernel low-level debugging messages via ep93xx UART"
326 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/ |
| D | Kconfig.debug | 97 bool "Verbose user fault messages"
132 bool "Kernel low-level debugging messages via Alpine UART0"
262 bool "Kernel low-level debugging messages via BCM KONA UART"
294 messages to appear over the UART, select this option.
297 bool "Kernel low-level debugging messages via UART1"
304 bool "Kernel low-level debugging messages via UART2"
327 bool "Kernel low-level debugging messages via footbridge serial port"
334 bool "Kernel low-level debugging messages via Digicolor UA0"
341 bool "Kernel low-level debugging messages via ep93xx UART"
349 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using
45 The multiplexor provides the message steering. In the transmit path, messages
47 Similarly, in the receive path, messages are constructed on each TCP socket
48 (Psock) and complete messages are steered to a KCM socket.
55 messages on receive as well as other connection specific information for KCM.
63 can be used to send and receive messages from the KCM socket.
73 Messages are sent over a TCP stream with some application protocol message
74 format that typically includes a header which frames the messages. The length
102 socket. The BPF program may also enforce a maximum messages size and report an
105 A timeout may be set for assembling messages on a receive socket. The timeout
[all …]
|
| D | netif-msg.rst | 23 to shed the more verbose level messages as they matured.
25 - 0 Minimal messages, only essential information on fatal errors.
26 - 1 Standard messages, initialization status. No run-time messages
27 - 2 Special media selection messages, generally timer-driver.
28 - 3 Interface starts and stops, including normal status messages
29 - 4 Tx and Rx frame error messages, and abnormal driver operation
46 - More selective control over the type of messages emitted.
65 Messages should changes from::
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using
45 The multiplexor provides the message steering. In the transmit path, messages
47 Similarly, in the receive path, messages are constructed on each TCP socket
48 (Psock) and complete messages are steered to a KCM socket.
55 messages on receive as well as other connection specific information for KCM.
63 can be used to send and receive messages from the KCM socket.
73 Messages are sent over a TCP stream with some application protocol message
74 format that typically includes a header which frames the messages. The length
102 socket. The BPF program may also enforce a maximum messages size and report an
105 A timeout may be set for assembling messages on a receive socket. The timeout
[all …]
|
| D | netif-msg.rst | 23 to shed the more verbose level messages as they matured.
25 - 0 Minimal messages, only essential information on fatal errors.
26 - 1 Standard messages, initialization status. No run-time messages
27 - 2 Special media selection messages, generally timer-driver.
28 - 3 Interface starts and stops, including normal status messages
29 - 4 Tx and Rx frame error messages, and abnormal driver operation
46 - More selective control over the type of messages emitted.
65 Messages should changes from::
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | uncore-interconnect.json | 550 "BriefDescription": "Messages sent direct to the Intel UPI",
1984 "BriefDescription": "CBox AD Credits Empty : VNA Messages",
1988 …"PublicDescription": "CBox AD Credits Empty : VNA Messages : No credits available to send to Cbox …
2181 …0 : REQ on AD : VN0 message requested but lost arbitration : Home (REQ) messages on AD. REQ is ge…
2190 …RSP on AD : VN0 message requested but lost arbitration : Response (RSP) messages on AD. RSP packe…
2199 …: SNP on AD : VN0 message requested but lost arbitration : Snoops (SNP) messages on AD. SNP is us…
2208 …0 message requested but lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is ge…
2217 … on BL : VN0 message requested but lost arbitration : Non-Coherent Standard (NCS) messages on BL.",
2226 …RSP on BL : VN0 message requested but lost arbitration : Response (RSP) messages on BL. RSP packet…
2235 …on BL : VN0 message requested but lost arbitration : Data Response (WB) messages on BL. WB is gen…
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-g-mode.rst | 42 used to initiate messages, i.e. it commands other CEC devices. The
43 follower is the filehandle that receives messages sent to the CEC
60 The CEC framework will process core messages unless requested otherwise
62 case, the CEC framework will pass on most core messages without
63 processing them and the follower will have to implement those messages.
64 There are some messages that the core will always process, regardless of
88 - This is not an initiator, i.e. it cannot transmit CEC messages or
95 it can transmit CEC messages and make changes to the CEC adapter,
102 only one that can transmit CEC messages and make changes to the
129 - This is a follower and it will receive CEC messages unless there
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-g-mode.rst | 42 used to initiate messages, i.e. it commands other CEC devices. The
43 follower is the filehandle that receives messages sent to the CEC
60 The CEC framework will process core messages unless requested otherwise
62 case, the CEC framework will pass on most core messages without
63 processing them and the follower will have to implement those messages.
64 There are some messages that the core will always process, regardless of
88 - This is not an initiator, i.e. it cannot transmit CEC messages or
95 it can transmit CEC messages and make changes to the CEC adapter,
102 only one that can transmit CEC messages and make changes to the
129 - This is a follower and it will receive CEC messages unless there
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/hyperv/ |
| D | vmbus.rst | 56 for passing messages. Most synthetic devices use a single channel,
64 The "in" ring buffer is for messages from the Hyper-V host to the
65 guest, and the "out" ring buffer is for messages from the guest to
105 VMbus messages
107 All VMbus messages have a standard header that includes the message
112 Messages follow one of two patterns:
125 Messages passed between the VSP and VSC are control messages. For
133 ring buffer is minimal. For example, time sync messages from the
140 Three functions exist to send VMbus messages:
142 1. vmbus_sendpacket(): Control-only messages and messages with
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/nvec/ |
| D | nvec.h | 83 * @node: Messages are part of various lists in a &struct nvec_chip
85 * @size: For TX messages, the number of bytes used in @data
86 * @pos: For RX messages, the current position to write to. For TX messages,
90 * This structure is used to hold outgoing and incoming messages. Outgoing
91 * messages have a different format than incoming messages, and that is not
111 * @notifier_list: Notifiers to be called on received messages, see
113 * @rx_data: Received messages that have to be processed
114 * @tx_data: Messages waiting to be sent to the controller
120 * @msg_pool: A pool of messages for allocation
122 * @tx_scratch: Used for building pseudo messages
|
| /kernel/linux/linux-6.6/drivers/staging/nvec/ |
| D | nvec.h | 83 * @node: Messages are part of various lists in a &struct nvec_chip
85 * @size: For TX messages, the number of bytes used in @data
86 * @pos: For RX messages, the current position to write to. For TX messages,
90 * This structure is used to hold outgoing and incoming messages. Outgoing
91 * messages have a different format than incoming messages, and that is not
111 * @notifier_list: Notifiers to be called on received messages, see
113 * @rx_data: Received messages that have to be processed
114 * @tx_data: Messages waiting to be sent to the controller
120 * @msg_pool: A pool of messages for allocation
122 * @tx_scratch: Used for building pseudo messages
|
| /kernel/linux/linux-6.6/include/trace/events/ |
| D | iscsi.h | 19 * Declare event class for iscsi debug messages.
42 * Define event to capture iscsi connection debug messages.
51 * Define event to capture iscsi session debug messages.
60 * Define event to capture iscsi error handling debug messages.
69 * Define event to capture iscsi tcp debug messages.
78 * Define event to capture iscsi sw tcp debug messages.
87 * Define event to capture iscsi transport session debug messages.
96 * Define event to capture iscsi transport connection debug messages.
|
| /kernel/linux/linux-5.10/include/trace/events/ |
| D | iscsi.h | 19 * Declare event class for iscsi debug messages.
42 * Define event to capture iscsi connection debug messages.
51 * Define event to capture iscsi session debug messages.
60 * Define event to capture iscsi error handling debug messages.
69 * Define event to capture iscsi tcp debug messages.
78 * Define event to capture iscsi sw tcp debug messages.
87 * Define event to capture iscsi transport session debug messages.
96 * Define event to capture iscsi transport connection debug messages.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | dev-kmsg | 8 Injecting messages:
20 is not possible to inject messages from userspace with the
22 the messages can always be reliably determined.
38 Messages in the record ring buffer get overwritten as whole,
39 there are never partial messages received by read().
41 In case messages get overwritten in the circular buffer while
48 messages, in case the buffer gets overwritten. And they allow
64 or write only whole variable length messages (records) that are
113 interleaved with unrelated messages, but merging the lines in
115 similar logic is used internally when messages are printed to
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | dev-kmsg | 8 Injecting messages:
20 is not possible to inject messages from userspace with the
22 the messages can always be reliably determined.
38 Messages in the record ring buffer get overwritten as whole,
39 there are never partial messages received by read().
41 In case messages get overwritten in the circular buffer while
48 messages, in case the buffer gets overwritten. And they allow
64 or write only whole variable length messages (records) that are
113 interleaved with unrelated messages, but merging the lines in
115 similar logic is used internally when messages are printed to
|
| /kernel/linux/linux-5.10/drivers/atm/ |
| D | Kconfig | 222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
226 messages is controlled by a bitmap. This may be specified as a
230 When active, these messages can have a significant impact on the
257 bool "Enable debugging messages"
260 Somewhat useful debugging messages are available. The choice of
261 messages is controlled by a bitmap. This may be specified as a
268 When active, these messages can have a significant impact on the
281 bool "Enable debugging messages"
284 Somewhat useful debugging messages are available. The choice of
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/dwc2/ |
| D | Kconfig | 68 bool "Enable Debugging Messages"
70 Say Y here to enable debugging messages in the DWC2 Driver.
73 bool "Enable Verbose Debugging Messages"
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
88 bool "Enable Debugging Messages For Periodic Transfers"
92 Say N here to disable (verbose) debugging messages to be
95 incomplete. Note that this also disables some debug messages
|
| /kernel/linux/linux-6.6/drivers/usb/dwc2/ |
| D | Kconfig | 68 bool "Enable Debugging Messages"
70 Say Y here to enable debugging messages in the DWC2 Driver.
73 bool "Enable Verbose Debugging Messages"
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
88 bool "Enable Debugging Messages For Periodic Transfers"
92 Say N here to disable (verbose) debugging messages to be
95 incomplete. Note that this also disables some debug messages
|
| /kernel/linux/linux-6.6/sound/usb/line6/ |
| D | driver.c | 43 Class for asynchronous messages.
540 /* Enable buffering of incoming messages, flush the buffer */
547 line6->messages.active = 1; in line6_hwdep_open()
548 line6->messages.nonblock = file->f_flags & O_NONBLOCK ? 1 : 0; in line6_hwdep_open()
558 line6->messages.active = 0; in line6_hwdep_release()
572 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read()
575 while (kfifo_len(&line6->messages.fifo) == 0) { in line6_hwdep_read()
576 mutex_unlock(&line6->messages.read_lock); in line6_hwdep_read()
578 if (line6->messages.nonblock) in line6_hwdep_read()
582 line6->messages.wait_queue, in line6_hwdep_read()
[all …]
|
| /kernel/linux/linux-5.10/sound/usb/line6/ |
| D | driver.c | 43 Class for asynchronous messages.
535 /* Enable buffering of incoming messages, flush the buffer */
542 line6->messages.active = 1; in line6_hwdep_open()
543 line6->messages.nonblock = file->f_flags & O_NONBLOCK ? 1 : 0; in line6_hwdep_open()
553 line6->messages.active = 0; in line6_hwdep_release()
567 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read()
570 while (kfifo_len(&line6->messages.fifo) == 0) { in line6_hwdep_read()
571 mutex_unlock(&line6->messages.read_lock); in line6_hwdep_read()
573 if (line6->messages.nonblock) in line6_hwdep_read()
577 line6->messages.wait_queue, in line6_hwdep_read()
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/pci/bt8xx/ |
| D | dst_ca.c | 46 MODULE_PARM_DESC(verbose, "verbose startup messages, default is 1 (yes)");
134 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
141 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info()
142 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info()
146 length = state->messages[5]; in ca_get_app_info()
154 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info()
157 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info()
160 state->messages[9] = str_length; in ca_get_app_info()
161 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info()
173 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
[all …]
|
| /kernel/linux/linux-6.6/drivers/media/pci/bt8xx/ |
| D | dst_ca.c | 46 MODULE_PARM_DESC(verbose, "verbose startup messages, default is 1 (yes)");
134 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
141 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info()
142 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info()
146 length = state->messages[5]; in ca_get_app_info()
154 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info()
157 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info()
160 state->messages[9] = str_length; in ca_get_app_info()
161 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info()
173 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
[all …]
|