From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "jim.cromie@gmail.com" <jim.cromie@gmail.com>
Cc: "quic_saipraka@quicinc.com" <quic_saipraka@quicinc.com>,
Jason Baron <jbaron@akamai.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Will Deacon <will@kernel.org>, "maz@kernel.org" <maz@kernel.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Steven Rostedt <rostedt@goodmis.org>,
Pekka Paalanen <ppaalanen@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Sean Paul <sean@poorly.run>, Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"quic_psodagud@quicinc.com" <quic_psodagud@quicinc.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC
Date: Thu, 25 Nov 2021 14:51:19 +0100 [thread overview]
Message-ID: <20211125135119.GA7625@axis.com> (raw)
In-Reply-To: <CAJfuBxyvDtALAHM53RdnWT4ke6Cjrc3OWTAqNKe_n-o_LhtpYg@mail.gmail.com>
On Fri, Nov 19, 2021 at 11:46:31PM +0100, jim.cromie@gmail.com wrote:
> Vincent's code has the macro magic to define that event, which IIUC
> is what makes it controllable by ftrace, and therefore acceptable in
> principle to Steve.
> Would there be any reason to expand his set of 2 events into dev_dbg,
> pr_debug etc varieties ?
> (ie any value to separating dev, !dev ?, maybe so
>
> Sean's code uses trace_array_printk primarily, which is EXPORTed,
> which is a virtue.
>
> Vincents code does
> +/*
> + * This code is heavily based on __ftrace_trace_stack().
> + *
> + * Allow 4 levels of nesting: normal, softirq, irq, NMI.
> + */
>
> to implement
>
> +static void dynamic_trace(const char *fmt, va_list args)
>
> Has this __ftrace_trace_stack() code been bundled into or hidden under
> a supported interface ?
>
> would it look anything like trace_array_printk() ?
>
> what problem is that code solving inside dynamic-debug.c ?
I'm not sure I fully understand all of your questions, but perhaps this
thread with Steven's reply to the first version of my patchset will
answer some of them:
https://lore.kernel.org/lkml/20200723112644.7759f82f@oasis.local.home/
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "jim.cromie@gmail.com" <jim.cromie@gmail.com>
Cc: "quic_saipraka@quicinc.com" <quic_saipraka@quicinc.com>,
Jason Baron <jbaron@akamai.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Will Deacon <will@kernel.org>, "maz@kernel.org" <maz@kernel.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Steven Rostedt <rostedt@goodmis.org>,
Pekka Paalanen <ppaalanen@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"quic_psodagud@quicinc.com" <quic_psodagud@quicinc.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>
Subject: Re: [Intel-gfx] [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC
Date: Thu, 25 Nov 2021 14:51:19 +0100 [thread overview]
Message-ID: <20211125135119.GA7625@axis.com> (raw)
In-Reply-To: <CAJfuBxyvDtALAHM53RdnWT4ke6Cjrc3OWTAqNKe_n-o_LhtpYg@mail.gmail.com>
On Fri, Nov 19, 2021 at 11:46:31PM +0100, jim.cromie@gmail.com wrote:
> Vincent's code has the macro magic to define that event, which IIUC
> is what makes it controllable by ftrace, and therefore acceptable in
> principle to Steve.
> Would there be any reason to expand his set of 2 events into dev_dbg,
> pr_debug etc varieties ?
> (ie any value to separating dev, !dev ?, maybe so
>
> Sean's code uses trace_array_printk primarily, which is EXPORTed,
> which is a virtue.
>
> Vincents code does
> +/*
> + * This code is heavily based on __ftrace_trace_stack().
> + *
> + * Allow 4 levels of nesting: normal, softirq, irq, NMI.
> + */
>
> to implement
>
> +static void dynamic_trace(const char *fmt, va_list args)
>
> Has this __ftrace_trace_stack() code been bundled into or hidden under
> a supported interface ?
>
> would it look anything like trace_array_printk() ?
>
> what problem is that code solving inside dynamic-debug.c ?
I'm not sure I fully understand all of your questions, but perhaps this
thread with Steven's reply to the first version of my patchset will
answer some of them:
https://lore.kernel.org/lkml/20200723112644.7759f82f@oasis.local.home/
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "jim.cromie@gmail.com" <jim.cromie@gmail.com>
Cc: Jason Baron <jbaron@akamai.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Sean Paul <seanpaul@chromium.org>, Sean Paul <sean@poorly.run>,
"quic_saipraka@quicinc.com" <quic_saipraka@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Will Deacon <will@kernel.org>, "maz@kernel.org" <maz@kernel.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Steven Rostedt <rostedt@goodmis.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"quic_psodagud@quicinc.com" <quic_psodagud@quicinc.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC
Date: Thu, 25 Nov 2021 14:51:19 +0100 [thread overview]
Message-ID: <20211125135119.GA7625@axis.com> (raw)
In-Reply-To: <CAJfuBxyvDtALAHM53RdnWT4ke6Cjrc3OWTAqNKe_n-o_LhtpYg@mail.gmail.com>
On Fri, Nov 19, 2021 at 11:46:31PM +0100, jim.cromie@gmail.com wrote:
> Vincent's code has the macro magic to define that event, which IIUC
> is what makes it controllable by ftrace, and therefore acceptable in
> principle to Steve.
> Would there be any reason to expand his set of 2 events into dev_dbg,
> pr_debug etc varieties ?
> (ie any value to separating dev, !dev ?, maybe so
>
> Sean's code uses trace_array_printk primarily, which is EXPORTed,
> which is a virtue.
>
> Vincents code does
> +/*
> + * This code is heavily based on __ftrace_trace_stack().
> + *
> + * Allow 4 levels of nesting: normal, softirq, irq, NMI.
> + */
>
> to implement
>
> +static void dynamic_trace(const char *fmt, va_list args)
>
> Has this __ftrace_trace_stack() code been bundled into or hidden under
> a supported interface ?
>
> would it look anything like trace_array_printk() ?
>
> what problem is that code solving inside dynamic-debug.c ?
I'm not sure I fully understand all of your questions, but perhaps this
thread with Steven's reply to the first version of my patchset will
answer some of them:
https://lore.kernel.org/lkml/20200723112644.7759f82f@oasis.local.home/
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "jim.cromie@gmail.com" <jim.cromie@gmail.com>
Cc: Jason Baron <jbaron@akamai.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Sean Paul <seanpaul@chromium.org>, Sean Paul <sean@poorly.run>,
"quic_saipraka@quicinc.com" <quic_saipraka@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Will Deacon <will@kernel.org>, "maz@kernel.org" <maz@kernel.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Steven Rostedt <rostedt@goodmis.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"quic_psodagud@quicinc.com" <quic_psodagud@quicinc.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC
Date: Thu, 25 Nov 2021 14:51:19 +0100 [thread overview]
Message-ID: <20211125135119.GA7625@axis.com> (raw)
In-Reply-To: <CAJfuBxyvDtALAHM53RdnWT4ke6Cjrc3OWTAqNKe_n-o_LhtpYg@mail.gmail.com>
On Fri, Nov 19, 2021 at 11:46:31PM +0100, jim.cromie@gmail.com wrote:
> Vincent's code has the macro magic to define that event, which IIUC
> is what makes it controllable by ftrace, and therefore acceptable in
> principle to Steve.
> Would there be any reason to expand his set of 2 events into dev_dbg,
> pr_debug etc varieties ?
> (ie any value to separating dev, !dev ?, maybe so
>
> Sean's code uses trace_array_printk primarily, which is EXPORTed,
> which is a virtue.
>
> Vincents code does
> +/*
> + * This code is heavily based on __ftrace_trace_stack().
> + *
> + * Allow 4 levels of nesting: normal, softirq, irq, NMI.
> + */
>
> to implement
>
> +static void dynamic_trace(const char *fmt, va_list args)
>
> Has this __ftrace_trace_stack() code been bundled into or hidden under
> a supported interface ?
>
> would it look anything like trace_array_printk() ?
>
> what problem is that code solving inside dynamic-debug.c ?
I'm not sure I fully understand all of your questions, but perhaps this
thread with Steven's reply to the first version of my patchset will
answer some of them:
https://lore.kernel.org/lkml/20200723112644.7759f82f@oasis.local.home/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "jim.cromie@gmail.com" <jim.cromie@gmail.com>
Cc: "quic_saipraka@quicinc.com" <quic_saipraka@quicinc.com>,
Jason Baron <jbaron@akamai.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Will Deacon <will@kernel.org>, "maz@kernel.org" <maz@kernel.org>,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sean Paul <seanpaul@chromium.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Sean Paul <sean@poorly.run>, Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"quic_psodagud@quicinc.com" <quic_psodagud@quicinc.com>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC
Date: Thu, 25 Nov 2021 14:51:19 +0100 [thread overview]
Message-ID: <20211125135119.GA7625@axis.com> (raw)
In-Reply-To: <CAJfuBxyvDtALAHM53RdnWT4ke6Cjrc3OWTAqNKe_n-o_LhtpYg@mail.gmail.com>
On Fri, Nov 19, 2021 at 11:46:31PM +0100, jim.cromie@gmail.com wrote:
> Vincent's code has the macro magic to define that event, which IIUC
> is what makes it controllable by ftrace, and therefore acceptable in
> principle to Steve.
> Would there be any reason to expand his set of 2 events into dev_dbg,
> pr_debug etc varieties ?
> (ie any value to separating dev, !dev ?, maybe so
>
> Sean's code uses trace_array_printk primarily, which is EXPORTed,
> which is a virtue.
>
> Vincents code does
> +/*
> + * This code is heavily based on __ftrace_trace_stack().
> + *
> + * Allow 4 levels of nesting: normal, softirq, irq, NMI.
> + */
>
> to implement
>
> +static void dynamic_trace(const char *fmt, va_list args)
>
> Has this __ftrace_trace_stack() code been bundled into or hidden under
> a supported interface ?
>
> would it look anything like trace_array_printk() ?
>
> what problem is that code solving inside dynamic-debug.c ?
I'm not sure I fully understand all of your questions, but perhaps this
thread with Steven's reply to the first version of my patchset will
answer some of them:
https://lore.kernel.org/lkml/20200723112644.7759f82f@oasis.local.home/
next prev parent reply other threads:[~2021-11-26 10:37 UTC|newest]
Thread overview: 129+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 22:01 [PATCH v10 00/10 RESEND] use DYNAMIC_DEBUG to implement DRM.debug & DRM.trace Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:01 ` [PATCH v10 01/10] dyndbg: add DEFINE_DYNAMIC_DEBUG_BITGRPS macro and callbacks Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:01 ` [PATCH v10 02/10] drm: fix doc grammar Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:01 ` [PATCH v10 03/10] amdgpu: use dyndbg.BITGRPS to control existing pr_debugs Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` Jim Cromie
2021-11-11 22:01 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 04/10] i915/gvt: trim spaces from pr_debug "gvt: core:" prefixes Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 05/10] i915/gvt: use dyndbg.BITGRPS for existing pr_debugs Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 06/10] drm_print: add choice to use dynamic debug in drm-debug Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 07/10] drm_print: instrument drm_debug_enabled Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-12 11:49 ` Vincent Whitchurch
2021-11-12 11:49 ` Vincent Whitchurch
2021-11-12 11:49 ` Vincent Whitchurch
2021-11-12 11:49 ` Vincent Whitchurch
2021-11-12 11:49 ` [Intel-gfx] " Vincent Whitchurch
2021-11-12 15:08 ` Jason Baron
2021-11-12 15:08 ` Jason Baron
2021-11-12 15:08 ` Jason Baron
2021-11-12 15:08 ` Jason Baron
2021-11-12 15:08 ` [Intel-gfx] " Jason Baron
2021-11-12 17:07 ` Steven Rostedt
2021-11-12 17:07 ` Steven Rostedt
2021-11-12 17:07 ` Steven Rostedt
2021-11-12 17:07 ` Steven Rostedt
2021-11-12 17:07 ` [Intel-gfx] " Steven Rostedt
2021-11-12 17:32 ` Jason Baron
2021-11-12 17:32 ` Jason Baron
2021-11-12 17:32 ` Jason Baron
2021-11-12 17:32 ` Jason Baron
2021-11-12 17:32 ` [Intel-gfx] " Jason Baron
2021-11-12 17:54 ` Steven Rostedt
2021-11-12 17:54 ` Steven Rostedt
2021-11-12 17:54 ` Steven Rostedt
2021-11-12 17:54 ` Steven Rostedt
2021-11-12 17:54 ` [Intel-gfx] " Steven Rostedt
2021-11-16 8:46 ` Pekka Paalanen
2021-11-16 8:46 ` Pekka Paalanen
2021-11-16 8:46 ` Pekka Paalanen
2021-11-16 8:46 ` [Intel-gfx] " Pekka Paalanen
2021-11-18 14:29 ` Jason Baron
2021-11-18 14:29 ` Jason Baron
2021-11-18 14:29 ` Jason Baron
2021-11-18 14:29 ` [Intel-gfx] " Jason Baron
2021-11-18 15:24 ` Pekka Paalanen
2021-11-18 15:24 ` Pekka Paalanen
2021-11-18 15:24 ` Pekka Paalanen
2021-11-18 15:24 ` [Intel-gfx] " Pekka Paalanen
2021-11-19 16:21 ` Jason Baron
2021-11-19 16:21 ` Jason Baron
2021-11-19 16:21 ` Jason Baron
2021-11-19 16:21 ` [Intel-gfx] " Jason Baron
2021-11-19 22:46 ` jim.cromie
2021-11-19 22:46 ` jim.cromie
2021-11-19 22:46 ` jim.cromie
2021-11-19 22:46 ` jim.cromie
2021-11-19 22:46 ` [Intel-gfx] " jim.cromie
2021-11-19 22:54 ` Steven Rostedt
2021-11-19 22:54 ` Steven Rostedt
2021-11-19 22:54 ` Steven Rostedt
2021-11-19 22:54 ` Steven Rostedt
2021-11-19 22:54 ` [Intel-gfx] " Steven Rostedt
2021-11-25 13:51 ` Vincent Whitchurch [this message]
2021-11-25 13:51 ` Vincent Whitchurch
2021-11-25 13:51 ` Vincent Whitchurch
2021-11-25 13:51 ` Vincent Whitchurch
2021-11-25 13:51 ` [Intel-gfx] " Vincent Whitchurch
2021-11-22 9:02 ` Pekka Paalanen
2021-11-22 9:02 ` Pekka Paalanen
2021-11-22 9:02 ` Pekka Paalanen
2021-11-22 9:02 ` [Intel-gfx] " Pekka Paalanen
2021-11-22 22:42 ` jim.cromie
2021-11-22 22:42 ` jim.cromie
2021-11-22 22:42 ` jim.cromie
2021-11-22 22:42 ` [Intel-gfx] " jim.cromie
2021-11-23 8:45 ` Pekka Paalanen
2021-11-23 8:45 ` Pekka Paalanen
2021-11-23 8:45 ` Pekka Paalanen
2021-11-23 8:45 ` [Intel-gfx] " Pekka Paalanen
2021-11-23 9:32 ` Simon Ser
2021-11-23 9:32 ` Simon Ser
2021-11-23 9:32 ` Simon Ser
2021-11-23 9:32 ` [Intel-gfx] " Simon Ser
2021-12-08 5:16 ` jim.cromie
2021-12-08 5:16 ` jim.cromie
2021-12-08 5:16 ` jim.cromie
2021-12-08 5:16 ` jim.cromie
2021-12-08 5:16 ` [Intel-gfx] " jim.cromie
2021-12-09 15:09 ` Vincent Whitchurch
2021-12-09 15:09 ` Vincent Whitchurch
2021-12-09 15:09 ` Vincent Whitchurch
2021-12-09 15:09 ` Vincent Whitchurch
2021-12-09 15:09 ` [Intel-gfx] " Vincent Whitchurch
2021-11-11 22:02 ` [PATCH v10 09/10] dyndbg: create DEFINE_DYNAMIC_DEBUG_LOG|TRACE_GROUPS Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:02 ` [PATCH v10 10/10] drm: use DEFINE_DYNAMIC_DEBUG_TRACE_GROUPS in 3 places Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` Jim Cromie
2021-11-11 22:02 ` [Intel-gfx] " Jim Cromie
2021-11-11 22:40 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for use DYNAMIC_DEBUG to implement DRM.debug & DRM.trace (rev3) Patchwork
2021-12-10 7:22 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for use DYNAMIC_DEBUG to implement DRM.debug & DRM.trace (rev4) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-11-05 19:26 [PATCH v10 00/10] use DYNAMIC_DEBUG to implement DRM.debug & DRM.trace Jim Cromie
2021-11-05 19:26 ` [PATCH v10 08/10] dyndbg: add print-to-tracefs, selftest with it - RFC Jim Cromie
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=20211125135119.GA7625@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=ppaalanen@gmail.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_saipraka@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=will@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.