forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2023-12-11 6778948f9de86c3cfaf36725a7c87dcff9ba247f 
 kernel/fs/pstore/Kconfig
....@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
12 config PSTORE
23 	tristate "Persistent store support"
34 	select CRYPTO if PSTORE_COMPRESS
....@@ -114,18 +115,6 @@
114115 	  When the option is enabled, pstore will log all kernel
115116 	  messages, even if no oops or panic happened.
116117 
117
-config PSTORE_CONSOLE_FORCE
118
-	bool "Log kernel console messages ignore loglevel setting"
119
-	depends on PSTORE_CONSOLE
120
-	help
121
-	  When the option is enabled, allow all kernel messages
122
-	  log to the pstore console. Enable this with a kernel bool
123
-	  parameter like "pstore_con_force=1".
124
-
125
-config PSTORE_CONSOLE_FORCE_ON
126
-	bool "Log kernel console messages ignore loglevel setting on by default"
127
-	depends on PSTORE_CONSOLE_FORCE
128
-
129118 config PSTORE_PMSG
130119 	bool "Log user space messages"
131120 	depends on PSTORE
....@@ -153,7 +142,6 @@
153142 	tristate "Log panic/oops to a RAM buffer"
154143 	depends on PSTORE
155144 	depends on HAS_IOMEM
156
-	depends on HAVE_MEMBLOCK
157145 	select REED_SOLOMON
158146 	select REED_SOLOMON_ENC8
159147 	select REED_SOLOMON_DEC8
....@@ -166,6 +154,116 @@
166154 
167155 	  For more information, see Documentation/admin-guide/ramoops.rst.
168156 
157
+config PSTORE_ZONE
158
+	tristate
159
+	depends on PSTORE
160
+	help
161
+	  The common layer for pstore/blk (and pstore/ram in the future)
162
+	  to manage storage in zones.
163
+
164
+config PSTORE_BLK
165
+	tristate "Log panic/oops to a block device"
166
+	depends on PSTORE
167
+	depends on BLOCK
168
+	depends on BROKEN
169
+	select PSTORE_ZONE
170
+	default n
171
+	help
172
+	  This enables panic and oops message to be logged to a block dev
173
+	  where it can be read back at some later point.
174
+
175
+	  For more information, see Documentation/admin-guide/pstore-blk.rst
176
+
177
+	  If unsure, say N.
178
+
179
+config PSTORE_BLK_BLKDEV
180
+	string "block device identifier"
181
+	depends on PSTORE_BLK
182
+	default ""
183
+	help
184
+	  Which block device should be used for pstore/blk.
185
+
186
+	  It accepts the following variants:
187
+	  1) <hex_major><hex_minor> device number in hexadecimal representation,
188
+	     with no leading 0x, for example b302.
189
+	  2) /dev/<disk_name> represents the device name of disk
190
+	  3) /dev/<disk_name><decimal> represents the device name and number
191
+	     of partition - device number of disk plus the partition number
192
+	  4) /dev/<disk_name>p<decimal> - same as the above, this form is
193
+	     used when disk name of partitioned disk ends with a digit.
194
+	  5) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the
195
+	     unique id of a partition if the partition table provides it.
196
+	     The UUID may be either an EFI/GPT UUID, or refer to an MSDOS
197
+	     partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero-
198
+	     filled hex representation of the 32-bit "NT disk signature", and PP
199
+	     is a zero-filled hex representation of the 1-based partition number.
200
+	  6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation
201
+	     to a partition with a known unique id.
202
+	  7) <major>:<minor> major and minor number of the device separated by
203
+	     a colon.
204
+
205
+	  NOTE that, both Kconfig and module parameters can configure
206
+	  pstore/blk, but module parameters have priority over Kconfig.
207
+
208
+config PSTORE_BLK_KMSG_SIZE
209
+	int "Size in Kbytes of kmsg dump log to store"
210
+	depends on PSTORE_BLK
211
+	default 64
212
+	help
213
+	  This just sets size of kmsg dump (oops, panic, etc) log for
214
+	  pstore/blk. The size is in KB and must be a multiple of 4.
215
+
216
+	  NOTE that, both Kconfig and module parameters can configure
217
+	  pstore/blk, but module parameters have priority over Kconfig.
218
+
219
+config PSTORE_BLK_MAX_REASON
220
+	int "Maximum kmsg dump reason to store"
221
+	depends on PSTORE_BLK
222
+	default 2
223
+	help
224
+	  The maximum reason for kmsg dumps to store. The default is
225
+	  2 (KMSG_DUMP_OOPS), see include/linux/kmsg_dump.h's
226
+	  enum kmsg_dump_reason for more details.
227
+
228
+	  NOTE that, both Kconfig and module parameters can configure
229
+	  pstore/blk, but module parameters have priority over Kconfig.
230
+
231
+config PSTORE_BLK_PMSG_SIZE
232
+	int "Size in Kbytes of pmsg to store"
233
+	depends on PSTORE_BLK
234
+	depends on PSTORE_PMSG
235
+	default 64
236
+	help
237
+	  This just sets size of pmsg (pmsg_size) for pstore/blk. The size is
238
+	  in KB and must be a multiple of 4.
239
+
240
+	  NOTE that, both Kconfig and module parameters can configure
241
+	  pstore/blk, but module parameters have priority over Kconfig.
242
+
243
+config PSTORE_BLK_CONSOLE_SIZE
244
+	int "Size in Kbytes of console log to store"
245
+	depends on PSTORE_BLK
246
+	depends on PSTORE_CONSOLE
247
+	default 64
248
+	help
249
+	  This just sets size of console log (console_size) to store via
250
+	  pstore/blk. The size is in KB and must be a multiple of 4.
251
+
252
+	  NOTE that, both Kconfig and module parameters can configure
253
+	  pstore/blk, but module parameters have priority over Kconfig.
254
+
255
+config PSTORE_BLK_FTRACE_SIZE
256
+	int "Size in Kbytes of ftrace log to store"
257
+	depends on PSTORE_BLK
258
+	depends on PSTORE_FTRACE
259
+	default 64
260
+	help
261
+	  This just sets size of ftrace log (ftrace_size) for pstore/blk. The
262
+	  size is in KB and must be a multiple of 4.
263
+
264
+	  NOTE that, both Kconfig and module parameters can configure
265
+	  pstore/blk, but module parameters have priority over Kconfig.
266
+
169267 config PSTORE_BOOT_LOG
170268 	bool "Print boot log by linux"
171269 	depends on PSTORE