public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, shuah@kernel.org
Subject: Re: [PATCH v3 1/2] riscv: Introduce support for hardware break/watchpoints
Date: Thu, 26 Feb 2026 08:48:21 +0000	[thread overview]
Message-ID: <20260226-sappy-name-e8aa49b42e51@spud> (raw)
In-Reply-To: <CA+Ht8=ZF2nT+gWwtEi5QdoKuOQPX5ts66WmFcF2gaoTNKT8hgw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1406 bytes --]

On Thu, Feb 26, 2026 at 08:17:47AM +0530, Himanshu Chauhan wrote:
> On Wed, Feb 25, 2026 at 2:30 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Wed, Feb 25, 2026 at 10:33:27AM +0530, Himanshu Chauhan wrote:
> > > On Tue, Feb 24, 2026 at 1:33 PM Conor Dooley <conor.dooley@microchip.com> wrote:
> > > >
> > > > On Tue, Feb 24, 2026 at 09:30:24AM +0530, Himanshu Chauhan wrote:
> > > > > Hi,
> > > > >
> > > > > On Mon, Feb 23, 2026 at 3:55 PM Conor Dooley <conor.dooley@microchip.com> wrote:
> > > > > >
> > > > > > On Mon, Feb 23, 2026 at 10:19:17AM +0530, Himanshu Chauhan wrote:
> >
> > > >
> > > > Did you miss the comment at the end about the remaining TODOs?
> > >
> > > No. As I mentioned in the cover letter, the ptrace support is not
> > > implemented here. I am actively working on it and these are
> > > implemented in ptrace work.
> > > The test is done using the perf events directly. The second patch in
> > > this patch set has the test application.
> >
> > Then the patchset should still be marked RFC, since it is not finished.
> 
> Why? I disagree.
> It enables the debug triggers support with perf. Ptrace will build upon it.

If the functions marked TODO are are not required for the patchset to be
merged, your commit message should clearly explain why these particular
functions do not need to be implemented at this stage.

Cheers,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-02-26  8:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  4:49 [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints Himanshu Chauhan
2026-02-23  4:49 ` [PATCH v3 1/2] " Himanshu Chauhan
2026-02-23 10:24   ` Conor Dooley
2026-02-24  4:00     ` Himanshu Chauhan
2026-02-24  8:03       ` Conor Dooley
2026-02-25  5:03         ` Himanshu Chauhan
2026-02-25  9:00           ` Conor Dooley
2026-02-26  2:47             ` Himanshu Chauhan
2026-02-26  8:48               ` Conor Dooley [this message]
2026-02-26  5:35             ` Anup Patel
2026-02-26  8:44               ` Conor Dooley
2026-02-26 11:40                 ` Anup Patel
2026-02-26 12:35                   ` Conor Dooley
2026-02-26 13:03                     ` Anup Patel
2026-02-26  8:52   ` Conor Dooley
2026-03-18 12:00   ` Ilya Mamay
2026-04-06  4:51     ` Himanshu Chauhan
2026-04-07 10:29       ` Ilya Mamay
2026-04-07 15:22         ` Himanshu Chauhan
2026-03-19 10:36   ` Ilya Mamay
2026-04-06  4:49     ` Himanshu Chauhan
2026-04-07 11:34       ` Ilya Mamay
2026-04-07 15:29         ` Himanshu Chauhan
2026-04-03  7:37   ` liangzhen
2026-04-06  4:48     ` Himanshu Chauhan
2026-04-07  1:47       ` liangzhen
2026-04-07  4:53         ` Himanshu Chauhan
2026-04-07 10:32           ` liangzhen
2026-02-23  4:49 ` [PATCH v3 2/2] riscv: Add breakpoint and watchpoint test for riscv Himanshu Chauhan

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=20260226-sappy-name-e8aa49b42e51@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=himanshu.chauhan@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=shuah@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