From: Greg KH <gregkh@linuxfoundation.org>
To: Zane Leung <liangzhen@linux.spacemit.com>
Cc: anup.patel@oss.qualcomm.com, adrian.hunter@intel.com,
alex@ghiti.fr, alexander.shishkin@linux.intel.com,
andrew.jones@oss.qualcomm.com, anup@brainfault.org,
atish.patra@linux.dev, conor+dt@kernel.org,
devicetree@vger.kernel.org, irogers@google.com, jolsa@kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mark.rutland@arm.com,
mayuresh.chitale@oss.qualcomm.com, mchitale@gmail.com,
mingo@redhat.com, namhyung@kernel.org, palmer@dabbelt.com,
peterz@infradead.org, pjw@kernel.org, robh@kernel.org,
sunilvl@oss.qualcomm.com
Subject: Re: [PATCH v4 02/12] rvtrace: Initial implementation of driver framework
Date: Fri, 3 Jul 2026 07:41:29 +0200 [thread overview]
Message-ID: <2026070316-surgery-unneeded-bceb@gregkh> (raw)
In-Reply-To: <BDD9553502347B02+ee3069d3-eb04-4a37-b364-107cf8d0653c@linux.spacemit.com>
On Thu, Jul 02, 2026 at 04:19:53PM +0800, Zane Leung wrote:
> Hi,
>
> Based on the current framework, I am concerned about how to support RISC-V ATB and reuse the Coresight component (ETB/tmc/TPIU) in the future.
That is very vague. Please provide specific examples.
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Zane Leung <liangzhen@linux.spacemit.com>
Cc: anup.patel@oss.qualcomm.com, adrian.hunter@intel.com,
alex@ghiti.fr, alexander.shishkin@linux.intel.com,
andrew.jones@oss.qualcomm.com, anup@brainfault.org,
atish.patra@linux.dev, conor+dt@kernel.org,
devicetree@vger.kernel.org, irogers@google.com, jolsa@kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mark.rutland@arm.com,
mayuresh.chitale@oss.qualcomm.com, mchitale@gmail.com,
mingo@redhat.com, namhyung@kernel.org, palmer@dabbelt.com,
peterz@infradead.org, pjw@kernel.org, robh@kernel.org,
sunilvl@oss.qualcomm.com
Subject: Re: [PATCH v4 02/12] rvtrace: Initial implementation of driver framework
Date: Fri, 3 Jul 2026 07:41:29 +0200 [thread overview]
Message-ID: <2026070316-surgery-unneeded-bceb@gregkh> (raw)
In-Reply-To: <BDD9553502347B02+ee3069d3-eb04-4a37-b364-107cf8d0653c@linux.spacemit.com>
On Thu, Jul 02, 2026 at 04:19:53PM +0800, Zane Leung wrote:
> Hi,
>
> Based on the current framework, I am concerned about how to support RISC-V ATB and reuse the Coresight component (ETB/tmc/TPIU) in the future.
That is very vague. Please provide specific examples.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-03 5:41 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:51 [PATCH v4 00/12] Linux RISC-V trace framework and drivers Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 01/12] dt-bindings: Add RISC-V trace component bindings Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-13 17:17 ` Rob Herring (Arm)
2026-05-13 17:17 ` Rob Herring (Arm)
2026-04-29 12:51 ` [PATCH v4 02/12] rvtrace: Initial implementation of driver framework Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-07-02 8:19 ` Zane Leung
2026-07-02 8:19 ` Zane Leung
2026-07-03 5:41 ` Greg KH [this message]
2026-07-03 5:41 ` Greg KH
2026-07-03 7:32 ` Zane Leung
2026-07-03 7:32 ` Zane Leung
2026-07-03 7:41 ` Greg KH
2026-07-03 7:41 ` Greg KH
2026-07-03 9:00 ` Zane Leung
2026-07-03 9:00 ` Zane Leung
2026-07-03 9:57 ` Mark Zhuang
2026-07-03 9:57 ` Mark Zhuang
2026-07-03 12:01 ` Anup Patel
2026-07-03 12:01 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 03/12] rvtrace: Add functions to create/destroy a trace component path Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-22 19:55 ` Sergey Matyukevich
2026-05-22 19:55 ` Sergey Matyukevich
2026-04-29 12:51 ` [PATCH v4 04/12] rvtrace: Add functions to start/stop tracing on a " Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 05/12] rvtrace: Add trace encoder driver Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-22 18:46 ` Sergey Matyukevich
2026-05-22 18:46 ` Sergey Matyukevich
2026-06-02 11:29 ` Mayuresh Chitale
2026-06-02 11:29 ` Mayuresh Chitale
2026-04-29 12:51 ` [PATCH v4 06/12] rvtrace: Add function to copy into perf AUX buffer Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 07/12] rvtrace: Add trace ramsink driver Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-22 18:48 ` Sergey Matyukevich
2026-05-22 18:48 ` Sergey Matyukevich
2026-05-22 20:04 ` Sergey Matyukevich
2026-05-22 20:04 ` Sergey Matyukevich
2026-06-02 11:24 ` Mayuresh Chitale
2026-06-02 11:24 ` Mayuresh Chitale
2026-04-29 12:51 ` [PATCH v4 08/12] riscv: Enable DMA_RESTRICTED_POOL in defconfig Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 09/12] rvtrace: Add perf driver for tracing using perf tool Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-04-29 12:51 ` [PATCH v4 10/12] perf tools: Add RISC-V trace PMU record capabilities Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-20 11:30 ` Adrian Hunter
2026-05-20 11:30 ` Adrian Hunter
2026-06-02 11:31 ` Mayuresh Chitale
2026-06-02 11:31 ` Mayuresh Chitale
2026-04-29 12:51 ` [PATCH v4 11/12] perf tools: Initial support for RISC-V trace decoder Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-20 11:32 ` Adrian Hunter
2026-05-20 11:32 ` Adrian Hunter
2026-04-29 12:51 ` [PATCH v4 12/12] MAINTAINERS: Add entry for RISC-V trace framework Anup Patel
2026-04-29 12:51 ` Anup Patel
2026-05-19 8:21 ` [PATCH v4 00/12] Linux RISC-V trace framework and drivers Anup Patel
2026-05-19 8:21 ` Anup Patel
2026-05-21 8:32 ` Greg KH
2026-05-21 8:32 ` Greg KH
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=2026070316-surgery-unneeded-bceb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup.patel@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=liangzhen@linux.spacemit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mayuresh.chitale@oss.qualcomm.com \
--cc=mchitale@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sunilvl@oss.qualcomm.com \
/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.