Lines Matching full:logging
72 the logging criteria. The log of accesses is placed at the top of each script
83 (refer to the \fB-e\fR option for more information). By default, logging
85 from areas mapped for both reading and writing. You can constrain logging by
87 \fIlength\fR. Logging will continue for \fIcount\fR matching accesses, with an
154 If \fIacc_types\fR is set to \fBlog\fR, logging will match all \fBPIO\fR
157 case the matching condition for logging will be restricted to the specified
192 logging, the number of logged accesses is given by \fIcount\fR +
196 Note that access logging may be combined with error injection if
198 logging and any of the other access types (\fBpio\fR, \fBdma\fR and \fBintr\fR)
334 option applies only to non-logging errdefs. If an error definition remains
440 multiple driver handles, multiple logging errdefs are registered with the
441 \fBbofi\fR driver and logging terminates when all logs become full or when
533 Continuous logging (that is, the log will wrap when full).
553 transaction logged as size 2 bytes. Without this option, the default logging
580 logging errdefs is to generate a test script for each driver access handle. Use