From: Bo Gan <ganboing@gmail.com>
To: Mayuresh Chitale <mchitale@ventanamicro.com>,
Bo Gan <ganboing@gmail.com>
Cc: Anup Patel <apatel@ventanamicro.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Greg KH <gregkh@linuxfoundation.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Alexandre Ghiti <alex@ghiti.fr>,
Atish Patra <atish.patra@linux.dev>,
Peter Zijlstra <peterz@infradead.org>,
Anup Patel <anup@brainfault.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Jiri Olsa <jolsa@kernel.org>,
Mayuresh Chitale <mchitale@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-riscv@lists.infradead.org,
Andrew Jones <ajones@ventanamicro.com>,
Liang Kan <kan.liang@linux.intel.com>
Subject: Re: [PATCH 07/11] rvtrace: Add trace ramsink driver
Date: Fri, 10 Oct 2025 17:41:58 -0700 [thread overview]
Message-ID: <3af020da-f61b-4a32-8209-227b8fe58a78@gmail.com> (raw)
In-Reply-To: <CAN37VV5J2+gzpraR2NhaJBNfQ3dPsr-72Mmg03+ykcLoouZ8_Q@mail.gmail.com>
On 10/8/25 03:35, Mayuresh Chitale wrote:
>
>
> On Tue, Oct 7, 2025 at 1:21 PM Bo Gan <ganboing@gmail.com <mailto:ganboing@gmail.com>> wrote:
> >
> > On 10/1/25 23:07, Anup Patel wrote:
> > > From: Mayuresh Chitale <mchitale@ventanamicro.com <mailto:mchitale@ventanamicro.com>>
> > >
> > > Add initial implementation of RISC-V trace ramsink driver. The ramsink
> > > is defined in the RISC-V Trace Control Interface specification.
> > >
> > > Co-developed-by: Anup Patel <apatel@ventanamicro.com <mailto:apatel@ventanamicro.com>>
> > > Signed-off-by: Anup Patel <apatel@ventanamicro.com <mailto:apatel@ventanamicro.com>>
> > > Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com <mailto:mchitale@ventanamicro.com>>
> > > ---
> > > drivers/hwtracing/rvtrace/Kconfig | 8 +
> > > drivers/hwtracing/rvtrace/Makefile | 1 +
> > > drivers/hwtracing/rvtrace/rvtrace-ramsink.c | 198 ++++++++++++++++++++
> > > 3 files changed, 207 insertions(+)
> > > create mode 100644 drivers/hwtracing/rvtrace/rvtrace-ramsink.c
> > >
> > > diff --git a/drivers/hwtracing/rvtrace/Kconfig b/drivers/hwtracing/rvtrace/Kconfig
> > > index ba35c05f3f54..aef7e9989165 100644
> > > --- a/drivers/hwtracing/rvtrace/Kconfig
> > > +++ b/drivers/hwtracing/rvtrace/Kconfig
> > > @@ -21,3 +21,11 @@ config RVTRACE_ENCODER
> > > default y
> > > help
> > > This driver provides support for RISC-V Trace Encoder component.
> > > +
> > > +config RVTRACE_RAMSINK
> > > + tristate "RISC-V Trace Ramsink driver"
> > > + depends on RVTRACE
> > > + default y
> > > + help
> > > + This driver provides support for Risc-V E-Trace Ramsink
> > > + component.
> > > diff --git a/drivers/hwtracing/rvtrace/Makefile b/drivers/hwtracing/rvtrace/Makefile
> > > index f320693a1fc5..122e575da9fb 100644
> > > --- a/drivers/hwtracing/rvtrace/Makefile
> > > +++ b/drivers/hwtracing/rvtrace/Makefile
> > > @@ -3,3 +3,4 @@
> > > obj-$(CONFIG_RVTRACE) += rvtrace.o
> > > rvtrace-y := rvtrace-core.o rvtrace-platform.o
> > > obj-$(CONFIG_RVTRACE_ENCODER) += rvtrace-encoder.o
> > > +obj-$(CONFIG_RVTRACE_RAMSINK) += rvtrace-ramsink.o
> > > diff --git a/drivers/hwtracing/rvtrace/rvtrace-ramsink.c b/drivers/hwtracing/rvtrace/rvtrace-ramsink.c
> > > new file mode 100644
> > > index 000000000000..7bd0cf1e4dfd
> > > --- /dev/null
> > > +++ b/drivers/hwtracing/rvtrace/rvtrace-ramsink.c
> > > @@ -0,0 +1,198 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > +/*
> > > + * Copyright (c) 2025 Ventana Micro Systems Inc.
> > > + */
> > > +
> > > +#include <linux/device.h>
> > > +#include <linux/io.h>
> > > +#include <linux/of.h>
> > > +#include <linux/of_graph.h>
> > > +#include <linux/platform_device.h>
> > > +#include <linux/property.h>
> > > +#include <linux/dma-mapping.h>
> > > +#include <linux/rvtrace.h>
> > > +#include <linux/types.h>
> > > +#include <linux/sizes.h>
> > > +
> > > +#define RVTRACE_RAMSINK_STARTLOW_OFF 0x010
> > > +#define RVTRACE_RAMSINK_STARTHIGH_OFF 0x014
> > > +#define RVTRACE_RAMSINK_LIMITLOW_OFF 0x018
> > > +#define RVTRACE_RAMSINK_LIMITHIGH_OFF 0x01c
> > > +#define RVTRACE_RAMSINK_WPLOW_OFF 0x020
> > > +#define RVTRACE_RAMSINK_WPHIGH_OFF 0x024
> > > +#define RVTRACE_RAMSINK_RPLOW_OFF 0x028
> > > +#define RVTRACE_RAMSINK_RPHIGH_OFF 0x02c
> > > +
> > > +struct rvtrace_ramsink_priv {
> > > + size_t size;
> > > + void *va;
> > > + dma_addr_t start;
> > > + dma_addr_t end;
> > > + /* WP from prev iteration */
> > > + dma_addr_t prev_head;
> > > +};
> > > +
> > > +struct trace_buf {
> > > + void *base;
> > > + size_t size;
> > > + int cur, len;
> > > +};
> > > +
> > > +static void tbuf_to_pbuf_copy(struct trace_buf *src, struct trace_buf *dst)
> > > +{
> > > + int bytes_dst, bytes_src, bytes;
> > > + void *dst_addr, *src_addr;
> > > +
> > > + while (src->size) {
> > > + src_addr = src->base + src->cur;
> > > + dst_addr = dst->base + dst->cur;
> > > +
> > > + if (dst->len - dst->cur < src->size)
> > > + bytes_dst = dst->len - dst->cur;
> > > + else
> > > + bytes_dst = src->size;
> > > + if (src->len - src->cur < src->size)
> > > + bytes_src = src->len - src->cur;
> > > + else
> > > + bytes_src = src->size;
> > > + bytes = bytes_dst < bytes_src ? bytes_dst : bytes_src;
> > > + memcpy(dst_addr, src_addr, bytes);
> > > + dst->cur = (dst->cur + bytes) % dst->len;
> > > + src->cur = (src->cur + bytes) % src->len;
> > > + src->size -= bytes;
> > > + }
> > > +}
> > > +
> > > +static size_t rvtrace_ramsink_copyto_auxbuf(struct rvtrace_component *comp,
> > > + struct rvtrace_perf_auxbuf *buf)
> > > +{
> > > + struct rvtrace_ramsink_priv *priv = dev_get_drvdata(&comp->dev);
> > > + struct trace_buf src, dst;
> > > + u32 wp_low, wp_high;
> > > + u64 buf_cur_head;
> > > + size_t size;
> > > +
> > > + wp_low = rvtrace_read32(comp->pdata, RVTRACE_RAMSINK_WPLOW_OFF);
> > > + wp_high = rvtrace_read32(comp->pdata, RVTRACE_RAMSINK_WPHIGH_OFF);
> > > + buf_cur_head = (u64)(wp_high) << 32 | wp_low;
> > > +
> > > + if (buf_cur_head == priv->prev_head)
> > > + return 0;
> > > +
> > > + dst.base = buf->base;
> > > + dst.len = buf->length;
> > > + dst.cur = buf->pos;
> > > + dst.size = 0;
> > > +
> > > + src.base = priv->va;
> > > + src.len = priv->end - priv->start;
> > > + if (buf_cur_head > priv->prev_head) {
> > > + src.size = buf_cur_head - priv->prev_head;
> > > + } else {
> > > + src.size = priv->end - priv->prev_head;
> > > + src.size += buf_cur_head - priv->start;
> > > + }
> > > +
> > > + src.cur = buf_cur_head - priv->start;
> > > + size = src.size;
> > > + tbuf_to_pbuf_copy(&src, &dst);
> > > + buf->pos = dst.cur;
> > > + priv->prev_head = buf_cur_head;
> > > +
> > > + return size;
> > > +}
> > > +
> > > +static int rvtrace_ramsink_setup(struct rvtrace_component *comp)
> > > +{
> > > + struct rvtrace_ramsink_priv *priv;
> > > +
> > > + priv = devm_kzalloc(&comp->dev, sizeof(*priv), GFP_KERNEL);
> > > + if (!priv)
> > > + return -ENOMEM;
> > > + dev_set_drvdata(&comp->dev, priv);
> > > +
> > > + priv->size = SZ_4M;
> > Can we make this size dynamically determined? 4M seems inadequate. This is
> > exceedingly so if the RAM sink is linked to a funnel, where you can have
> > many harts dumping traces into this sink.
> >
> > > + priv->va = dma_alloc_coherent(&comp->dev, priv->size, &priv->start, GFP_KERNEL);
> > > + if (!priv->va)
> > > + return -ENOMEM;
> > > + priv->end = priv->start + priv->size;
> > > + priv->prev_head = priv->start;
> > > +
> > > + /* Setup ram sink addresses */
> > > + rvtrace_write32(comp->pdata, lower_32_bits(priv->start), RVTRACE_RAMSINK_STARTLOW_OFF);
> > > + rvtrace_write32(comp->pdata, upper_32_bits(priv->start), RVTRACE_RAMSINK_STARTHIGH_OFF);
> > > + rvtrace_write32(comp->pdata, lower_32_bits(priv->start), RVTRACE_RAMSINK_WPLOW_OFF);
> > > + rvtrace_write32(comp->pdata, upper_32_bits(priv->start), RVTRACE_RAMSINK_WPHIGH_OFF);
> > > + /* Limit address needs to be set to end - 4 so that HW doesn't cause an overflow. */> + rvtrace_write32(comp->pdata, lower_32_bits(priv->end - 0x4), RVTRACE_RAMSINK_LIMITLOW_OFF);
> > Should not hardcode 4 as the trace write width. Control Interface Spec
> > chapter 7.1 has the proper instruction on how to probe for this width:
> >
> > "Not every value may be settable in trRamStart/Limit registers. Value
> > written may be trimmed (for example aligned on a particular 2^N boundary)
> > and a trace tool should verify values being written"
> >
> Thanks for the comments. I will incorporate those in v2.
@Mayuresh, I went over the spec again. I don't see the handling off wrap.
You need to detect if the buffer has wrapped around by testing bit 0 of
trRamWPLow. So:
a. trRamWPLow needs masking bit 0 before being used as address to read
trace data.
b. If wrapped, then the trace buffer is actually scattered in two parts:
[WP, Limit + width) and [Start, WP). During copying, you need to use
the right portion of the trace buffer.
ref: https://github.com/ganboing/riscv-trace-umd/blob/master/rvtrace/funnel.py#L260
BTW, again your mail wasn't delivered to the mailing-list for some reason
Please check: I couldn't find your name on
https://lists.infradead.org/pipermail/linux-riscv/2025-October/thread.html
https://lore.kernel.org/all/20251002060732.100213-1-apatel@ventanamicro.com/
>
> > > + rvtrace_write32(comp->pdata, upper_32_bits(priv->end), RVTRACE_RAMSINK_LIMITHIGH_OFF);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static void rvtrace_ramsink_cleanup(struct rvtrace_component *comp)
> > > +{
> > > + struct rvtrace_ramsink_priv *priv = dev_get_drvdata(&comp->dev);
> > > +
> > > + dma_free_coherent(&comp->dev, priv->size, priv->va, priv->start);
> > > +}
> > > +
> > > +static int rvtrace_ramsink_probe(struct rvtrace_component *comp)
> > > +{
> > > + int ret;
> > > +
> > > + ret = rvtrace_ramsink_setup(comp);
> > > + if (ret)
> > > + return dev_err_probe(&comp->dev, ret, "failed to setup ramsink.\n");
> > > +
> > > + ret = rvtrace_enable_component(comp);
> > > + if (ret)
> > > + return dev_err_probe(&comp->dev, ret, "failed to enable ramsink.\n");
> > > +
> > > + return ret;
> > > +}
> > > +
> > > +static void rvtrace_ramsink_remove(struct rvtrace_component *comp)
> > > +{
> > > + int ret;
> > > +
> > > + ret = rvtrace_disable_component(comp);
> > > + if (ret)
> > > + dev_err(&comp->dev, "failed to disable ramsink.\n");
> > > +
> > > + rvtrace_ramsink_cleanup(comp);
> > > +}
> > > +
> > > +static struct rvtrace_component_id rvtrace_ramsink_ids[] = {
> > > + { .type = RVTRACE_COMPONENT_TYPE_RAMSINK,
> > > + .version = rvtrace_component_mkversion(1, 0), },
> > > + {},
> > > +};
> > > +
> > > +static struct rvtrace_driver rvtrace_ramsink_driver = {
> > > + .id_table = rvtrace_ramsink_ids,
> > > + .copyto_auxbuf = rvtrace_ramsink_copyto_auxbuf,
> > > + .probe = rvtrace_ramsink_probe,
> > > + .remove = rvtrace_ramsink_remove,
> > > + .driver = {
> > > + .name = "rvtrace-ramsink",
> > > + },
> > > +};
> > > +
> > > +static int __init rvtrace_ramsink_init(void)
> > > +{
> > > + return rvtrace_register_driver(&rvtrace_ramsink_driver);
> > > +}
> > > +
> > > +static void __exit rvtrace_ramsink_exit(void)
> > > +{
> > > + rvtrace_unregister_driver(&rvtrace_ramsink_driver);
> > > +}
> > > +
> > > +module_init(rvtrace_ramsink_init);
> > > +module_exit(rvtrace_ramsink_exit);
> > > +
> > > +/* Module information */
> > > +MODULE_AUTHOR("Mayuresh Chitale <mchitale@ventanamicro.com <mailto:mchitale@ventanamicro.com>>");
> > > +MODULE_DESCRIPTION("RISC-V Trace Ramsink Driver");
> > > +MODULE_LICENSE("GPL");
> >
> > Bo
Bo
next prev parent reply other threads:[~2025-10-11 0:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 6:07 [PATCH 00/11] Linux RISC-V trace framework and drivers Anup Patel
2025-10-02 6:07 ` [PATCH 01/11] dt-bindings: Add RISC-V trace component bindings Anup Patel
2025-10-02 19:25 ` Rob Herring
2025-10-09 13:34 ` Anup Patel
2025-10-02 6:07 ` [PATCH 02/11] rvtrace: Initial implementation of driver framework Anup Patel
2025-10-11 1:07 ` Bo Gan
2025-10-30 8:37 ` Anup Patel
2025-10-02 6:07 ` [PATCH 03/11] rvtrace: Add functions to create/destroy a trace component path Anup Patel
2025-10-02 6:07 ` [PATCH 04/11] rvtrace: Add functions to start/stop tracing on a " Anup Patel
2025-10-08 9:13 ` Bo Gan
2025-10-13 3:43 ` Anup Patel
2025-10-13 4:52 ` Bo Gan
2025-10-14 8:10 ` Mayuresh Chitale
2025-10-14 8:59 ` Bo Gan
2025-10-02 6:07 ` [PATCH 05/11] rvtrace: Add trace encoder driver Anup Patel
2025-10-07 7:09 ` Bo Gan
2025-10-08 8:48 ` Bo Gan
[not found] ` <CAN37VV7uBkRzYsQcgGtw_iFg=za91OH7_1OSJ+b8eeuCzL5iDw@mail.gmail.com>
2025-10-08 9:51 ` Bo Gan
2025-10-02 6:07 ` [PATCH 06/11] rvtrace: Add function to copy into perf AUX buffer Anup Patel
2025-10-02 6:07 ` [PATCH 07/11] rvtrace: Add trace ramsink driver Anup Patel
2025-10-07 7:49 ` Bo Gan
[not found] ` <CAN37VV5J2+gzpraR2NhaJBNfQ3dPsr-72Mmg03+ykcLoouZ8_Q@mail.gmail.com>
2025-10-11 0:41 ` Bo Gan [this message]
2025-10-13 13:38 ` Mayuresh Chitale
2025-10-02 6:07 ` [PATCH 08/11] rvtrace: Add perf driver for tracing using perf tool Anup Patel
2025-10-02 6:07 ` [PATCH 09/11] perf tools: Add RISC-V trace PMU record capabilities Anup Patel
2025-10-02 6:07 ` [PATCH 10/11] perf tools: Initial support for RISC-V trace decoder Anup Patel
2025-10-02 6:07 ` [PATCH 11/11] MAINTAINERS: Add entry for RISC-V trace framework and drivers Anup Patel
2025-10-02 6:26 ` [PATCH 00/11] Linux " Greg KH
2025-10-02 6:39 ` Anup Patel
2025-10-02 6:44 ` Greg KH
2025-10-02 20:42 ` Bo Gan
2025-10-03 4:15 ` Anup Patel
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=3af020da-f61b-4a32-8209-227b8fe58a78@gmail.com \
--to=ganboing@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atish.patra@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchitale@gmail.com \
--cc=mchitale@ventanamicro.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).