Received: by 2002:a05:7412:8d11:b0:fa:4934:9f with SMTP id bj17csp240461rdb; Sun, 14 Jan 2024 15:11:04 -0800 (PST) X-Google-Smtp-Source: AGHT+IEfKHf43iY05feEkugUWirQUemZp1WxhteDQXWLs0e9k9c/Uc5F7sLIvQf/0JYJwB6tqxgA X-Received: by 2002:a17:902:efc2:b0:1d4:b4a8:d3b0 with SMTP id ja2-20020a170902efc200b001d4b4a8d3b0mr5582337plb.85.1705273864517; Sun, 14 Jan 2024 15:11:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705273864; cv=none; d=google.com; s=arc-20160816; b=aOtVlSMUvsAU3kDsXi/njb2+7pdMvN9dWXWgcuPZJcve9fmPxMJZI+Glc9+IHLgQYB 7o6NyDcLHKOu0RM5f9xrw7bHRhjmG77P4yUSnkA1nqkTfh1hBxlhrOJBDIci+791LEqK Bo8+Q0vhSzy8D2WFFzjLWhSbu9GIBDMghGws9qGZNHQRBs4CUcc16wBNRUAhW3JguyT7 isvTiF2f5ZBgc0+jx+0QrQc6eIks3tXrb++DwZeiXSTrXsF/4UcYmTpJkjD64sswW7PT +04Fxb+QKstMyUdWe4X+ScyTUAe5dCUVFM/YI/lcshMmI0N150orrs6qz7IWacQVUFa7 P9VA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :subject:cc:to:from:date:dkim-signature; bh=P5DM+qZW5QsLgZHPbUwTEp8dXWTguh18fPV8+LJKv9I=; fh=mL0iTtlxaef9Y0xhUGuttLEXTcAYWHjhFgQQFI9wu68=; b=d/NHzV5fpljzAQsnIWE3Pv3OWfD3y7QKx48JRT9Dw5n1ujwK3V3N9CLbS/w3bMcJVd NIDeYQ6CJxPcaSYFFxJJicrdRsQEMb/Qm+ufmJ856HF1r3kvqA+qZG2Cex3ICiG4cGIr 0wkY8T2rD65KTpU5uFm861+fr6joJwaDhxzFzB6uXAFkJcJdaJTaVWCAy2vbB9UbXtOy e9zWsThZlZMEXrBDHSZaS1WoYqN0XOsGJsfsXxkvCuPAVQIfFQ/h9HqEu8gZSXW2H3eL 1AkAaHMXMvVyFIRadFWQ6LQe8qic0kclDehaELCkX8e7f8zo5yxvuAGIUKXVCao09auM BPeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=X497RmJp; spf=pass (google.com: domain of linux-kernel+bounces-25554-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-25554-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id d1-20020a170902aa8100b001d54e3e3bfdsi7394946plr.404.2024.01.14.15.11.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 14 Jan 2024 15:11:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-25554-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=X497RmJp; spf=pass (google.com: domain of linux-kernel+bounces-25554-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-25554-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 53980B20E9D for ; Sun, 14 Jan 2024 23:11:01 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 55C342C686; Sun, 14 Jan 2024 23:10:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="X497RmJp" Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 60BA413AE9; Sun, 14 Jan 2024 23:10:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4F6CDC433F1; Sun, 14 Jan 2024 23:10:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705273851; bh=4/J2DlKzYXXiP0hp5Un/b/TpU09wYZRPVW0CwMsJcDg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=X497RmJpq1P3lLfqgKzHzraF738L/fJ/u39IipcL386D31flZuGww0b7G/Ljj/1us lE/pjp5P7N3fcJWwJ+HGiVAPt4J+p/0K18RT3AQ54hFUl/NA9iLGSfHOwBSu1sPOQY jjh4OYlcTXPvHDIpqzm3zYB+AkSJP79WjDbImTV3KkUu243stFgAGsNNWRuGdThj2V Rk8Ex2RMG1aVCq+XAUXoRktNEDEBo1jhBalXKQcwRIcNNu1dfT2N3nKKC1m1aVWZEK eqLlEWBD15Br4mkN7qkbjWGROukFZxZEVe5du9V4UdDAyH1T8OWzzGeWSM/qTY5Gu0 LaW3DmKjUggTg== Date: Mon, 15 Jan 2024 08:10:47 +0900 From: Masami Hiramatsu (Google) To: Steven Rostedt Cc: Vincent Donnefort , linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com, kernel-team@android.com Subject: Re: [PATCH v11 4/5] Documentation: tracing: Add ring-buffer mapping Message-Id: <20240115081047.c7edecc6e6d9ee038e9474f4@kernel.org> In-Reply-To: <20240114112324.0ddbb457@rorschach.local.home> References: <20240111161712.1480333-1-vdonnefort@google.com> <20240111161712.1480333-5-vdonnefort@google.com> <20240114232643.ed27554959afea426446e9b5@kernel.org> <20240114112324.0ddbb457@rorschach.local.home> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 14 Jan 2024 11:23:24 -0500 Steven Rostedt wrote: > On Sun, 14 Jan 2024 23:26:43 +0900 > Masami Hiramatsu (Google) wrote: > > > Hi Vincent, > > > > On Thu, 11 Jan 2024 16:17:11 +0000 > > Vincent Donnefort wrote: > > > > > It is now possible to mmap() a ring-buffer to stream its content. Add > > > some documentation and a code example. > > > > > > Signed-off-by: Vincent Donnefort > > > > > > diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst > > > index 5092d6c13af5..0b300901fd75 100644 > > > --- a/Documentation/trace/index.rst > > > +++ b/Documentation/trace/index.rst > > > @@ -29,6 +29,7 @@ Linux Tracing Technologies > > > timerlat-tracer > > > intel_th > > > ring-buffer-design > > > + ring-buffer-map > > > stm > > > sys-t > > > coresight/index > > > diff --git a/Documentation/trace/ring-buffer-map.rst b/Documentation/trace/ring-buffer-map.rst > > > new file mode 100644 > > > index 000000000000..2ba7b5339178 > > > --- /dev/null > > > +++ b/Documentation/trace/ring-buffer-map.rst > > > @@ -0,0 +1,105 @@ > > > +.. SPDX-License-Identifier: GPL-2.0 > > > + > > > +================================== > > > +Tracefs ring-buffer memory mapping > > > +================================== > > > + > > > +:Author: Vincent Donnefort > > > + > > > +Overview > > > +======== > > > +Tracefs ring-buffer memory map provides an efficient method to stream data > > > +as no memory copy is necessary. The application mapping the ring-buffer becomes > > > +then a consumer for that ring-buffer, in a similar fashion to trace_pipe. > > > + > > > +Memory mapping setup > > > +==================== > > > +The mapping works with a mmap() of the trace_pipe_raw interface. > > > + > > > +The first system page of the mapping contains ring-buffer statistics and > > > +description. It is referred as the meta-page. One of the most important field of > > > +the meta-page is the reader. It contains the subbuf ID which can be safely read > > > +by the mapper (see ring-buffer-design.rst). > > > + > > > +The meta-page is followed by all the subbuf, ordered by ascendant ID. It is > > > +therefore effortless to know where the reader starts in the mapping: > > > + > > > +.. code-block:: c > > > + > > > + reader_id = meta->reader->id; > > > + reader_offset = meta->meta_page_size + reader_id * meta->subbuf_size; > > > + > > > +When the application is done with the current reader, it can get a new one using > > > +the trace_pipe_raw ioctl() TRACE_MMAP_IOCTL_GET_READER. This ioctl also updates > > > +the meta-page fields. > > > + > > > +Limitations > > > +=========== > > > +When a mapping is in place on a Tracefs ring-buffer, it is not possible to > > > +either resize it (either by increasing the entire size of the ring-buffer or > > > +each subbuf). It is also not possible to use snapshot or splice. > > > > I've played with the sample code. > > > > - "free_buffer" just doesn't work when the process is mmap the ring buffer. > > - After mmap the buffers, when the snapshot took, the IOCTL returns an error. > > > > OK, but I rather like to fail snapshot with -EBUSY when the buffer is mmaped. > > > > > + > > > +Concurrent readers (either another application mapping that ring-buffer or the > > > +kernel with trace_pipe) are allowed but not recommended. They will compete for > > > +the ring-buffer and the output is unpredictable. > > > + > > > +Example > > > +======= > > > + > > > +.. code-block:: c > > > + > > > + #include > > > + #include > > > + #include > > > + #include > > > + > > > + #include > > > + > > > + #include > > > + #include > > > + > > > + #define TRACE_PIPE_RAW "/sys/kernel/tracing/per_cpu/cpu0/trace_pipe_raw" > > > + > > > + int main(void) > > > + { > > > + int page_size = getpagesize(), fd, reader_id; > > > + unsigned long meta_len, data_len; > > > + struct trace_buffer_meta *meta; > > > + void *map, *reader, *data; > > > + > > > + fd = open(TRACE_PIPE_RAW, O_RDONLY); > > > + if (fd < 0) > > > + exit(EXIT_FAILURE); > > > + > > > + map = mmap(NULL, page_size, PROT_READ, MAP_SHARED, fd, 0); > > > + if (map == MAP_FAILED) > > > + exit(EXIT_FAILURE); > > > + > > > + meta = (struct trace_buffer_meta *)map; > > > + meta_len = meta->meta_page_size; > > > + > > > + printf("entries: %lu\n", meta->entries); > > > + printf("overrun: %lu\n", meta->overrun); > > > + printf("read: %lu\n", meta->read); > > > + printf("subbufs_touched:%lu\n", meta->subbufs_touched); > > > + printf("subbufs_lost: %lu\n", meta->subbufs_lost); > > > + printf("subbufs_read: %lu\n", meta->subbufs_read); > > > + printf("nr_subbufs: %u\n", meta->nr_subbufs); > > > + > > > + data_len = meta->subbuf_size * meta->nr_subbufs; > > > + data = mmap(NULL, data_len, PROT_READ, MAP_SHARED, fd, data_len); > > The above is buggy. It should be: > > data = mmap(NULL, data_len, PROT_READ, MAP_SHARED, fd, meta_len); > > The last parameter is where to start the mapping from, which is just > after the meta page. The code is currently starting the map far away > from that. Ah, indeed! I confirmed that fixed the bus error. Thank you! > > -- Steve > > > > + if (data == MAP_FAILED) > > > + exit(EXIT_FAILURE); > > > + > > > + if (ioctl(fd, TRACE_MMAP_IOCTL_GET_READER) < 0) > > > + exit(EXIT_FAILURE); > > > + > > > + reader_id = meta->reader.id; > > > + reader = data + meta->subbuf_size * reader_id; > > > > Also, this caused a bus error if I add below 2 lines here. > > > > printf("reader_id: %d, addr: %p\n", reader_id, reader); > > printf("read data head: %lx\n", *(unsigned long *)reader); > > > > ----- > > / # cd /sys/kernel/tracing/ > > /sys/kernel/tracing # echo 1 > events/enable > > [ 17.941894] Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and stat_runtime require the kernel parameter schedstats=enable or kernel.sched_schedstats=1 > > /sys/kernel/tracing # > > /sys/kernel/tracing # echo 1 > buffer_percent > > /sys/kernel/tracing # /mnt/rbmap2 > > entries: 245291 > > overrun: 203741 > > read: 0 > > subbufs_touched:2041 > > subbufs_lost: 1688 > > subbufs_read: 0 > > nr_subbufs: 355 > > reader_id: 1, addr: 0x7f0cde51a000 > > Bus error > > ----- > > > > Is this expected behavior? how can I read the ring buffer? > > > > Thank you, > > > > > + > > > + munmap(data, data_len); > > > + munmap(meta, meta_len); > > > + close (fd); > > > + > > > + return 0; > > > + } > > > -- > > > 2.43.0.275.g3460e3d667-goog > > > > > > > > -- Masami Hiramatsu (Google)