From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Alexander Potapenko <glider@google.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
kasan-dev@googlegroups.com,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, dm-devel@redhat.com,
Mike Snitzer <snitzer@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
linux-arch@vger.kernel.org
Subject: Re: [patch V2 21/29] tracing: Use percpu stack trace buffer more intelligently
Date: Thu, 18 Apr 2019 17:43:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904181743270.3174@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190418105334.5093528d@gandalf.local.home>
On Thu, 18 Apr 2019, Steven Rostedt wrote:
> On Thu, 18 Apr 2019 10:41:40 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
> > -static DEFINE_PER_CPU(struct ftrace_stack, ftrace_stack);
> > +/* This allows 8 level nesting which is plenty */
>
> Can we make this 4 level nesting and increase the size? (I can see us
> going more than 64 deep, kernel developers never cease to amaze me ;-)
> That's all we need:
>
> Context: Normal, softirq, irq, NMI
>
> Is there any other way to nest?
Not that I know, but you are the tracer dude :)
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>
Cc: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Joonas Lahtinen
<joonas.lahtinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Alexander Potapenko
<glider-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Alasdair Kergon <agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
kasan-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
Johannes Thumshirn <jthumshirn-l3A5Bk7waGM@public.gmane.org>,
Andrey Ryabinin
<aryabinin-5HdwGun5lf+gSpxsJD1C4w@public.gmane.org>,
Alexey Dobriyan
<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Maarten Lankhorst
<maarten.lankhorst-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Akinobu Mita
<akinobu.mita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jani Nikula <jani.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Josef Bacik <josef-DigfWCa+lFGyeJad7bwFQA@public.gmane.org>,
Rodrigo Vivi
<rodrigo.vivi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Mike Rapoport <rppt@linux>
Subject: Re: [patch V2 21/29] tracing: Use percpu stack trace buffer more intelligently
Date: Thu, 18 Apr 2019 17:43:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904181743270.3174@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190418105334.5093528d-f9ZlEuEWxVcJvu8Pb33WZ0EMvNT87kid@public.gmane.org>
On Thu, 18 Apr 2019, Steven Rostedt wrote:
> On Thu, 18 Apr 2019 10:41:40 +0200
> Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org> wrote:
> > -static DEFINE_PER_CPU(struct ftrace_stack, ftrace_stack);
> > +/* This allows 8 level nesting which is plenty */
>
> Can we make this 4 level nesting and increase the size? (I can see us
> going more than 64 deep, kernel developers never cease to amaze me ;-)
> That's all we need:
>
> Context: Normal, softirq, irq, NMI
>
> Is there any other way to nest?
Not that I know, but you are the tracer dude :)
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mike Snitzer <snitzer@redhat.com>,
David Airlie <airlied@linux.ie>,
Catalin Marinas <catalin.marinas@arm.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
dm-devel@redhat.com, Alexander Potapenko <glider@google.com>,
Christoph Lameter <cl@linux.com>, Christoph Hellwig <hch@lst.de>,
Alasdair Kergon <agk@redhat.com>,
linux-arch@vger.kernel.org, x86@kernel.org,
kasan-dev@googlegroups.com,
Johannes Thumshirn <jthumshirn@suse.de>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
intel-gfx@lists.freedesktop.org,
David Rientjes <rientjes@google.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Josef Bacik <josef@toxicpanda.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andy Lutomirski <luto@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
David Sterba <dsterba@suse.com>,
Dmitry Vyukov <dvyukov@google.com>, Chris Mason <clm@fb.com>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
iommu@lists.linux-foundation.org, Daniel Vetter <daniel@ffwll.ch>,
Andrew Morton <akpm@linux-foundation.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [patch V2 21/29] tracing: Use percpu stack trace buffer more intelligently
Date: Thu, 18 Apr 2019 17:43:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904181743270.3174@nanos.tec.linutronix.de> (raw)
Message-ID: <20190418154359.yVciWPs9F9Ka0uGHa-kHAaU7zTED8DfSiT5jvBuphGs@z> (raw)
In-Reply-To: <20190418105334.5093528d@gandalf.local.home>
On Thu, 18 Apr 2019, Steven Rostedt wrote:
> On Thu, 18 Apr 2019 10:41:40 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
> > -static DEFINE_PER_CPU(struct ftrace_stack, ftrace_stack);
> > +/* This allows 8 level nesting which is plenty */
>
> Can we make this 4 level nesting and increase the size? (I can see us
> going more than 64 deep, kernel developers never cease to amaze me ;-)
> That's all we need:
>
> Context: Normal, softirq, irq, NMI
>
> Is there any other way to nest?
Not that I know, but you are the tracer dude :)
Thanks,
tglx
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-04-18 15:44 UTC|newest]
Thread overview: 233+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 8:41 [patch V2 00/29] stacktrace: Consolidate stack trace usage Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 01/29] tracing: Cleanup stack trace code Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 13:57 ` Josh Poimboeuf
2019-04-18 13:57 ` Josh Poimboeuf
2019-04-18 13:57 ` Josh Poimboeuf
2019-04-18 21:14 ` Thomas Gleixner
2019-04-18 21:14 ` Thomas Gleixner
2019-04-18 21:14 ` Thomas Gleixner
2019-04-18 21:14 ` Thomas Gleixner
2019-04-18 21:24 ` Steven Rostedt
2019-04-18 21:24 ` Steven Rostedt
2019-04-18 21:24 ` Steven Rostedt
2019-04-18 21:50 ` Steven Rostedt
2019-04-18 21:50 ` Steven Rostedt
2019-04-18 21:50 ` Steven Rostedt
2019-04-18 22:19 ` Steven Rostedt
2019-04-18 22:19 ` Steven Rostedt
2019-04-18 22:19 ` Steven Rostedt
2019-04-18 22:44 ` Thomas Gleixner
2019-04-18 22:44 ` Thomas Gleixner
2019-04-18 22:44 ` Thomas Gleixner
2019-04-18 22:44 ` Thomas Gleixner
2019-04-19 0:39 ` Steven Rostedt
2019-04-19 0:39 ` Steven Rostedt
2019-04-19 0:39 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 02/29] stacktrace: Provide helpers for common stack trace operations Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 03/29] lib/stackdepot: Provide functions which operate on plain storage arrays Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 11:51 ` Mike Rapoport
2019-04-18 11:51 ` Mike Rapoport
2019-04-18 11:51 ` Mike Rapoport
2019-04-18 11:58 ` Thomas Gleixner
2019-04-18 11:58 ` Thomas Gleixner
2019-04-18 11:58 ` Thomas Gleixner
2019-04-18 11:58 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 04/29] backtrace-test: Simplify stack trace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 05/29] proc: Simplify task stack retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 06/29] latency_top: Simplify stack trace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 07/29] mm/slub: Simplify stack trace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 08/29] mm/kmemleak: Simplify stacktrace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 15:17 ` Catalin Marinas
2019-04-18 15:17 ` Catalin Marinas
2019-04-18 15:17 ` Catalin Marinas
2019-04-18 8:41 ` [patch V2 09/29] mm/kasan: " Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 10:39 ` Andrey Ryabinin
2019-04-18 10:39 ` Andrey Ryabinin
2019-04-18 10:39 ` Andrey Ryabinin
2019-04-18 11:53 ` Thomas Gleixner
2019-04-18 11:53 ` Thomas Gleixner
2019-04-18 11:53 ` Thomas Gleixner
2019-04-18 11:53 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 10/29] mm/page_owner: Simplify stack trace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 11/29] fault-inject: Simplify stacktrace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 12/29] dma/debug: Simplify stracktrace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-19 7:05 ` Christoph Hellwig
2019-04-19 7:05 ` Christoph Hellwig
2019-04-19 7:05 ` Christoph Hellwig
2019-04-18 8:41 ` [patch V2 13/29] btrfs: ref-verify: Simplify stack trace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 14/29] dm bufio: " Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 10:44 ` Alexander Potapenko
2019-04-18 10:44 ` Alexander Potapenko via iommu
2019-04-18 10:44 ` Alexander Potapenko
2019-04-18 10:44 ` Alexander Potapenko
2019-04-18 11:54 ` Thomas Gleixner
2019-04-18 11:54 ` Thomas Gleixner
2019-04-18 11:54 ` Thomas Gleixner
2019-04-18 11:54 ` Thomas Gleixner
2019-04-18 12:11 ` Alexander Potapenko
2019-04-18 12:11 ` Alexander Potapenko via iommu
2019-04-18 12:11 ` Alexander Potapenko
2019-04-18 12:11 ` Alexander Potapenko
2019-04-18 13:33 ` Steven Rostedt
2019-04-18 13:33 ` Steven Rostedt
2019-04-18 13:33 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 15/29] dm persistent data: Simplify stack trace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 16/29] drm: Simplify stacktrace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-23 7:36 ` Daniel Vetter
2019-04-23 7:36 ` Daniel Vetter
2019-04-23 7:36 ` Daniel Vetter
2019-04-18 8:41 ` [patch V2 17/29] lockdep: Remove unused trace argument from print_circular_bug() Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 18/29] lockdep: Move stack trace logic into check_prev_add() Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-24 19:45 ` Peter Zijlstra
2019-04-24 19:45 ` Peter Zijlstra
2019-04-24 19:45 ` Peter Zijlstra
2019-04-24 19:51 ` Thomas Gleixner
2019-04-24 19:51 ` Thomas Gleixner
2019-04-24 19:51 ` Thomas Gleixner
2019-04-24 19:51 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 19/29] lockdep: Simplify stack trace handling Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-24 19:45 ` Peter Zijlstra
2019-04-24 19:45 ` Peter Zijlstra
2019-04-24 19:45 ` Peter Zijlstra
2019-04-18 8:41 ` [patch V2 20/29] tracing: Simplify stacktrace retrieval in histograms Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 13:40 ` Steven Rostedt
2019-04-18 13:40 ` Steven Rostedt
2019-04-18 13:40 ` Steven Rostedt
2019-04-18 19:58 ` Tom Zanussi
2019-04-18 19:58 ` Tom Zanussi
2019-04-18 19:58 ` Tom Zanussi
2019-04-18 19:58 ` Tom Zanussi
2019-04-18 20:13 ` Steven Rostedt
2019-04-18 20:13 ` Steven Rostedt
2019-04-18 20:13 ` Steven Rostedt
2019-04-18 20:22 ` Tom Zanussi
2019-04-18 20:22 ` Tom Zanussi
2019-04-18 20:22 ` Tom Zanussi
2019-04-18 20:22 ` Tom Zanussi
2019-04-18 8:41 ` [patch V2 21/29] tracing: Use percpu stack trace buffer more intelligently Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 14:53 ` Steven Rostedt
2019-04-18 14:53 ` Steven Rostedt
2019-04-18 14:53 ` Steven Rostedt
2019-04-18 15:43 ` Thomas Gleixner [this message]
2019-04-18 15:43 ` Thomas Gleixner
2019-04-18 15:43 ` Thomas Gleixner
2019-04-18 15:43 ` Thomas Gleixner
2019-04-18 15:46 ` Steven Rostedt
2019-04-18 15:46 ` Steven Rostedt
2019-04-18 15:46 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 22/29] tracing: Make ftrace_trace_userstack() static and conditional Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-19 13:28 ` Steven Rostedt
2019-04-19 13:28 ` Steven Rostedt
2019-04-19 13:28 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 23/29] tracing: Simplify stack trace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-19 20:11 ` Steven Rostedt
2019-04-19 20:11 ` Steven Rostedt
2019-04-19 20:11 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 24/29] tracing: Remove the last struct stack_trace usage Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-19 20:11 ` Steven Rostedt
2019-04-19 20:11 ` Steven Rostedt
2019-04-19 20:11 ` Steven Rostedt
2019-04-18 8:41 ` [patch V2 25/29] livepatch: Simplify stack trace retrieval Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-23 8:18 ` Miroslav Benes
2019-04-23 8:18 ` Miroslav Benes
2019-04-23 8:18 ` Miroslav Benes
2019-04-23 8:18 ` Miroslav Benes
2019-04-18 8:41 ` [patch V2 26/29] stacktrace: Remove obsolete functions Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 27/29] lib/stackdepot: " Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` [patch V2 28/29] stacktrace: Provide common infrastructure Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 11:52 ` Mike Rapoport
2019-04-18 11:52 ` Mike Rapoport
2019-04-18 11:52 ` Mike Rapoport
2019-04-18 11:57 ` Thomas Gleixner
2019-04-18 11:57 ` Thomas Gleixner
2019-04-18 11:57 ` Thomas Gleixner
2019-04-18 11:57 ` Thomas Gleixner
2019-04-18 14:52 ` Josh Poimboeuf
2019-04-18 14:52 ` Josh Poimboeuf
2019-04-18 14:52 ` Josh Poimboeuf
2019-04-18 15:42 ` Thomas Gleixner
2019-04-18 15:42 ` Thomas Gleixner
2019-04-18 15:42 ` Thomas Gleixner
2019-04-18 15:42 ` Thomas Gleixner
2019-04-19 7:02 ` Peter Zijlstra
2019-04-19 7:02 ` Peter Zijlstra
2019-04-19 7:02 ` Peter Zijlstra
2019-04-19 15:50 ` Josh Poimboeuf
2019-04-19 15:50 ` Josh Poimboeuf
2019-04-19 15:50 ` Josh Poimboeuf
2019-04-19 7:18 ` Peter Zijlstra
2019-04-19 7:18 ` Peter Zijlstra
2019-04-19 7:18 ` Peter Zijlstra
2019-04-19 7:18 ` Peter Zijlstra
2019-04-19 8:32 ` Thomas Gleixner
2019-04-19 8:32 ` Thomas Gleixner
2019-04-19 8:32 ` Thomas Gleixner
2019-04-19 8:32 ` Thomas Gleixner
2019-04-19 9:07 ` Peter Zijlstra
2019-04-19 9:07 ` Peter Zijlstra
2019-04-19 9:07 ` Peter Zijlstra
2019-04-19 16:17 ` Josh Poimboeuf
2019-04-19 16:17 ` Josh Poimboeuf
2019-04-19 16:17 ` Josh Poimboeuf
2019-04-18 8:41 ` [patch V2 29/29] x86/stacktrace: Use " Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 8:41 ` Thomas Gleixner
2019-04-18 10:48 ` ✗ Fi.CI.BAT: failure for stacktrace: Consolidate stack trace usage Patchwork
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=alpine.DEB.2.21.1904181743270.3174@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=agk@redhat.com \
--cc=airlied@linux.ie \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=clm@fb.com \
--cc=daniel@ffwll.ch \
--cc=dm-devel@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsterba@suse.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=josef@toxicpanda.com \
--cc=jpoimboe@redhat.com \
--cc=jthumshirn@suse.de \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rodrigo.vivi@intel.com \
--cc=rostedt@goodmis.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=snitzer@redhat.com \
--cc=x86@kernel.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.