Lines Matching full:buffer

30 written to the tracing ring buffer in a lockless way. To make it even
32 string, and save the raw arguments into the buffer. The format and the
33 arguments will be post processed when the ring buffer is read. This way the
62 The tracing ring buffer, by default, is a circular buffer than will
64 the ring buffer will be all the events that lead up to the crash.
68 buffer when a oops occurs to the console. This can be useful if the console
70 make sure the ring buffer is relatively small, otherwise the dumping of the
71 ring buffer may take several minutes to hours to finish. Here's an example
76 Note, the tracing buffer is made up of per CPU buffers where each of these
83 If the system memory allows it, the tracing ring buffer can be specified at
85 the memory is not modified, the tracing buffer can be retrieved from the
87 buffer.
92 advantage of using this method, is that the memory for the ring buffer will
100 reserved. As the ring buffer is broke up into per CPU buffers, the 12
102 each per CPU ring buffer will be 1.5 megabytes in size. Note, that also
103 includes meta data, so the amount of memory actually used by the ring buffer
106 Another more generic but less robust way to allocate a ring buffer mapping
119 then the ring buffer will not be from the previous boot and will be reset.
123 using a larger alignment, you may find better that the buffer is more
128 On boot up, the memory reserved for the ring buffer is validated. It will go
129 through a series of tests to make sure that the ring buffer contains valid
131 instance. If it fails any of the tests, it will clear the entire ring buffer
137 layout and mark the buffer as invalid.
144 buffer (like dump stacks), either set the instance to be the trace_printk()