| /linux/net/mac80211/ |
| H A D | Kconfig | 98 bool "Trace all mac80211 debug messages"
103 collect all debugging messages, independent of
106 The overhead in this option is that all the messages
137 many debugging messages. It should not be selected
138 on production systems as some of the messages are
148 debugging messages for the managed-mode MLME. It
150 of the messages are remotely triggerable.
159 debugging messages for station addition/removal.
171 of the messages are remotely triggerable.
180 very verbose OCB debugging messages. It should not
[all …]
|
| /linux/arch/arm/ |
| H A D | Kconfig.debug | 94 bool "Verbose user fault messages"
129 bool "Kernel low-level debugging messages via Alpine UART0"
259 bool "Kernel low-level debugging messages via BCM KONA UART"
291 messages to appear over the UART, select this option.
294 bool "Kernel low-level debugging messages via UART1"
301 bool "Kernel low-level debugging messages via UART2"
324 bool "Kernel low-level debugging messages via footbridge serial port"
331 bool "Kernel low-level debugging messages via Digicolor UA0"
338 bool "Kernel low-level debugging messages via ep93xx UART"
346 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
|
| /linux/Documentation/networking/ |
| H A 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 …]
|
| H A 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::
|
| H A D | ipvs-sysctl.rst | 79 - 0 - transmission error messages (default)
80 - 1 - non-fatal error messages
95 Higher debugging levels include the messages for lower debugging
97 messages. Thus, logging becomes more and more verbose the higher
200 It controls sending icmp error messages (ICMP_DEST_UNREACH)
239 new sync message. It can be used to avoid sync messages for the
251 to protect against loss of sync messages. The range of the
256 Hard limit for queued sync messages that are not sent yet. It
258 number of messages. It will protect us from allocating large
311 synchronisation messages.
[all …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A 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 …]
|
| /linux/drivers/staging/nvec/ |
| H A 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
|
| /linux/include/trace/events/ |
| H A 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.
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | uncore-interconnect.json | 675 "BriefDescription": "Messages sent direct to the Intel UPI",
2448 "BriefDescription": "CBox AD Credits Empty : VNA Messages",
2454 …"PublicDescription": "CBox AD Credits Empty : VNA Messages : No credits available to send to Cbox …
2690 …0 : REQ on AD : VN0 message requested but lost arbitration : Home (REQ) messages on AD. REQ is ge…
2701 …RSP on AD : VN0 message requested but lost arbitration : Response (RSP) messages on AD. RSP packe…
2712 …: SNP on AD : VN0 message requested but lost arbitration : Snoops (SNP) messages on AD. SNP is us…
2723 …0 message requested but lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is ge…
2734 … on BL : VN0 message requested but lost arbitration : Non-Coherent Standard (NCS) messages on BL.",
2745 …RSP on BL : VN0 message requested but lost arbitration : Response (RSP) messages on BL. RSP packet…
2756 …on BL : VN0 message requested but lost arbitration : Data Response (WB) messages on BL. WB is gen…
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | uncore-interconnect.json | 675 "BriefDescription": "Messages sent direct to the Intel UPI",
2448 "BriefDescription": "CBox AD Credits Empty : VNA Messages",
2454 …"PublicDescription": "CBox AD Credits Empty : VNA Messages : No credits available to send to Cbox …
2690 …0 : REQ on AD : VN0 message requested but lost arbitration : Home (REQ) messages on AD. REQ is ge…
2701 …RSP on AD : VN0 message requested but lost arbitration : Response (RSP) messages on AD. RSP packe…
2712 …: SNP on AD : VN0 message requested but lost arbitration : Snoops (SNP) messages on AD. SNP is us…
2723 …0 message requested but lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is ge…
2734 … on BL : VN0 message requested but lost arbitration : Non-Coherent Standard (NCS) messages on BL.",
2745 …RSP on BL : VN0 message requested but lost arbitration : Response (RSP) messages on BL. RSP packet…
2756 …on BL : VN0 message requested but lost arbitration : Data Response (WB) messages on BL. WB is gen…
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| /linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_vf_mbx.c | 87 * is a possibility of a malicious VF transmitting too many MBX messages to the
92 * messages within the mailbox queue while looking for a malicious VF.
124 * the max messages check must be ignored in the algorithm
173 * Condition-2: If the maximum messages serviced in the mailbox for a in ice_mbx_traverse()
175 * to check if the number of messages processed is equal to it. If not in ice_mbx_traverse()
176 * check if the number of messages processed is greater than or equal in ice_mbx_traverse()
192 * This function tracks the number of asynchronous messages
194 * the permissible number of messages to send.
227 * asynchronous messages sent by VFs. On capturing the snapshot
228 * and depending on whether the number of pending messages in that
[all …]
|
| /linux/sound/usb/line6/ |
| H A 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 …]
|
| /linux/drivers/media/pci/bt8xx/ |
| H A 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 …]
|
| /linux/drivers/usb/dwc2/ |
| H A 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
|
| /linux/tools/testing/selftests/ipc/ |
| H A D | msgque.c | 32 struct msg1 *messages; member
67 if (msgsnd(msgque->msq_id, &msgque->messages[i].mtype, in restore_queue()
68 msgque->messages[i].msize, IPC_NOWAIT) != 0) { in restore_queue()
97 if (ret != msgque->messages[cnt].msize) { in check_and_destroy_queue()
99 msgque->messages[cnt].msize); in check_and_destroy_queue()
103 if (message.mtype != msgque->messages[cnt].mtype) { in check_and_destroy_queue()
108 if (memcmp(message.mtext, msgque->messages[cnt].mtext, ret)) { in check_and_destroy_queue()
151 msgque->messages = malloc(sizeof(struct msg1) * ds.msg_qnum); in dump_queue()
152 if (msgque->messages == NULL) { in dump_queue()
162 ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype, in dump_queue()
[all …]
|
| /linux/arch/sh/kernel/cpu/sh2/ |
| H A D | smp-j2.c | 25 unsigned messages, i; in j2_ipi_interrupt_handler() local
27 do messages = *pmsg; in j2_ipi_interrupt_handler()
28 while (cmpxchg(pmsg, messages, 0) != messages); in j2_ipi_interrupt_handler()
30 if (!messages) return IRQ_NONE; in j2_ipi_interrupt_handler()
33 if (messages & (1U<<i)) in j2_ipi_interrupt_handler()
114 /* There is only one IPI interrupt shared by all messages, so in j2_send_ipi()
|
| /linux/drivers/usb/serial/ |
| H A D | keyspan_usa49msg.h | 41 Buffer formats for RX/TX data messages are not defined by
44 USB OUT (host -> USAxx, transmit) messages contain a
52 USB IN (USAxx -> host, receive) messages begin with a status
83 messages, but the but the PARITY/FRAMING/BREAK bits
84 only appear in (b) format messages.
96 until a control messages with enablePort is sent
117 Host->device messages sent on the global control endpoint:
208 during normal operation, status messages are returned
210 circumstances (e.g. Windows), status messages from the
214 this message, and then suppress further status messages;
[all …]
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | debug.rst | 14 config option is not set, the debug messages are not even built into the kernel.
19 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
23 the debug messages.
58 The "debug_level" is a mask that selects different types of messages, e.g.,
59 those related to initialization, method execution, informational messages, etc.
122 Enable all ACPI hardware-related messages::
126 Enable all ACPI_DB_INFO messages after boot::
|
| /linux/Documentation/hwmon/ |
| H A D | submitting-patches.rst | 19 errors, no warnings, and few if any check messages. If there are any
20 messages, please be prepared to explain.
26 * If your patch generates checkpatch errors, warnings, or check messages,
87 * Limit the number of kernel log messages. In general, your driver should not
90 that kernel error log messages not only fill up the kernel log, but also are
98 * If the driver has a detect function, make sure it is silent. Debug messages
99 and messages printed after a successful detection are acceptable, but it
100 must not print messages such as "Chip XXX not found/supported".
103 address if a chip is detected on that address. Unnecessary messages will just
|
| /linux/fs/jffs2/ |
| H A D | debug.h | 29 * By defining/undefining the below macros one may select debugging messages
51 * Dx() are mainly used for debugging messages, they must go away and be
73 /* The prefixes of JFFS2 messages */
96 * We split our debugging messages on several parts, depending on the JFFS2
99 /* Read inode debugging messages */
111 /* Fragtree build debugging messages */
123 /* Directory entry list manilulation debugging messages */
130 /* Print the messages about manipulating node_refs */
144 /* Summary debugging messages */
151 /* File system build messages */
|
| /linux/drivers/i2c/busses/ |
| H A D | i2c-cros-ec-tunnel.c | 41 * @i2c_msgs: The i2c messages to read
42 * @num: The number of i2c messages.
44 * Returns the number of bytes the messages will take up.
67 * @i2c_msgs: The i2c messages to read.
68 * @num: The number of i2c messages.
110 * @i2c_msgs: The i2c messages to fill up.
111 * @num: The number of i2c messages expected.
134 * @i2c_msgs: The i2c messages to fill up.
135 * @num: The number of i2c messages; will be modified to include the actual
157 /* Other side could send us back fewer messages, but not more */ in ec_i2c_parse_response()
[all …]
|
| /linux/Documentation/misc-devices/ |
| H A D | ibmvmc.rst | 50 The set of HMC to hypervisor messages supported by the management
77 sending/receiving any of the protocol messages.
79 This driver also utilizes Transport Event CRQs. CRQ messages are sent
82 Two new classes of CRQ messages are introduced for the VMC device. VMC
83 Administrative messages are used for each partition using the VMC to
84 communicate capabilities to their partner. HMC Interface messages are used
85 for the actual flow of HMC messages between the management partition and
86 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer,
154 hypervisor receives this information, it sends Add Buffer messages to the
178 exchange HMC messages via the Signal VMC message and RDMA operations. When
[all …]
|
| /linux/fs/ubifs/ |
| H A D | debug.h | 170 /* General messages */
172 /* Additional journal messages */
176 /* Additional TNC messages */
180 /* Additional lprops messages */
182 /* Additional LEB find messages */
184 /* Additional mount messages */
188 /* Additional I/O messages */
190 /* Additional commit messages */
192 /* Additional budgeting messages */
194 /* Additional log messages */
[all …]
|
| /linux/include/linux/ |
| H A D | ipmi_smi.h | 35 * waiting for watchdog timeouts, commands and/or messages.
42 * SMI messages
44 * When communicating with an SMI, messages come in two formats:
64 * With normal messages, only commands are sent and only responses are
84 * IPMB messages can be commands and responses in both directions.
95 * Messages to/from the lower layer. The smi interface will take one
104 * asynchronous data and messages and request them from the
142 * The low-level interface cannot start sending messages to
183 * interface watch for received messages and watchdog
194 * Called when flushing all pending messages.
[all …]
|