Home
last modified time | relevance | path

Searched refs:logging (Results 1 – 25 of 94) sorted by relevance

1234

/Linux-v5.4/scripts/
Dgen_compile_commands.py12 import logging
114 level = getattr(logging, log_level)
115 logging.basicConfig(format='%(levelname)s: %(message)s', level=level)
138 logging.info('Could not add line from %s: %s',
146 logging.warning(
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-log.rst4 The device-mapper logging code is used by some of the device-mapper
14 There is a generic logging interface that the device-mapper RAID
15 implementations use to perform logging operations (see
17 logging implementations are available and provide different
31 logging state survives reboots/crashes.
44 logging requests to userspace, where a daemon receives and processes the
/Linux-v5.4/tools/perf/tests/
Dattr.py10 import logging
337 level = logging.CRITICAL
340 level = logging.WARNING
342 level = logging.INFO
344 level = logging.DEBUG
346 log = logging.getLogger('test')
348 ch = logging.StreamHandler()
350 formatter = logging.Formatter('%(message)s')
/Linux-v5.4/tools/testing/selftests/tpm2/
Dtpm2_tests.py10 import logging
226 logging.basicConfig(filename='SpaceTest.log', level=logging.DEBUG)
229 log = logging.getLogger(__name__)
243 log = logging.getLogger(__name__)
253 log = logging.getLogger(__name__)
270 log = logging.getLogger(__name__)
/Linux-v5.4/Documentation/sphinx/
Dkernellog.py11 from sphinx.util import logging
12 logger = logging.getLogger('kerneldoc')
/Linux-v5.4/Documentation/networking/
Dnetconsole.txt14 problem where disk logging fails and serial consoles are impractical.
35 tgt-port port for logging agent (6666)
36 tgt-ip IP address for logging agent
37 tgt-macaddr ethernet MAC address for logging agent (broadcast)
51 It also supports logging to multiple remote agents by specifying
83 remote logging targets to be dynamically added, removed, or have their
95 To add a remote logging target (target names can be arbitrary):
183 TIP: in case the remote logging agent is on a separate LAN subnet than
193 NOTE: if you find that the remote logging agent is not receiving or
206 enable the logging of even the most critical kernel bugs. It works
/Linux-v5.4/kernel/debug/kdb/
Dkdb_io.c560 int logging, saved_loglevel = 0; in vkdb_printf() local
591 diag = kdbgetintenv("LOGGING", &logging); in vkdb_printf()
593 logging = 0; in vkdb_printf()
717 if (logging) { in vkdb_printf()
781 if (logging) in vkdb_printf()
847 if (logging) in vkdb_printf()
/Linux-v5.4/tools/thermal/tmon/
Dtmon.c39 static int logging; /* for recording thermal data to a file */ variable
139 if (!logging) in prepare_logging()
260 logging = 1; in main()
/Linux-v5.4/Documentation/filesystems/
Dxfs-delayed-logging-design.txt4 Introduction to Re-logging in XFS
7 XFS logging is a combination of logical and physical logging. Some objects,
21 "re-logging". Conceptually, this is quite simple - all it requires is that any
90 The key thing to note about the asynchronous logging combined with the
104 is the fundamental goal of delayed logging.
113 Delayed logging is the name we've given to keeping and tracking transactional
122 One of the key changes that delayed logging makes to the operation of the
128 crash is much greater than for the existing logging mechanism.
137 It should be noted that delayed logging is not an innovative new concept that
145 The fundamental requirements for delayed logging in XFS are simple:
[all …]
Drelay.txt81 tarball) provides a couple of high-level logging functions to the
124 users should make sure that all logging to the channel has
419 relay_write() or __relay_write(). relay_write() is the main logging
421 used if you might be logging from interrupt context. If you know
422 you'll never be logging from interrupt context, you can use
426 value in the fast logging path anyway, and that they'll always succeed
469 within the kernel application, such as enabling/disabling logging to
/Linux-v5.4/drivers/gpu/drm/msm/
DKconfig31 bool "MSM DRM register logging"
35 Compile in support for logging register reads/writes in a format
37 logging can be switched on via msm.reglog=y module param.
/Linux-v5.4/tools/testing/selftests/futex/functional/
DMakefile9 ../include/logging.h
/Linux-v5.4/tools/kvm/kvm_stat/
Dkvm_stat.txt23 Use batch and logging modes for scripting purposes.
69 run in logging mode (like vmstat)
/Linux-v5.4/fs/ocfs2/
DKconfig61 bool "OCFS2 logging support"
65 The ocfs2 filesystem has an extensive logging system. The system
/Linux-v5.4/include/trace/events/
Djbd2.h248 __field( unsigned long, logging )
262 __entry->logging = stats->rs_logging;
277 jiffies_to_msecs(__entry->logging),
/Linux-v5.4/drivers/message/fusion/
DKconfig112 bool "Fusion MPT logging facility"
114 This turns on a logging facility that can be used to debug a number
/Linux-v5.4/drivers/staging/vc04_services/interface/vchi/
DTODO43 5) Cleanup logging mechanism
45 The driver should probably be using the standard kernel logging mechanisms
/Linux-v5.4/samples/bpf/
Dtcp_bpf.readme19 The tcp_*_kern.o programs use special print functions to print logging
/Linux-v5.4/arch/powerpc/platforms/pseries/
DKconfig43 kernel buffer. Saying Y here will enable logging these events,
89 bool "Enable extra debug logging in platforms/pseries"
/Linux-v5.4/Documentation/s390/
Dcommon_io.rst13 Enable logging of debug information in case of ccw device timeouts.
137 The level of logging can be changed to be more or less verbose by piping to
/Linux-v5.4/drivers/acpi/apei/
DKconfig37 bool "APEI PCIe AER logging/recovering support"
/Linux-v5.4/drivers/net/ethernet/sfc/
DKconfig57 bool "Solarflare SFC9000/SFC9100-family MCDI logging support"
/Linux-v5.4/Documentation/power/regulator/
Dmachine.rst54 for use in logging and other diagnostic output. Normally the name
/Linux-v5.4/fs/verity/
DKconfig21 be hashed at once, such as: (a) auditing (logging the file's
/Linux-v5.4/drivers/gpu/drm/i915/
DKconfig.debug74 bool "Insert extra logging (very verbose) for common GEM errors"
78 Enable additional logging that may help track down the cause of

1234