From: Uladzislau Rezki <urezki@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event
Date: Tue, 18 Oct 2022 18:17:55 +0200 [thread overview]
Message-ID: <Y07Rsz5R1ufZu6Od@pc636> (raw)
In-Reply-To: <202210180250.V8hzNH8X-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
Hello, Steven.
>
> [auto build test ERROR on akpm-mm/mm-everything]
> [also build test ERROR on linus/master v6.1-rc1 next-20221017]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Uladzislau-Rezki-Sony/Add-basic-trace-events-for-vmap-vmalloc/20221018-000544
> base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link: https://lore.kernel.org/r/20221017160233.16582-7-urezki%40gmail.com
> patch subject: [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event
> config: um-i386_defconfig
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> # https://github.com/intel-lab-lkp/linux/commit/fbc853c689b29d3bb9fe250b2653fd2dd8046fc7
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Uladzislau-Rezki-Sony/Add-basic-trace-events-for-vmap-vmalloc/20221018-000544
> git checkout fbc853c689b29d3bb9fe250b2653fd2dd8046fc7
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from include/trace/events/vmap.h:123,
> from mm/vmalloc.c:47:
> >> include/trace/define_trace.h:84:34: fatal error: trace/events/kernel_vmap.h: No such file or directory
> 84 | # define __TRACE_INCLUDE(system) <trace/events/system.h>
> | ^
> compilation terminated.
>
I can reproduce it. It seems it happens so far only on the ARCH=um case.
For regular arm/x86 i do not see such build error.
If i rename the TRACE_SYSTEM macro to something different then "vmap"
it compiles fine. In case of:
#define TRACE_SYSTEM vmap
the prefix "kernel_" is added, thus the header name becomes as kernel_vmap.h
Steven can you give some indications? Or any thoughts about it?
Thank you in advance!
--
Uladzislau Rezki
WARNING: multiple messages have this Message-ID (diff)
From: Uladzislau Rezki <urezki@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Nicholas Piggin <npiggin@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event
Date: Tue, 18 Oct 2022 18:17:55 +0200 [thread overview]
Message-ID: <Y07Rsz5R1ufZu6Od@pc636> (raw)
In-Reply-To: <202210180250.V8hzNH8X-lkp@intel.com>
Hello, Steven.
>
> [auto build test ERROR on akpm-mm/mm-everything]
> [also build test ERROR on linus/master v6.1-rc1 next-20221017]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Uladzislau-Rezki-Sony/Add-basic-trace-events-for-vmap-vmalloc/20221018-000544
> base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link: https://lore.kernel.org/r/20221017160233.16582-7-urezki%40gmail.com
> patch subject: [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event
> config: um-i386_defconfig
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> # https://github.com/intel-lab-lkp/linux/commit/fbc853c689b29d3bb9fe250b2653fd2dd8046fc7
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Uladzislau-Rezki-Sony/Add-basic-trace-events-for-vmap-vmalloc/20221018-000544
> git checkout fbc853c689b29d3bb9fe250b2653fd2dd8046fc7
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from include/trace/events/vmap.h:123,
> from mm/vmalloc.c:47:
> >> include/trace/define_trace.h:84:34: fatal error: trace/events/kernel_vmap.h: No such file or directory
> 84 | # define __TRACE_INCLUDE(system) <trace/events/system.h>
> | ^
> compilation terminated.
>
I can reproduce it. It seems it happens so far only on the ARCH=um case.
For regular arm/x86 i do not see such build error.
If i rename the TRACE_SYSTEM macro to something different then "vmap"
it compiles fine. In case of:
#define TRACE_SYSTEM vmap
the prefix "kernel_" is added, thus the header name becomes as kernel_vmap.h
Steven can you give some indications? Or any thoughts about it?
Thank you in advance!
--
Uladzislau Rezki
next prev parent reply other threads:[~2022-10-18 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 16:02 [PATCH 0/7] Add basic trace events for vmap/vmalloc Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 1/7] mm: vmap: Add alloc_vmap_area trace event Uladzislau Rezki (Sony)
2022-10-18 16:41 ` Steven Rostedt
2022-10-18 16:57 ` Uladzislau Rezki
2022-10-17 16:02 ` [PATCH 2/7] mm: vmap: Add a purge_vmap_area_lazy " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 2/7] mm: vmap: Add " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 3/7] mm: vmap: Add a free_vmap_area_noflush " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 3/7] mm: vmap: Add " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event Uladzislau Rezki (Sony)
2022-10-17 19:12 ` kernel test robot
2022-10-18 16:17 ` Uladzislau Rezki [this message]
2022-10-18 16:17 ` Uladzislau Rezki
2022-10-18 16:44 ` Steven Rostedt
2022-10-18 16:44 ` Steven Rostedt
2022-10-18 16:55 ` Uladzislau Rezki
2022-10-18 16:55 ` Uladzislau Rezki
2022-10-17 16:02 ` [PATCH 5/7] mm/vmalloc: Use a trace_purge_vmap_area_lazy event Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 6/7] mm/vmalloc: Use a trace_free_vmap_area_noflush event Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 7/7] vmalloc: Add reviewers for vmalloc code Uladzislau Rezki (Sony)
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=Y07Rsz5R1ufZu6Od@pc636 \
--to=urezki@gmail.com \
--cc=kbuild-all@lists.01.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 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.