The overall goal of this patch series is to add the ability to read
from IO mapped memory at the kdb prompt. This is something I've long
wished to have but never got around to implementing until now.

As I tried to implement this, I realized that the existing "md" code was
a bit of a mess. I spent a bunch of time cleaning up the function which
made the ability to support iomapped memory atop that pretty simple.

The cleanup code here is not quite a no-op. The "md" handling code has
some esoteric corner cases that it handled and, as part of this, I removed
some of the weird corners. I have a hard time believing anyone was relying
on these, but if you think someone is then please yell.

Also note that it would probably be good to add iomapped memory writes,
but this series is already pretty long so maybe that can be done later.


Douglas Anderson (13):
  kdb: Get rid of "minlen" for the "md" command
  kdb: Document the various "md" commands better
  kdb: Use "bool" in "md" implementation where appropriate
  kdb: Drop "offset" and "name" args to kdbgetaddrarg()
  kdb: Separate out "mdr" handling
  kdb: Remove "mdW" and "mdWcN" handling of "W" == 0
  kdb: Tweak "repeat" handling code for "mdW" and "mdWcN"
  kdb: In kdb_md() make `repeat` and `mdcount` calculations more obvious
  kdb: Use 'unsigned int' in kdb_md() where appropriate
  kdb: Replease simple_strtoul() with kstrtouint() in kdb_md()
  kdb: Abstract out parsing for mdWcN
  kdb: Add mdpW / mdpWcN commands
  kdb: Add mdi, mdiW / mdiWcN commands to show iomapped memory

 kernel/debug/kdb/kdb_bp.c      |   5 +-
 kernel/debug/kdb/kdb_bt.c      |   4 +-
 kernel/debug/kdb/kdb_main.c    | 309 +++++++++++++++++++--------------
 kernel/debug/kdb/kdb_private.h |   5 +-
 kernel/debug/kdb/kdb_support.c |  48 +++++
 5 files changed, 236 insertions(+), 135 deletions(-)

-- 
2.45.2.627.g7a2c4fd464-goog



_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to