From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Song Liu <song@kernel.org>, Masami Hiramatsu <mhiramat@kernel.org> Cc: "Jarkko Sakkinen" <jarkko@kernel.org>, "Guo Ren" <guoren@kernel.org>, "Jarkko Sakkinen" <jarkko@profian.com>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, "Nathaniel McCallum" <nathaniel@profian.com>, "Russell King" <linux@armlinux.org.uk>, "Catalin Marinas" <catalin.marinas@arm.com>, "Will Deacon" <will@kernel.org>, "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>, "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>, "Helge Deller" <deller@gmx.de>, "Michael Ellerman" <mpe@ellerman.id.au>, "Benjamin Herrenschmidt" <benh@kernel.crashing.org>, "Paul Mackerras" <paulus@samba.org>, "Paul Walmsley" <paul.walmsley@sifive.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Albert Ou" <aou@eecs.berkeley.edu>, "Heiko Carstens" <hca@linux.ibm.com>, "Vasily Gorbik" <gor@linux.ibm.com>, "Alexander Gordeev" <agordeev@linux.ibm.com>, "Christian Borntraeger" <borntraeger@linux.ibm.com>, "Sven Schnelle" <svens@linux.ibm.com>, "David S. Miller" <davem@davemloft.net>, "Thomas Gleixner" <tglx@linutronix.de>, "Ingo Molnar" <mingo@redhat.com>, "Borislav Petkov" <bp@alien8.de>, "Dave Hansen" <dave.hansen@linux.intel.com>, "the arch/x86 maintainers" <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>, "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>, "Anil S Keshavamurthy" <anil.s.keshavamurthy@intel.com>, "Luis Chamberlain" <mcgrof@kernel.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Kees Cook" <keescook@chromium.org>, "Peter Zijlstra (Intel)" <peterz@infradead.org>, "Nathan Chancellor" <nathan@kernel.org>, "Josh Poimboeuf" <jpoimboe@kernel.org>, "Mark Rutland" <mark.rutland@arm.com>, "Eric W. Biederman" <ebiederm@xmission.com>, "Marco Elver" <elver@google.com>, "Dan Li" <ashimida@linux.alibaba.com>, "Sami Tolvanen" <samitolvanen@google.com>, "Ard Biesheuvel" <ardb@kernel.org>, "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>, "Nick Desaulniers" <ndesaulniers@google.com>, "Linus Walleij" <linus.walleij@linaro.org>, "Chen Zhongjin" <chenzhongjin@huawei.com>, "Nicolas Pitre" <nico@fluxnic.net>, "Mark Brown" <broonie@kernel.org>, "Luis Machado" <luis.machado@linaro.org>, "Geert Uytterhoeven" <geert@linux-m68k.org>, "Joey Gouly" <joey.gouly@arm.com>, "Masahiro Yamada" <masahiroy@kernel.org>, "Andrew Morton" <akpm@linux-foundation.org>, "Andrey Konovalov" <andreyknvl@gmail.com>, "Kefeng Wang" <wangkefeng.wang@huawei.com>, "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>, "Guenter Roeck" <linux@roeck-us.net>, "Dave Anglin" <dave.anglin@bell.net>, "Alexei Starovoitov" <ast@kernel.org>, "Nicholas Piggin" <npiggin@gmail.com>, "Daniel Axtens" <dja@axtens.net>, "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>, "Jordan Niethe" <jniethe5@gmail.com>, "Anup Patel" <anup@brainfault.org>, "Atish Patra" <atishp@atishpatra.org>, "Changbin Du" <changbin.du@intel.com>, "Heiko Stuebner" <heiko@sntech.de>, "Liao Chang" <liaochang1@huawei.com>, "Philipp Tomsich" <philipp.tomsich@vrull.eu>, "Wu Caize" <zepan@sipeed.com>, "Emil Renner Berthing" <kernel@esmil.dk>, "Alexander Egorenkov" <egorenar@linux.ibm.com>, "Thomas Richter" <tmricht@linux.ibm.com>, "Tobias Huschle" <huschle@linux.ibm.com>, "Ilya Leoshkevich" <iii@linux.ibm.com>, "Tom Lendacky" <thomas.lendacky@amd.com>, "Daniel Bristot de Oliveira" <bristot@redhat.com>, "Michael Roth" <michael.roth@amd.com>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, "Javier Martinez Canillas" <javierm@redhat.com>, "Miroslav Benes" <mbenes@suse.cz>, "André Almeida" <andrealmeid@igalia.com>, "Tiezhu Yang" <yangtiezhu@loongson.cn>, "Dmitry Torokhov" <dmitry.torokhov@gmail.com>, "Aaron Tomlin" <atomlin@redhat.com>, "Linux ARM" <linux-arm-kernel@lists.infradead.org>, "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>, "Parisc List" <linux-parisc@vger.kernel.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, linux-riscv <linux-riscv@lists.infradead.org>, linux-s390 <linux-s390@vger.kernel.org>, sparclinux <sparclinux@vger.kernel.org>, "linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org> Subject: Re: [PATCH] kprobes: Enable tracing for mololithic kernel images Date: Thu, 9 Jun 2022 08:33:55 +0000 [thread overview] Message-ID: <f7ff2a8d-4128-dac9-9768-1d98bfb06a06@csgroup.eu> (raw) In-Reply-To: <CAPhsuW6iUieQvA6KqzSLgtxmjkVSWCuVwNA338DATb_myHxo7w@mail.gmail.com> Le 08/06/2022 à 18:12, Song Liu a écrit : > On Wed, Jun 8, 2022 at 7:21 AM Masami Hiramatsu <mhiramat@kernel.org> wrote: >> >> Hi Jarkko, >> >> On Wed, 8 Jun 2022 08:25:38 +0300 >> Jarkko Sakkinen <jarkko@kernel.org> wrote: >> >>> On Wed, Jun 08, 2022 at 10:35:42AM +0800, Guo Ren wrote: >>>> . >>>> >>>> On Wed, Jun 8, 2022 at 8:02 AM Jarkko Sakkinen <jarkko@profian.com> wrote: >>>>> >>>>> Tracing with kprobes while running a monolithic kernel is currently >>>>> impossible because CONFIG_KPROBES is dependent of CONFIG_MODULES. This >>>>> dependency is a result of kprobes code using the module allocator for the >>>>> trampoline code. >>>>> >>>>> Detaching kprobes from modules helps to squeeze down the user space, >>>>> e.g. when developing new core kernel features, while still having all >>>>> the nice tracing capabilities. >>>>> >>>>> For kernel/ and arch/*, move module_alloc() and module_memfree() to >>>>> module_alloc.c, and compile as part of vmlinux when either CONFIG_MODULES >>>>> or CONFIG_KPROBES is enabled. In addition, flag kernel module specific >>>>> code with CONFIG_MODULES. >>>>> >>>>> As the result, kprobes can be used with a monolithic kernel. >>>> It's strange when MODULES is n, but vmlinux still obtains module_alloc. >>>> >>>> Maybe we need a kprobe_alloc, right? >>> >>> Perhaps not the best name but at least it documents the fact that >>> they use the same allocator. >>> >>> Few years ago I carved up something "half-way there" for kprobes, >>> and I used the name text_alloc() [*]. >>> >>> [*] https://lore.kernel.org/all/20200724050553.1724168-1-jarkko.sakkinen@linux.intel.com/ >> >> Yeah, I remember that. Thank you for updating your patch! >> I think the idea (split module_alloc() from CONFIG_MODULE) is good to me. >> If module support maintainers think this name is not good, you may be >> able to rename it as text_alloc() and make the module_alloc() as a >> wrapper of it. > > IIUC, most users of module_alloc() use it to allocate memory for text, except > that module code uses it for both text and data. Therefore, I guess calling it > text_alloc() is not 100% accurate until we change the module code (to use > a different API to allocate memory for data). When CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC, module code uses module_alloc() for text and vmalloc() for data, see function move_module() in kernel/module/main.c > > Thanks, > Song > >> >> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> >> for kprobe side. >> >> Thank you, >> >> -- >> Masami Hiramatsu (Google) <mhiramat@kernel.org> _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Leroy <christophe.leroy@csgroup.eu> To: Song Liu <song@kernel.org>, Masami Hiramatsu <mhiramat@kernel.org> Cc: "Dan Li" <ashimida@linux.alibaba.com>, "Heiko Stuebner" <heiko@sntech.de>, "Linus Walleij" <linus.walleij@linaro.org>, "Guo Ren" <guoren@kernel.org>, "Alexander Gordeev" <agordeev@linux.ibm.com>, "Javier Martinez Canillas" <javierm@redhat.com>, "Geert Uytterhoeven" <geert@linux-m68k.org>, "Catalin Marinas" <catalin.marinas@arm.com>, "Christian Borntraeger" <borntraeger@linux.ibm.com>, "Guenter Roeck" <linux@roeck-us.net>, "André Almeida" <andrealmeid@igalia.com>, "Michael Roth" <michael.roth@amd.com>, "Nicholas Piggin" <npiggin@gmail.com>, "Thomas Gleixner" <tglx@linutronix.de>, "Andrey Konovalov" <andreyknvl@gmail.com>, "Nick Desaulniers" <ndesaulniers@google.com>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, "Luis Chamberlain" <mcgrof@kernel.org>, "Sven Schnelle" <svens@linux.ibm.com>, "Wu Caize" <zepan@sipeed.com>, "Paul Mackerras" <paulus@samba.org>, "Andrew Morton" <akpm@linux-foundation.org>, "Mark Rutland" <mark.rutland@arm.com>, "Luis Machado" <luis.machado@linaro.org>, "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>, "Dave Hansen" <dave.hansen@linux.intel.com>, "Joey Gouly" <joey.gouly@arm.com>, "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>, linux-s390 <linux-s390@vger.kernel.org>, "Ilya Leoshkevich" <iii@linux.ibm.com>, "Anup Patel" <anup@brainfault.org>, "Helge Deller" <deller@gmx.de>, "Anil S Keshavamurthy" <anil.s.keshavamurthy@intel.com>, "Tom Lendacky" <thomas.lendacky@amd.com>, "Vasily Gorbik" <gor@linux.ibm.com>, "Philipp Tomsich" <philipp.tomsich@vrull.eu>, "Dave Anglin" <dave.anglin@bell.net>, "Linux ARM" <linux-arm-kernel@lists.infradead.org>, "Daniel Axtens" <dja@axtens.net>, "Nicolas Pitre" <nico@fluxnic.net>, "Jarkko Sakkinen" <jarkko@kernel.org>, "Eric W. Biederman" <ebiederm@xmission.com>, "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>, "Daniel Bristot de Oliveira" <bristot@redhat.com>, "Kefeng Wang" <wangkefeng.wang@huawei.com>, "Emil Renner Berthing" <kernel@esmil.dk>, "Jordan Niethe" <jniethe5@gmail.com>, "Atish Patra" <atishp@atishpatra.org>, "Alexei Starovoitov" <ast@kernel.org>, "Will Deacon" <will@kernel.org>, "Masahiro Yamada" <masahiroy@kernel.org>, "Jarkko Sakkinen" <jarkko@profian.com>, "Sami Tolvanen" <samitolvanen@google.com>, "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>, "Marco Elver" <elver@google.com>, "Kees Cook" <keescook@chromium.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Nathan Chancellor" <nathan@kernel.org>, "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>, "Mark Brown" <broonie@kernel.org>, "Borislav Petkov" <bp@alien8.de>, "Alexander Egorenkov" <egorenar@linux.ibm.com>, "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>, "Parisc List" <linux-parisc@vger.kernel.org>, "Nathaniel McCallum" <nathaniel@profian.com>, "Dmitry Torokhov" <dmitry.torokhov@gmail.com>, "David S. Miller" <davem@davemloft.net>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, "Tobias Huschle" <huschle@linux.ibm.com>, "Peter Zijlstra (Intel)" <peterz@infradead.org>, "H. Peter Anvin" <hpa@zytor.com>, sparclinux <sparclinux@vger.kernel.org>, "Tiezhu Yang" <yangtiezhu@loongson.cn>, "Miroslav Benes" <mbenes@suse.cz>, "Chen Zhongjin" <chenzhongjin@huawei.com>, "Ard Biesheuvel" <ardb@kernel.org>, "the arch/x86 maintainers" <x86@kernel.org>, "Russell King" <linux@armlinux.org.uk>, linux-riscv <linux-riscv@lists.infradead.org>, "Ingo Molnar" <mingo@redhat.com>, "Aaron Tomlin" <atomlin@redhat.com>, "Albert Ou" <aou@eecs.berkeley.edu>, "Heiko Carstens" <hca@linux.ibm.com>, "Liao Chang" <liaochang1@huawei.com>, "Paul Walmsley" <paul.walmsley@sifive.com>, "Josh Poimboeuf" <jpoimboe@kernel.org>, "Thomas Richter" <tmricht@linux.ibm.com>, "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>, "Changbin Du" <changbin.du@intel.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH] kprobes: Enable tracing for mololithic kernel images Date: Thu, 9 Jun 2022 08:33:55 +0000 [thread overview] Message-ID: <f7ff2a8d-4128-dac9-9768-1d98bfb06a06@csgroup.eu> (raw) In-Reply-To: <CAPhsuW6iUieQvA6KqzSLgtxmjkVSWCuVwNA338DATb_myHxo7w@mail.gmail.com> Le 08/06/2022 à 18:12, Song Liu a écrit : > On Wed, Jun 8, 2022 at 7:21 AM Masami Hiramatsu <mhiramat@kernel.org> wrote: >> >> Hi Jarkko, >> >> On Wed, 8 Jun 2022 08:25:38 +0300 >> Jarkko Sakkinen <jarkko@kernel.org> wrote: >> >>> On Wed, Jun 08, 2022 at 10:35:42AM +0800, Guo Ren wrote: >>>> . >>>> >>>> On Wed, Jun 8, 2022 at 8:02 AM Jarkko Sakkinen <jarkko@profian.com> wrote: >>>>> >>>>> Tracing with kprobes while running a monolithic kernel is currently >>>>> impossible because CONFIG_KPROBES is dependent of CONFIG_MODULES. This >>>>> dependency is a result of kprobes code using the module allocator for the >>>>> trampoline code. >>>>> >>>>> Detaching kprobes from modules helps to squeeze down the user space, >>>>> e.g. when developing new core kernel features, while still having all >>>>> the nice tracing capabilities. >>>>> >>>>> For kernel/ and arch/*, move module_alloc() and module_memfree() to >>>>> module_alloc.c, and compile as part of vmlinux when either CONFIG_MODULES >>>>> or CONFIG_KPROBES is enabled. In addition, flag kernel module specific >>>>> code with CONFIG_MODULES. >>>>> >>>>> As the result, kprobes can be used with a monolithic kernel. >>>> It's strange when MODULES is n, but vmlinux still obtains module_alloc. >>>> >>>> Maybe we need a kprobe_alloc, right? >>> >>> Perhaps not the best name but at least it documents the fact that >>> they use the same allocator. >>> >>> Few years ago I carved up something "half-way there" for kprobes, >>> and I used the name text_alloc() [*]. >>> >>> [*] https://lore.kernel.org/all/20200724050553.1724168-1-jarkko.sakkinen@linux.intel.com/ >> >> Yeah, I remember that. Thank you for updating your patch! >> I think the idea (split module_alloc() from CONFIG_MODULE) is good to me. >> If module support maintainers think this name is not good, you may be >> able to rename it as text_alloc() and make the module_alloc() as a >> wrapper of it. > > IIUC, most users of module_alloc() use it to allocate memory for text, except > that module code uses it for both text and data. Therefore, I guess calling it > text_alloc() is not 100% accurate until we change the module code (to use > a different API to allocate memory for data). When CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC, module code uses module_alloc() for text and vmalloc() for data, see function move_module() in kernel/module/main.c > > Thanks, > Song > >> >> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> >> for kprobe side. >> >> Thank you, >> >> -- >> Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-06-09 8:48 UTC|newest] Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 23:59 [PATCH] kprobes: Enable tracing for mololithic kernel images Jarkko Sakkinen 2022-06-07 23:59 ` Jarkko Sakkinen 2022-06-07 23:59 ` Jarkko Sakkinen 2022-06-08 2:35 ` Guo Ren 2022-06-08 2:35 ` Guo Ren 2022-06-08 2:35 ` Guo Ren 2022-06-08 5:25 ` Jarkko Sakkinen 2022-06-08 5:25 ` Jarkko Sakkinen 2022-06-08 5:25 ` Jarkko Sakkinen 2022-06-08 14:21 ` Masami Hiramatsu 2022-06-08 14:21 ` Masami Hiramatsu 2022-06-08 14:21 ` Masami Hiramatsu 2022-06-08 16:12 ` Song Liu 2022-06-08 16:12 ` Song Liu 2022-06-08 16:12 ` Song Liu 2022-06-08 18:20 ` Song Liu 2022-06-08 18:20 ` Song Liu 2022-06-08 18:20 ` Song Liu 2022-06-08 20:26 ` Luis Chamberlain 2022-06-08 20:26 ` Luis Chamberlain 2022-06-08 20:26 ` Luis Chamberlain 2022-06-09 3:48 ` Christoph Hellwig 2022-06-09 3:48 ` Christoph Hellwig 2022-06-09 3:48 ` Christoph Hellwig 2022-06-09 13:24 ` Luis Chamberlain 2022-06-09 13:24 ` Luis Chamberlain 2022-06-09 13:24 ` Luis Chamberlain 2022-06-09 18:41 ` Edgecombe, Rick P 2022-06-09 18:41 ` Edgecombe, Rick P 2022-06-09 18:41 ` Edgecombe, Rick P 2022-06-09 22:48 ` Song Liu 2022-06-09 22:48 ` Song Liu 2022-06-09 22:48 ` Song Liu 2022-06-14 12:32 ` jarkko 2022-06-14 12:32 ` jarkko 2022-06-14 12:32 ` jarkko 2022-06-15 6:37 ` hch 2022-06-15 6:37 ` hch 2022-06-15 6:37 ` hch 2022-06-15 21:29 ` jarkko 2022-06-15 21:29 ` jarkko 2022-06-15 21:29 ` jarkko 2022-06-09 8:33 ` Christophe Leroy [this message] 2022-06-09 8:33 ` Christophe Leroy 2022-06-09 22:23 ` Song Liu 2022-06-09 22:23 ` Song Liu 2022-06-09 22:23 ` Song Liu 2022-06-09 13:12 ` Jarkko Sakkinen 2022-06-09 13:12 ` Jarkko Sakkinen 2022-06-09 13:12 ` Jarkko Sakkinen 2022-06-09 13:23 ` Ard Biesheuvel 2022-06-09 13:23 ` Ard Biesheuvel 2022-06-09 13:23 ` Ard Biesheuvel 2022-06-12 12:18 ` Masami Hiramatsu 2022-06-12 12:18 ` Masami Hiramatsu 2022-06-12 12:18 ` Masami Hiramatsu 2022-06-12 15:59 ` Christophe Leroy 2022-06-12 15:59 ` Christophe Leroy 2022-06-13 0:01 ` Masami Hiramatsu 2022-06-13 0:01 ` Masami Hiramatsu 2022-06-14 10:54 ` Jarkko Sakkinen 2022-06-14 10:54 ` Jarkko Sakkinen 2022-06-14 10:54 ` Jarkko Sakkinen 2022-06-09 12:59 ` Jarkko Sakkinen 2022-06-09 12:59 ` Jarkko Sakkinen 2022-06-09 12:59 ` Jarkko Sakkinen 2022-06-08 16:27 ` Ard Biesheuvel 2022-06-08 16:27 ` Ard Biesheuvel 2022-06-08 16:27 ` Ard Biesheuvel 2022-06-08 18:19 ` Song Liu 2022-06-08 18:19 ` Song Liu 2022-06-08 18:19 ` Song Liu 2022-06-12 12:30 ` Masami Hiramatsu 2022-06-12 12:30 ` Masami Hiramatsu 2022-06-12 12:30 ` Masami Hiramatsu 2022-06-14 12:30 ` Jarkko Sakkinen 2022-06-14 12:30 ` Jarkko Sakkinen 2022-06-14 12:30 ` Jarkko Sakkinen 2022-06-09 5:37 ` Jarkko Sakkinen 2022-06-09 5:37 ` Jarkko Sakkinen 2022-06-09 5:37 ` Jarkko Sakkinen 2022-06-09 7:47 ` Russell King (Oracle) 2022-06-09 7:47 ` Russell King (Oracle) 2022-06-09 7:47 ` Russell King (Oracle) 2022-06-09 11:48 ` Jarkko Sakkinen 2022-06-09 11:48 ` Jarkko Sakkinen 2022-06-09 11:48 ` Jarkko Sakkinen 2022-06-09 13:44 ` Luis Chamberlain 2022-06-09 13:44 ` Luis Chamberlain 2022-06-09 13:44 ` Luis Chamberlain 2022-06-14 12:26 ` Jarkko Sakkinen 2022-06-14 12:26 ` Jarkko Sakkinen 2022-06-14 12:26 ` Jarkko Sakkinen 2022-06-14 12:36 ` Christophe Leroy 2022-06-14 12:36 ` Christophe Leroy 2022-06-15 21:24 ` Jarkko Sakkinen 2022-06-15 21:24 ` Jarkko Sakkinen 2022-06-15 21:24 ` Jarkko Sakkinen 2022-06-09 8:30 ` Christophe Leroy 2022-06-09 8:30 ` Christophe Leroy 2022-06-09 12:57 ` Jarkko Sakkinen 2022-06-09 12:57 ` Jarkko Sakkinen 2022-06-09 12:57 ` Jarkko Sakkinen 2022-06-09 13:42 ` Christophe Leroy 2022-06-09 13:42 ` Christophe Leroy
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=f7ff2a8d-4128-dac9-9768-1d98bfb06a06@csgroup.eu \ --to=christophe.leroy@csgroup.eu \ --cc=James.Bottomley@hansenpartnership.com \ --cc=agordeev@linux.ibm.com \ --cc=akpm@linux-foundation.org \ --cc=andrealmeid@igalia.com \ --cc=andreyknvl@gmail.com \ --cc=aneesh.kumar@linux.ibm.com \ --cc=anemo@mba.ocn.ne.jp \ --cc=anil.s.keshavamurthy@intel.com \ --cc=anup@brainfault.org \ --cc=aou@eecs.berkeley.edu \ --cc=ardb@kernel.org \ --cc=ashimida@linux.alibaba.com \ --cc=ast@kernel.org \ --cc=atishp@atishpatra.org \ --cc=atomlin@redhat.com \ --cc=benh@kernel.crashing.org \ --cc=borntraeger@linux.ibm.com \ --cc=bp@alien8.de \ --cc=bristot@redhat.com \ --cc=broonie@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=changbin.du@intel.com \ --cc=chenzhongjin@huawei.com \ --cc=dave.anglin@bell.net \ --cc=dave.hansen@linux.intel.com \ --cc=davem@davemloft.net \ --cc=deller@gmx.de \ --cc=dja@axtens.net \ --cc=dmitry.torokhov@gmail.com \ --cc=ebiederm@xmission.com \ --cc=egorenar@linux.ibm.com \ --cc=elver@google.com \ --cc=geert@linux-m68k.org \ --cc=gor@linux.ibm.com \ --cc=guoren@kernel.org \ --cc=hca@linux.ibm.com \ --cc=heiko@sntech.de \ --cc=hpa@zytor.com \ --cc=huschle@linux.ibm.com \ --cc=iii@linux.ibm.com \ --cc=jarkko@kernel.org \ --cc=jarkko@profian.com \ --cc=javierm@redhat.com \ --cc=jniethe5@gmail.com \ --cc=joey.gouly@arm.com \ --cc=jpoimboe@kernel.org \ --cc=keescook@chromium.org \ --cc=kernel@esmil.dk \ --cc=kirill.shutemov@linux.intel.com \ --cc=liaochang1@huawei.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-modules@vger.kernel.org \ --cc=linux-parisc@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=linux-s390@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=linux@roeck-us.net \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=luis.machado@linaro.org \ --cc=mark.rutland@arm.com \ --cc=masahiroy@kernel.org \ --cc=mbenes@suse.cz \ --cc=mcgrof@kernel.org \ --cc=mhiramat@kernel.org \ --cc=michael.roth@amd.com \ --cc=mingo@redhat.com \ --cc=mpe@ellerman.id.au \ --cc=nathan@kernel.org \ --cc=nathaniel@profian.com \ --cc=naveen.n.rao@linux.ibm.com \ --cc=ndesaulniers@google.com \ --cc=nico@fluxnic.net \ --cc=npiggin@gmail.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=paulus@samba.org \ --cc=peterz@infradead.org \ --cc=philipp.tomsich@vrull.eu \ --cc=rmk+kernel@armlinux.org.uk \ --cc=rostedt@goodmis.org \ --cc=samitolvanen@google.com \ --cc=song@kernel.org \ --cc=sparclinux@vger.kernel.org \ --cc=svens@linux.ibm.com \ --cc=tglx@linutronix.de \ --cc=thomas.lendacky@amd.com \ --cc=tmricht@linux.ibm.com \ --cc=tsbogend@alpha.franken.de \ --cc=wangkefeng.wang@huawei.com \ --cc=will@kernel.org \ --cc=x86@kernel.org \ --cc=yangtiezhu@loongson.cn \ --cc=zepan@sipeed.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: linkBe 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.