tracing: Cleanup and simplify the persistent ring buffer for 6.15
Subsystems (4)
Steven Rostedt
maintainercover tracing: Cleanup and simplify the persistent ring buffer for 6.15
Persistent buffer cleanups and simplifications for v6.15:
It was mistaken that the physical memory returned from "reserve_mem" had to be vmap()'d to get to it from a virtual address. But reserve_mem already maps the memory to the virtual address of the kernel so a simple phys_to_virt() can be used to get to the virtual address from the physical memory returned by "reserve_mem". With this new found knowledge, the code can be cleaned up and simplified.
- Enforce that the persistent memory is page aligned
As the buffers using the persistent memory are all going to be mapped via pages, make sure that the memory given to the tracing infrastructure is page aligned. If it is not, it will print a warning and fail to map the buffer.
- Use phys_to_virt() to get the virtual address from reserve_mem
Instead of calling vmap() on the physical memory returned from "reserve_mem", use phys_to_virt() instead.
As the memory returned by "memmap" or any other means where a physical address is given to the tracing infrastructure, it still needs to be vmap(). Since this memory can never be returned back to the buddy allocator nor should it ever be memmory mapped to user space, flag this buffer and up the ref count. The ref count will keep it from ever being freed, and the flag will prevent it from ever being memory mapped to user space.
- Use vmap_page_range() for memmap virtual address mapping
For the memmap buffer, instead of allocating an array of struct pages, assigning them to the contiguous phsycial memory and then passing that to vmap(), use vmap_page_range() instead
- Replace flush_dcache_folio() with flush_kernel_vmap_range()
Instead of calling virt_to_folio() and passing that to flush_dcache_folio(), just call flush_kernel_vmap_range() directly. This also fixes a bug where if a subbuffer was bigger than PAGE_SIZE only the PAGE_SIZE portion would be flushed.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/fixes
Head SHA1: e4d4b8670c44cdd22212cab3c576e2d317efa67c
Steven Rostedt (4):
tracing: Enforce the persistent ring buffer to be page aligned
tracing: Have reserve_mem use phys_to_virt() and separate from memmap buffer
tracing: Use vmap_page_range() to map memmap ring buffer
ring-buffer: Use flush_kernel_vmap_range() over flush_dcache_folio()
----
Documentation/admin-guide/kernel-parameters.txt | 2 + Documentation/trace/debugging.rst | 2 + kernel/trace/ring_buffer.c | 5 +- kernel/trace/trace.c | 66 ++++++++++++++++--------- kernel/trace/trace.h | 1 + 5 files changed, 50 insertions(+), 26 deletions(-)
Steven Rostedt
maintainerPATCH 1/4 tracing: Enforce the persistent ring buffer to be page aligned
From: Steven Rostedt <[email protected]>
Enforce that the address and the size of the memory used by the persistent ring buffer is page aligned. Also update the documentation to reflect this requirement.
--- Documentation/admin-guide/kernel-parameters.txt | 2 ++ Documentation/trace/debugging.rst | 2 ++ kernel/trace/trace.c | 10 ++++++++++ 3 files changed, 14 insertions(+)
Documentation/admin-guide/kernel-parameters.txt +2 -0
@@ -7241,6 +7241,8 @@ This is just one of many ways that can clear memory. Make sure your system keeps the content of memory across reboots before relying on this option. + NB: Both the mapped address and size must be page aligned for the architecture. + See also Documentation/trace/debugging.rst
Documentation/trace/debugging.rst +2 -0
@@ -136,6 +136,8 @@ kernel, so only the same kernel is guaranteed to work if the mapping is preserved. Switching to a different kernel version may find a different layout and mark the buffer as invalid. +NB: Both the mapped address and size must be page aligned for the architecture. + Using trace_printk() in the boot instance ----------------------------------------- By default, the content of trace_printk() goes into the top level tracing
kernel/trace/trace.c +10 -0
@@ -10774,6 +10774,16 @@ __init static void enable_instances(void) }if (start) { +/* Start and size must be page aligned */ +if (start & ~PAGE_MASK ) { +pr_warn ("Tracing: mapping start addr %pa is not page aligned\n" , &start); +continue ; + } +if (size & ~PAGE_MASK ) { +pr_warn ("Tracing: mapping size %pa is not page aligned\n" , &size); +continue ; + } + addr =map_pages (start, size);if (addr) { pr_info("Tracing: mapped boot instance %s at physical memory %pa of size 0x%lx\n",
Signature · 1 line
2.47.2
Steven Rostedt
maintainerPATCH 2/4 tracing: Have reserve_mem use phys_to_virt() and separate from memmap buffer
In reply to Steven RostedtFrom: Steven Rostedt <[email protected]>
The reserve_mem kernel command line option may pass back a physical address, but the memory is still part of the normal memory just like using memblock_alloc() would be. This means that the physical memory returned by the reserve_mem command line option can be converted directly to virtual memory by simply using phys_to_virt().
When freeing the buffer there's no need to call vunmap() anymore as the memory allocated by reserve_mem is freed by the call to reserve_mem_release_by_name().
Because the persistent ring buffer can also be allocated via the memmap option, which *is* different than normal memory as it cannot be added back to the buddy system, it must be treated differently. It still needs to be virtually mapped to have access to it. It also can not be freed nor can it ever be memory mapped to user space.
Create a new trace_array flag called TRACE_ARRAY_FL_MEMMAP which gets set if the buffer is created by the memmap option, and this will prevent the buffer from being memory mapped by user space.
Also increment the ref count for memmap'ed buffers so that they can never be freed.
--- kernel/trace/trace.c | 23 ++++++++++++++++------- kernel/trace/trace.h | 1 + 2 files changed, 17 insertions(+), 7 deletions(-)
kernel/trace/trace.c +16 -7
@@ -8492,6 +8492,10 @@ static int tracing_buffers_mmap(struct file *filp, struct vm_area_struct *vma)struct trace_iterator *iter = &info->iter;int ret =0 ; +/* A memmap'ed buffer is not supported for user space mmap */ +if (iter->tr->flags &TRACE_ARRAY_FL_MEMMAP ) +return -ENODEV ; +/* Currently the boot mapped buffer is not supported for mmap */ if (iter->tr->flags &TRACE_ARRAY_FL_BOOT )return -ENODEV ;
@@ -9600,9 +9604,6 @@ static void free_trace_buffers(struct trace_array *tr)#ifdef CONFIG_TRACER_MAX_TRACE free_trace_buffer (&tr->max_buffer);#endif - -if (tr->range_addr_start) -vunmap ((void *)tr->range_addr_start); }static void init_trace_flags_index (struct trace_array *tr)
@@ -10696,6 +10697,7 @@ static inline void do_allocate_snapshot(const char *name) { }__init static void enable_instances (void ) {struct trace_array *tr; +bool memmap_area = false;char *curr_str;char *name;char *str;
@@ -10764,6 +10766,7 @@ __init static void enable_instances(void) name);continue ; } + memmap_area = true; }else if (tok) {if (!reserve_mem_find_by_name (tok, &start, &size)) { start =0 ;
@@ -10784,7 +10787,10 @@ __init static void enable_instances(void)continue ; } - addr =map_pages (start, size); +if (memmap_area) + addr =map_pages (start, size); +else + addr = (unsigned long )phys_to_virt (start);if (addr) {pr_info ("Tracing: mapped boot instance %s at physical memory %pa of size 0x%lx\n" , name, &start, (unsigned long )size);
@@ -10811,10 +10817,13 @@ __init static void enable_instances(void)update_printk_trace (tr);/* -* If start is set, then this is a mapped buffer, and -* cannot be deleted by user space, so keep the reference -* to it. +* memmap'd buffers can not be freed. */ +if (memmap_area) { + tr->flags |=TRACE_ARRAY_FL_MEMMAP ; + tr->ref++; + } +if (start) { tr->flags |=TRACE_ARRAY_FL_BOOT |TRACE_ARRAY_FL_LAST_BOOT ; tr->range_name =no_free_ptr (rname);
kernel/trace/trace.h +1 -0
@@ -446,6 +446,7 @@ enum {TRACE_ARRAY_FL_BOOT =BIT (1 ),TRACE_ARRAY_FL_LAST_BOOT =BIT (2 ),TRACE_ARRAY_FL_MOD_INIT =BIT (3 ), + TRACE_ARRAY_FL_MEMMAP = BIT(4), };#ifdef CONFIG_MODULES
Signature · 1 line
2.47.2
Steven Rostedt
maintainerPATCH 3/4 tracing: Use vmap_page_range() to map memmap ring buffer
In reply to Steven RostedtFrom: Steven Rostedt <[email protected]>
The code to map the physical memory retrieved by memmap currently allocates an array of pages to cover the physical memory and then calls vmap() to map it to a virtual address. Instead of using this temporary array of struct page descriptors, simply use vmap_page_range() that can directly map the contiguous physical memory to a virtual address.
--- kernel/trace/trace.c | 33 ++++++++++++++++----------------- 1 file changed, 16 insertions(+), 17 deletions(-)
kernel/trace/trace.c +16 -17
@@ -50,6 +50,7 @@#include <linux/irq_work.h> #include <linux/workqueue.h> #include <linux/sort.h> +#include <linux/io.h> /* vmap_page_range() */ #include <asm/setup.h> /* COMMAND_LINE_SIZE */
@@ -9796,29 +9797,27 @@ static int instance_mkdir(const char *name)return ret; } -static u64 map_pages (u64 start,u64 size) +static u64 map_pages (unsigned long start,unsigned long size) { -struct page **pages; -phys_addr_t page_start; -unsigned int page_count; -unsigned int i; -void *vaddr; - - page_count =DIV_ROUND_UP (size,PAGE_SIZE ); +unsigned long vmap_start, vmap_end; +struct vm_struct *area; +int ret; - page_start = start; - pages =kmalloc_array (page_count,sizeof (struct page *),GFP_KERNEL ); -if (!pages) + area =get_vm_area (size,VM_IOREMAP ); +if (!area)return 0 ; -for (i =0 ; i < page_count; i++) { -phys_addr_t addr = page_start + i *PAGE_SIZE ; - pages[i] =pfn_to_page (addr >>PAGE_SHIFT ); + vmap_start = (unsigned long ) area->addr; + vmap_end = vmap_start + size; + + ret =vmap_page_range (vmap_start, vmap_end, + start,pgprot_nx (PAGE_KERNEL )); +if (ret <0 ) { +free_vm_area (area); +return 0 ; } - vaddr =vmap (pages, page_count,VM_MAP ,PAGE_KERNEL ); -kfree (pages); -return (u64 )(unsigned long )vaddr; +return (u64 )vmap_start; }/**
Signature · 1 line
2.47.2
Steven Rostedt
maintainerPATCH 4/4 ring-buffer: Use flush_kernel_vmap_range() over flush_dcache_folio()
In reply to Steven RostedtFrom: Steven Rostedt <[email protected]>
Some architectures do not have data cache coherency between user and kernel space. For these architectures, the cache needs to be flushed on both the kernel and user addresses so that user space can see the updates the kernel has made.
Instead of using flush_dcache_folio() and playing with virt_to_folio() within the call to that function, use flush_kernel_vmap_range() which takes the virtual address and does the work for those architectures that need it.
This also fixes a bug where the flush of the reader page only flushed one page. If the sub-buffer order is 1 or more, where the sub-buffer size would be greater than a page, it would miss the rest of the sub-buffer content, as the "reader page" is not just a page, but the size of a sub-buffer.
--- kernel/trace/ring_buffer.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
kernel/trace/ring_buffer.c +3 -2
@@ -6016,7 +6016,7 @@ static void rb_update_meta_page(struct ring_buffer_per_cpu *cpu_buffer) meta->read = cpu_buffer->read;/* Some archs do not have data cache coherency between kernel and user-space */ -flush_dcache_folio (virt_to_folio (cpu_buffer->meta_page)); +flush_kernel_vmap_range (cpu_buffer->meta_page,PAGE_SIZE ); } static void
@@ -7319,7 +7319,8 @@ int ring_buffer_map_get_reader(struct trace_buffer *buffer, int cpu) out:/* Some archs do not have data cache coherency between kernel and user-space */ -flush_dcache_folio (virt_to_folio (cpu_buffer->reader_page->page)); +flush_kernel_vmap_range (cpu_buffer->reader_page->page, + buffer->subbuf_size +BUF_PAGE_HDR_SIZE );rb_update_meta_page (cpu_buffer);
Signature · 1 line
2.47.2