From: Thomas Gleixner <tglx@kernel.org>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
paulmck@kernel.org, Douglas Anderson <dianders@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb+git@google.com>
Subject: Re: [PATCH v1] kernel: add a simple timer based software watchpoint
Date: Fri, 26 Jun 2026 17:31:09 +0200 [thread overview]
Message-ID: <87cxxdiaiq.ffs@fw13> (raw)
In-Reply-To: <aj6NteGa2Biii_k1@U-2FWC9VHC-2323.local>
On Fri, Jun 26 2026 at 22:33, Feng Tang wrote:
> As HW jtag debugger is expensive and not generally available for
> software developer, also many production hardware don't have their
> jtag interface open for security reason, I think monitoring the
> abnormal changes to dram/mmio is convenient for debugging memory
> corruption issues. Could you help to give some suggestion on
> how to redesign this? Many thanks!
If you can reproduce in a VM, you have qemu + gdb, which allows you
even to debug the BIOS.
If it's bare metal you can use kgdb or perf events. All of those allow
you to set watchpoints, data breakpoints etc.
If you end up with no hit on a watch/breakpoint then you're lost in that
case as you can't debug the BIOS w/o a hardware debugger, but that's not
any different than with your magic hack.
The tools are all there you just have to use them correctly, no?
Thanks,
tglx
next prev parent reply other threads:[~2026-06-26 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:14 [PATCH v1] kernel: add a simple timer based software watchpoint Feng Tang
2026-06-22 8:42 ` David Hildenbrand (Arm)
2026-06-22 10:53 ` Thomas Gleixner
2026-06-22 12:45 ` Feng Tang
2026-06-22 14:13 ` David Hildenbrand (Arm)
2026-06-23 8:26 ` Feng Tang
2026-06-24 9:04 ` Thomas Gleixner
2026-06-24 10:21 ` David Hildenbrand (Arm)
2026-06-24 11:16 ` Feng Tang
2026-06-24 11:12 ` Feng Tang
2026-06-25 21:30 ` Thomas Gleixner
2026-06-26 1:56 ` Feng Tang
2026-06-26 2:57 ` Feng Tang
2026-06-26 6:50 ` Feng Tang
2026-06-26 9:16 ` Thomas Gleixner
2026-06-26 14:33 ` Feng Tang
2026-06-26 15:31 ` Thomas Gleixner [this message]
2026-06-23 17:26 ` Julian Braha
2026-06-24 2:43 ` Feng Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cxxdiaiq.ffs@fw13 \
--to=tglx@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb+git@google.com \
--cc=david@kernel.org \
--cc=dianders@chromium.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox