mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>,
	Feng Tang <feng.tang@linux.alibaba.com>
Cc: 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: Wed, 24 Jun 2026 12:21:38 +0200	[thread overview]
Message-ID: <ae2281f4-197e-467a-8239-9ef087c745f2@kernel.org> (raw)
In-Reply-To: <87a4skl36t.ffs@fw13>

On 6/24/26 11:04, Thomas Gleixner wrote:
> On Tue, Jun 23 2026 at 16:26, Feng Tang wrote:
>> On Mon, Jun 22, 2026 at 04:13:37PM +0200, David Hildenbrand (Arm) wrote:
>> As discussed in RFC patch review, this debug feature is similar to
>> soft/hard lockup detector and task-hung detector, should I make the control
> 
> How is this very specialized ad hoc debug magic in any way similar to
> generally useful and just working debug mechanism like the lockup or
> hung detector? Those are just turned on, do not need a boatload of
> command line parameters and are generally useful.
> 
> Your debug magic is a workaround for a disfunctional hardware debugger,
> which means it's going to be used by three people twice a year if at
> all. Seriously?

Jup.

As a side note, I worked on hw/sw breakpoint support for VMs in QEMU in the past.

So if the problem can be reproduced in a VM, there is the possible alternative
of attaching gdb to the gdbserver in QEMU and setting hw/sw breakpoints,
including watchpoints. It's primarily focused on memory accesses, of course (not
mmio).

-- 
Cheers,

David

  reply	other threads:[~2026-06-24 10:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22  8:14 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) [this message]
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
2026-06-29  8:35                       ` Feng Tang
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=ae2281f4-197e-467a-8239-9ef087c745f2@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=ardb+git@google.com \
    --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=tglx@kernel.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

Powered by JetHome