Searched full:messages (Results 1 – 25 of 369) sorted by relevance
12345678910>>...15
| /Documentation/networking/ |
| 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::
|
| 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 | 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 …]
|
| D | strparser.rst | 10 The stream parser (strparser) is a utility that parses messages of an
13 kernel support for application layer messages. For instance, Kernel
14 Connection Multiplexor (KCM) uses the Stream Parser to parse messages
21 callback of a TCP socket. Messages are parsed and delivered as they are
57 and no new messages are delivered to the upper layer.
101 maximum messages size is the limit of the receive socket
108 strp_check_rcv is called to check for new messages on the socket.
137 can proceed to read the messages itself
175 call strp_pause to prevent any further messages from being
198 read multiple messages in a loop and this function allows cleanup
|
| D | batman-adv.rst | 109 All error messages, warnings and information messages are sent to the kernel
112 the files ``/var/log/kern.log`` or ``/var/log/syslog``. All batman-adv messages
113 are prefixed with "batman-adv:" So to see just these messages try::
118 see more detailed debug messages. This must be enabled when compiling the
123 Those additional debug messages can be accessed using the perf infrastructure::
132 will enable debug messages for when routes and translation table entries change.
|
| D | tls.rst | 123 Send TLS control messages
126 Other than application data, TLS has control messages such as alert
127 messages (record type 21) and handshake messages (record type 22), etc.
128 These messages can be sent over the socket by providing the TLS record type
164 Receiving TLS control messages
167 TLS control messages are passed in the userspace buffer, with message
169 returned if a control message is received. Data messages may be
215 messages are not supported.
|
| D | netconsole.rst | 26 This module logs kernel printk messages over UDP allowing debugging of
75 The remote host has several options to receive the kernel messages,
179 Custom user data can be appended to the end of messages with netconsole
193 Messages will now include this additional user data::
209 the entry will be omitted from netconsole messages::
249 Log messages are transmitted with extended metadata header in the
308 messages is high, but should have no other impact.
313 printing all messages from the sender, it is likely that you have set
315 priority messages to the console. You can change this at runtime using::
320 all kernel messages to the console. A specific value for this parameter
|
| /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
|
| D | sysfs-bus-pci-devices-aer_stats | 97 collectors) that are AER capable. These indicate the number of error messages as
99 (internally) the ERR_* messages for errors seen by the internal rootport PCI
101 messages on the PCI hierarchy originating at that root port.
107 Description: Total number of ERR_COR messages reported to rootport.
113 Description: Total number of ERR_FATAL messages reported to rootport.
119 Description: Total number of ERR_NONFATAL messages reported to rootport.
|
| D | sysfs-bus-rpmsg | 23 inbound messages arrive to this address, the rpmsg core
41 inbound messages arrive to this address, the rpmsg core
49 and it is listening for inbound messages that may be sent
65 or remote, starts listening on it for messages (and is thus
71 can start sending messages).
|
| D | sysfs-devices | 16 Or rely on the uevent messages to notify programs of
21 chain will have emitted uevent messages, so userspace
|
| /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 …]
|
| D | cec-intro.rst | 19 contraption and is an unholy mix of low and high level messages. Some
20 messages, especially those part of the HEAC protocol layered on top of
37 and monitor CEC messages.
|
| D | cec-ioc-adap-g-caps.rst | 96 - Userspace can transmit CEC messages by calling
99 messages is a prerequisite of becoming a follower. If this
101 transmits and process all CEC messages it receives.
117 - The CEC hardware can monitor all messages, not just directed and
118 broadcast messages.
|
| D | cec-ioc-dqevent.rst | 86 - Set to the number of lost messages since the filehandle was opened
88 filehandle. The messages lost are the oldest messages. So when a
91 size of the message queue guarantees that all messages received in
92 the last two seconds will be stored. Since messages should be
126 - The number of lost messages as sent by the :ref:`CEC_EVENT_LOST_MSGS <CEC-EVENT-LOST-MSGS>`
151 - Generated if one or more CEC messages were lost because the
152 application didn't dequeue CEC messages fast enough.
|
| /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 channel messages
107 All messages sent in a VMBus channel have a standard header that includes
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 channel messages:
142 1. vmbus_sendpacket(): Control-only messages and messages with
[all …]
|
| /Documentation/virt/gunyah/ |
| D | message-queue.rst | 6 It is intended for sending small control and configuration messages. Each
12 use case for message queues, and creates messages queues between itself and VMs
13 with a fixed maximum message size of 240 bytes. Longer messages require a
14 further protocol on top of the message queue messages themselves. For instance,
16 messages which are split into smaller fragments.
19 involves 2 message queues. Message queue 1 allows VM_A to send messages to VM_B.
20 Message queue 2 allows VM_B to send messages to VM_A.
|
| /Documentation/firmware-guide/acpi/ |
| 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::
|
| /Documentation/hwmon/ |
| 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
|
| /Documentation/misc-devices/ |
| 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 …]
|
| /Documentation/admin-guide/blockdev/ |
| D | floppy.rst | 49 modprobe floppy floppy="omnibook messages"
54 options floppy floppy="omnibook messages"
94 if you frequently get "Unable to allocate DMA memory" messages.
114 master arbitration error" messages from your Ethernet card (or
129 To tune the fifo threshold, switch on over/underrun messages
130 using 'floppycontrol --messages'. Then access a floppy
132 messages, then the fifo threshold is too low. Try with a
137 that you need to do 'floppycontrol --messages' every time you
187 Print debugging messages.
189 floppy=messages
[all …]
|
| /Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 67 Error messages go to console/syslog::
234 Debug messages during Boot Process
237 To activate debug messages for core code and built-in modules during
245 messages in all code run after this early_initcall via this boot
262 Debug Messages at Module Initialization Time
301 the debugfs interface if the debug messages are no longer needed::
313 // enable all the messages in file svcsock.c
316 // enable all the messages in the NFS server module
319 // enable all 12 messages in the function svc_process()
322 // disable all 12 messages in the function svc_process()
[all …]
|
| /Documentation/driver-api/nfc/ |
| D | nfc-pn544.rst | 26 HCI messages consist of an eight bit header and the message body. The
28 33. In HCI mode sent messages are tested for a correct
29 checksum. Firmware update messages have the length in the second (MSB)
|
| /Documentation/core-api/ |
| D | printk-index.rst | 9 including more or less important warnings and error messages.
11 There are monitoring tools that filter and take action based on messages
14 The kernel messages are evolving together with the code. As a result,
15 particular kernel messages are not KABI and never will be!
18 knowing what messages were updated in a particular kernel version and why.
135 It helps matching messages from the real log with printk index.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | brcm,iproc-flexrm-mbox.txt | 24 number of completion messages for which FlexRM will inject
28 which FlexRM will wait to accumulate N completion messages
30 does not get required number of completion messages in time
|
12345678910>>...15