History

kdb: Remove the misfeature 'KDBFLAGS'

Currently, 'KDBFLAGS' is an internal variable of kdb, it is combined by 'KDBDEBUG' and state flags. It will be shown only when 'KDBDEBUG' is set, and the user can define an environment variable named 'KDBFLAGS' too. These are puzzling indeed. After communication with Daniel, it seems that 'KDBFLAGS' is a misfeature. So let's replace 'KDBFLAGS' with 'KDBDEBUG' to just show the value we wrote into. After this modification, we can use `md4c1 kdb_flags` instead, to observe the state flags.

Wei Li committed 6 years ago

Commit c893de11 parent 1b310032 files · +5 −5Browse files

Showing the changes to include/linux (1 of 2 files). Show all

Unified · Split

include/linux/kdb.h+1−1
@@ -125,7 +125,7 @@ extern const char *kdb_diemsg; · 124 unmodified lines
125#define KDB_FLAG_NO_I8042 (1 << 7) /* No i8042 chip is available, do125#define KDB_FLAG_NO_I8042 (1 << 7) /* No i8042 chip is available, do
126 * not use keyboard */126 * not use keyboard */
127 127
128extern int kdb_flags; /* Global flags, see kdb_state for per cpu state */128extern unsigned int kdb_flags; /* Global flags, see kdb_state for per cpu state */
129 129
130extern void kdb_save_flags(void);130extern void kdb_save_flags(void);
131extern void kdb_restore_flags(void);131extern void kdb_restore_flags(void);