mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vincent Donnefort <vdonnefort@google.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Jann Horn <jannh@google.com>
Subject: Re: [PATCH v6 3/4] tracing: Use vmap_page_range() to map memmap ring buffer
Date: Mon, 7 Apr 2025 08:57:44 -0700	[thread overview]
Message-ID: <2c0b957b-3a7c-4607-9a8b-79fcbf7297c8@roeck-us.net> (raw)
In-Reply-To: <20250407112352.264e12b0@gandalf.local.home>

On 4/7/25 08:23, Steven Rostedt wrote:
> On Sun, 6 Apr 2025 10:39:27 -0700
> Guenter Roeck <linux@roeck-us.net> wrote:
> 
>> non-MMU builds (xtensa:nommu_kc705_defconfig):
> 
> Bah!
> 
:-)

>>
>> kernel/trace/trace.o:(.init.literal+0x250): undefined reference to `get_vm_area'
> 
> Does this fix it?
> 

Yes, it does.

Tested-by: Guenter Roeck <linux@roeck-us.net>

Thanks,
Guenter

> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index b581e388a9d9..8ddf6b17215c 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -9806,6 +9806,7 @@ static int instance_mkdir(const char *name)
>   	return ret;
>   }
>   
> +#ifdef CONFIG_MMU
>   static u64 map_pages(unsigned long start, unsigned long size)
>   {
>   	unsigned long vmap_start, vmap_end;
> @@ -9828,6 +9829,12 @@ static u64 map_pages(unsigned long start, unsigned long size)
>   
>   	return (u64)vmap_start;
>   }
> +#else
> +static inline u64 map_pages(unsigned long start, unsigned long size)
> +{
> +	return 0;
> +}
> +#endif
>   
>   /**
>    * trace_array_get_by_name - Create/Lookup a trace array, given its name.
> 
> 
> -- Steve


  reply	other threads:[~2025-04-07 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 14:49 [PATCH v6 0/4] tracing: Clean up persistent ring buffer code Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 1/4] tracing: Enforce the persistent ring buffer to be page aligned Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 2/4] tracing: Have reserve_mem use phys_to_virt() and separate from memmap buffer Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 3/4] tracing: Use vmap_page_range() to map memmap ring buffer Steven Rostedt
2025-04-06 17:39   ` Guenter Roeck
2025-04-07 15:23     ` Steven Rostedt
2025-04-07 15:57       ` Guenter Roeck [this message]
2025-04-02 14:49 ` [PATCH v6 4/4] ring-buffer: Use flush_kernel_vmap_range() over flush_dcache_folio() Steven Rostedt
2025-04-02 14:56 ` [PATCH v6 0/4] tracing: Clean up persistent ring buffer code Mathieu Desnoyers
2025-04-02 15:49   ` Steven Rostedt
2025-04-02 16:00     ` Mathieu Desnoyers

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=2c0b957b-3a7c-4607-9a8b-79fcbf7297c8@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=vdonnefort@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®