All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: 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>,
	Thomas Gleixner <tglx@kernel.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: Mon, 22 Jun 2026 16:13:37 +0200	[thread overview]
Message-ID: <0c39c459-306f-49f5-b08e-e7b9b27b6352@kernel.org> (raw)
In-Reply-To: <ajkuf08Cj0Se4P_0@U-2FWC9VHC-2323.local>


>>> This provides the basic function, and there are more todoes:
>>>   * add a ftrace mode to do function level monitoring with ftrace hook,
>>>     which is more accurate timing wise, as suggested by Steven Rostedt
>>>   * merge the dram/mmio interface to auto detect it's dram or mmio
>>>   * support runtime changing the address
>>>   * move the starting point earlier in boot phase
>>>   * monitor a whole memory region
>>>   * currently is monitoring 'changing to a value', add support
>>>     for 'changing from a value'
>>
>> That really looks more like the kind of thing you would want to carry as a OOT
>> hack for your special debugging needs :)
> 
> Thanks for the review and bringing up a very good question that whether
> the patch is worthy!
> 
> Personally, I think it is.  

The problem is that the interface is odd (kernel parameters) and the
implementation is shaky (what happens if memory does not exist? What happens if
we unplug memory?).

I don't think it's a good use of our time to polish all that up and then
maintain it.

-- 
Cheers,

David

      reply	other threads:[~2026-06-22 14:13 UTC|newest]

Thread overview: 5+ 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) [this message]

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=0c39c459-306f-49f5-b08e-e7b9b27b6352@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.